[ Copied to [EMAIL PROTECTED] because of the bug reports ]

Nathan Catlow wrote:
> I am looking forward to some motorola L7089 <-> linux S5 IR action

I've made some progress, but so far, things don't look great. My
configuration:
 - PC: i386 architecture, 2.3.18 kernel, Tekram IRmate 210.
 - PDA: Psion S5, under EPOC (sigh), no aditional software installed.
 - Phone: Motorola L7089

Getting IrDA to work with 2.3.18 was a bit of a nightmare. I've applied
the 2.3.16 patch. Then I ran into the following problems:

 - trivial: net/irda/ircomm/Makefile adds ircomm_tty_ioctl.c to O_OBJS.
   Should be .o
 - tricky: net/irda/irlmp.c:irlmp_register_service calls get_random_bytes,
   but drivers/char/random.c isn't initialized yet (kernel oopses with a
   fairly nebulous stack trace). My ugly hack-around: call rand_initialize
   in irlmp_register_service if not compiled as a module and remove the
   original call to rand_initialize in drivers/char/mem.c. A cleaner
   solution would probably involve deferring the calls to get_random_bytes
   until they are really needed, i.e. when some user process starts using
   IrDA. Since I had more problems (probably just configuration), I
   eventually switched to using modules, assuming that's what's tested
   better.
 - nasty: had various crashes when removing modules or closing things. So
   I eventually strictly followed this sequence:
        reboot                          # very important step :-(
        insmod irda; insmod irtty
        insmod tekram                   # my IR dongle
        irattach /dev/ttyS1 -d tekram   # on ttyS1
        insmod ircomm; insmod ircomm-tty
        mknod /dev/irnine c 161 0       # largely undocumented feature (?)
                                        # see also /proc/tty/drivers
        irmanager -d 1
        dip -t
        port irnine
        term

   (BTW, irdadump-X11 is very nice.)

Communication among devices:
 - PDA-PC: seems to work well, didn't test it a lot. Note that the Psion
   doesn't seem to like to change partners in a Comm session. Works best
   if I exit Comm and restart it; Port activate on/off seems to work
   sometimes. irmanager is a lot more promiscuous.
 - PDA-Phone: see each other; communication works, but is fragile. Also,
   after a very short while, both parties get out of sync. Example:
   Typed:               Seen:           Comment:
   AT+CPBR=101,200      AT+CPBR=101,20  Last 0 missing; key didn't register ?
   0                    0               works, as expected ...
   [Enter]              0               uh ??
   [Enter]              ERROR           (sure, AT+CPBR=101,2000 is wrong)
   etc.

   I haven't made it to the point where a data call was set up properly
   with the Psion (under EPOC) so far.
 - PC-Phone: see each other; communication works, but is fragile. Data
   calls drop after maybe a minute. Not sure why. At least no "out of
   sync" problem.

Another interesting effect: my first few tests with the +CPBR command
with the Psion (read phone book) yielded the expected data (if I managed
to avoid the out of sync bug long enough). Later, any +CPBR either dropped
the IR connection or led to a phone reset (IR and radio dropped, but it
restarts itself, without asking for a PIN or such). Not quite sure what's
going on, could be a difference in the sequence of +C... commands.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, ICA, EPFL, CH       [EMAIL PROTECTED] /
/_IN_R_131__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/

_______________________________________________
Linux-IrDA mailing list  -  [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda

Reply via email to