I'm guessing some people may already be looking at the subject and
groaning ... I've hunted and searched and fiddled - and I'm now stuck.
Isn't that nice? Here's the state I'm at.
I started out with Bjorn Mork's patches from a message to this list on
January 23 and the RedHat 2.2.17 kernel source package (I've got some
other patches to apply and would really like to stick to this source
tree). The patch to findchip was fine and good. Currently it's telling
me ...
[root@bedlam irda]# findchip -v
Found SMC FDC37N971 Controller at 0xe0, DevID=0x02, Rev. 0
SIR Base 0x3e8, FIR Base 0x100
IRQ = 3, DMA = 2
Enabled: yes, Suspended: no
UART compatible: yes
Half duplex delay = 10 us
Looks like the expected result. From what I've seen of the two machines,
the M300 and V300 are pretty close as far as hardware goes.
Loading the module gets me ...
Mar 5 18:55:22 bedlam kernel: IrDA (tm) Protocols for Linux-2.2 (Dag
Brattli)
Mar 5 18:55:22 bedlam kernel: SMC IrDA Controller found; IrCC version
2.0, port 0x100, dma=2, irq=3
Mar 5 18:55:22 bedlam kernel: IrDA: Registered device irda0
So far so good, right?
Now at this point, I must admit to being a BIT unsure of what I'm doing.
I want to point irattach at the serial port, right? The serial port in
this case (I'm pretty sure) being /dev/ttyS2 (my logic being 0x3e8 ==
COM3 == ttyS2).
Mar 5 18:58:31 bedlam irattach: tcsetattr: Input/output error
I've also tried a module based on an smc-ircc.c posted by Rui Oliveira,
coupled with his setserial lines. Same result. Module loads fine, and
everything looks good until irattach.
I'm assuming I'm doing something way wrong down towards the end there
with irattach, since up until there everything looks perfect.
If someone can give me a gentle push in the right direction, I promise
I'll write some very clear documentation on my Armada/Linux web page. :)
Thanks,
Mike.
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
