Dag Brattli <[EMAIL PROTECTED]> writes:
> > i think the major problem is that nsc-ircc is failing in
> > nsc_ircc_setup on the chip version check... does anyone else have this
> > problem? is this check really important?
>
> You can always try to fix the code yourself. You'll just have to add the
> code shown with the + signs (but you should not add the + itself). Then you
> can do: "make modules && make modules_install" from /usr/src/linux and try
> again. If it now works for you, then I'll fix the code.
yup, tried this out this morning. that got me past the version check,
but now i get the message:
Jan 20 09:21:32 danube kernel: nsc-ircc, unable to allocate irq=0
this is probably a problem in the 338 probe routine, but i couldn't
get the debug code activated to get better output yet ;-). but,
oddly, when i run 'findchip -v' i get:
reg=0x030
Found NSC PC87338 Controller at 0x398, DevID=0x0b, Rev. 3
SIR Base 0x2e8, FIR Base 0x2e8
IRQ = 0, DMA = 3
Enabled: yes, Suspended: no
UART compatible: yes
Half duplex delay = 0 us
whereas lspnp -v gives me:
10 PNP0510 Generic IRDA-compatible device
dma 3
io 0x02e8-0x02ef
irq 3
so perhaps the probe isn't getting the IRQ right, and maybe this is
because the version string actually means there's a real difference
and maybe there's a bug, i'm not sure. i'm specifying the irq, dma,
and io in my modules.conf, so i'm not sure why it's trying "irq 0" at
all.
ian
--
----
Ian Soboroff [EMAIL PROTECTED]
University of MD Baltimore County http://www.cs.umbc.edu/~ian
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
