>> I have a Dell Lattitude CPxJ, which 'findchip' reports as containing an
>> SMC FDC37N958FR at 0x3f0, with SIR at 0x3e8 and FIR at 0x290. I have
>> successfully got IrDA working using 'irattach', but the 'smc-ircc' is
>> more problematic.
>
> How did u make it work? I've got the same problem with the ioport, but i
> won't even get IrDA working using irattach.
For a Lattitude, set the IR port to COM3 in the BIOS and set it to use FIR.
(COM1 is the serial port and COM2 is my modem).
>> When I do a 'modprobe smc-ircc' I get the frequently reported
>> 'device or resouce busy' type message, so I tried using 'setserial' to move
>
> setserial /dev/ttyS2 irq 3???
>
> > the IO addr of ttyS2 to another address. 'modprobe smc-ircc' now succeeds
> > and I get:
The command I used was:
setserial /dev/ttyS2 port 0x2e8
Where 0x2e8 is an unused serial port on my machine.
I'll give 'ifconfig irda0 up' a whiz later - thanks Bjorn.
BTW if you're having problems detecting the chip, recompiling with debug
on helps a lot - it's an option buried with the irda stuff, and you only
need to do a 'make modules' and copy the changed modules into /lib/modules.
This is how I found that smc-ircc was finding my chip and that the
'device or resource busy' was a correct statement and not that the driver
couldn't probe my chip. I found this after I modified the driver to set
io and io2 directly [incidentally this might be handy to build into the
driver, though probing works fine for me].
Cheers,
Robert
--
"Thou shalt not follow the NULL pointer, for chaos and madness
await thee at its end" - 2nd Commandment of C++, Anonymous
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
