>Is the Super I/O SMSC FDC37N769 controller supported by
>Linux IR? I can't see it mentioned anywhere.
>If it is supported - how do I configure it, if it isn't
>then any idea if/when it might be supported?
I've not checked the SMSC pages yet, but it looks like it's an SMC-IrCC FIR
chipset. There are two version I know of this FIR chipset: IrCC 1.x and
IrCC 2.0, somewhat supported by the smc-ircc.c driver.
Thomas worked on the version 1.x, but I've never heard success story for
this chipset (Thomas, can we have an update ?).
Since I have an IrCC version 2.0 on my Lifebook 270x, I had to modify the
smc-ircc.c driver to get it recognized (kernel 2.3.19). Even with the
modifications I've made since, the FIR is still not stable.
For the tests, I am using IrCOMM (light-hacked 2.2.12-irda3) and
HyperTerm on an Omnibook (under w95). To send data, I simply do "cat
/some/file > /dev/ircomm", or setup inittab and getty.
Here are the symptoms:
---------------------
* When I exchange "enough" data with the Omnibook using IrCOMM, my
Lifebook freeze black (no oops) after 3 seconds!
* If there's not too much data to send ( ~ < 2K, I've not tried to find
the threshold) , then there's no crash, and the data is received correctly
by the Omnibook.
* If a connection is established (w/ getty), but without exchanging data,
it doesn't crash (but the "keepalive keeps runnning at 4Mbps).
* I've noticed in klogs that when sending a "small" file (cat /a/2K_file
>/dev/ircomm), the DMA does not succeed to send properly big frames (some
bytes not sent). I wonder if it's not due to the IDE driver holding too
long interrupts, and having the threshold of the IrCC too high.
I still have to play with hdparm and threshold setup...
* I don't remeber in which case (maybe when sending a 4K file), but a bunch
of freaky characters are printed on the screen, maybe the content of the RAM
is printed to the console, and like a human would "see" all his life before
dying, so does my Lifebook.
I guess it's the same problem as the ppa driver.
* sometimes, the driver has trouble to switch from 4Mps back to 9600bps.
After the IrCOMM session is closed, IrLAP tells me sending is at 9600bps,
but receiving is still at 4Mps. Hence the Omnibook doen't "see" the
Lifebook anymore. Therfore I have to rmmod/insmod the driver to
re-initialize the chipset. The Takahide's hack can also be usefull (don't
forget to fix the bug of the hardcoded ioport in release_region!).
The Omnibook is not mine, so I cannot make tests whenever I want. But I'll
have it next week. So hopefully, I can get a step further...
Any advices, ideas, comments are welcome. Is there anyone else playing with
SMC IrCC in this list ?
Cheers,
--
Stephane
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
