> "Stefan R\vllin" <[EMAIL PROTECTED]> writes:
>
> And you did "rmmod serial" before you started? Since you can use irattach,
> you should be aware that the serial driver has already grabbed the IrDA
> port. You cannot have two device drivers for the same hardware, so if you
> want to use nsc_fir, then you must move away the serial driver. Either
> rmmod it, or if compiled into the kernel, you must use setserial to make it
> use some other ioport and irq.
I had serial support compiled into the kernel. After compiling it as a module
nothing has changed:
lsmod:
Module Size Used by
modprobe nsc_fir:
/lib/modules/2.2.14/misc/nsc_fir.o: init_module: Device or resource busy
kernel message:
Jan 7 11:15:03 laepi kernel: nsc_fir, Found NSC PC97338 chip, revision=3
> Yes, because now the serial driver will not attach itself to the IrDA
> port. Are you saying that you then got:
>
> /lib/modules/2.2.14/misc/nsc_fir.o: init_module: Device or resource busy
>
> and
>
> Jan 6 20:39:11 laepi kernel: nsc_fir, Found NSC PC97338 chip, revision=3
>
> at the same time?
Yes.
Do I have to enable or disable the infrared port in the bios to use with nsc_fir? Are
special settings (irq, dma) necessary?
Stefan
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
