From: Jean T. <jt...@bo...> - 2004-06-16 17:27:31
|
Robert Brueckmann wrote : > I have a laptop with an Actisys 200L dongle attached to Com1. I have loaded > the modules (kernel 2.6.6-rc1) and started irattach (irda-utils-0.9.16) with > > irattach /dev/ttyS0 -d act200l -s Hi, I can't really fault what you have done, therefore we will have to debug this stuff. Here are my comments : o The latest kernel I tried was 2.6.5, with an Actisys 220L dongle. In theory, there was no significant change later, but you never know. o The act200l-sir driver was converted to the new sir-dev API by Martin without the hardware. It is possible that some bugs were introduced in the conversion process. You may want to try the original act200l driver, either by going to 2.4.X, or testing with irport & 2.6.X. o The original act200l driver was not much tested/used, because the hardware is rare. However, the driver is fairly simple, so you should have a look at the source. You may want to increase some of the timings just to be on the safe side. o The driver uses the "raw write" functionality of the irtty driver. I think Martin has tested it, but check with him for latest status. o You may want to double check the serial port. In some occasion, Linux swap serial ports. Use "setserial" to check I/O address and irq. o Double check the dongle. Most people have the 220L+ dongle, which use a different driver (actisys-sir). Good luck ! Jean |
From: Martin D. <li...@md...> - 2004-06-17 07:01:29
|
On Wed, 16 Jun 2004, Jean Tourrilhes wrote: > Robert Brueckmann wrote : > > I have a laptop with an Actisys 200L dongle attached to Com1. I have loaded > > the modules (kernel 2.6.6-rc1) and started irattach (irda-utils-0.9.16) with > > > > irattach /dev/ttyS0 -d act200l -s > > Hi, > > I can't really fault what you have done, therefore we will > have to debug this stuff. Here are my comments : Thanks Jean - not much I could add at the moment: > o The latest kernel I tried was 2.6.5, with an Actisys 220L > dongle. In theory, there was no significant change later, but you > never know. I'd suggest trying 2.6.7. Well, the msecs_to_jiffies change should make anything different, but there is the fix for the missing spin_unlock in the raw tx-path in 2.6.7 and this might really be the culprit here. > o The act200l-sir driver was converted to the new sir-dev API > by Martin without the hardware. It is possible that some bugs were > introduced in the conversion process. You may want to try the original > act200l driver, either by going to 2.4.X, or testing with irport & > 2.6.X. Jep, if any of this works, we have a reference to check against. > o The original act200l driver was not much tested/used, > because the hardware is rare. However, the driver is fairly simple, so > you should have a look at the source. You may want to increase some of > the timings just to be on the safe side. > o The driver uses the "raw write" functionality of the irtty > driver. I think Martin has tested it, but check with him for latest > status. Well, without the hardware it's hardly tested by me. I did simply ir-attached the dongle and tried with a different physical one - but this doesn't cover the raw mode because this is only reached during speed change which doesn't happen without the dongle providing sane rx. So the raw mode stuff is just assumed to work in 2.6.7 since somebody with ma620 (or tekram, don't remember) reported it working after the locking fix mentioned above. > o You may want to double check the serial port. In some > occasion, Linux swap serial ports. Use "setserial" to check I/O > address and irq. Maybe this differs individually, but I haven't seen any irda device yet where I personally couldn't see some dim red visual light coming through the ir-window during active discovery in a very dark environment. Just as an ultimate check the dongle is at least transmitting something. > o Double check the dongle. Most people have the 220L+ dongle, > which use a different driver (actisys-sir). Martin |