Hi,
There seem to be real trouble with FIR and test11. As I did
push those patches in test11, I can give you my take on the situation.
I don't have any FIR device (apart from a VLSI, which doesn't
have any driver at all). All my tests are done with various kind of
SIR dongles. For me, test11 is rock solid and work beautifully.
I start it like :
> irattach /dev/ttyS0 -d actisys+ -s 1
So, my belief is that all the problems are due to FIR driver
and the lack of clear documentation. There is also problem with devfs,
but Dag has already this one under control.
It is my belief that irattach is *necessary* even for FIR
drivers, and that a FIR driver should be started like this :
--------------------------------
modprobe xxx-ircc
irattach irda0 -s
--------------------------------
Of course, I don't have any FIR hardware to prove it. But the
Oops that I've seen on the list suggest *very strongly* that the
internals of the IrDA stack are not initialised at all, which would be
consistent with the assumption above.
Now, if irattach do fail, that's a bug and should be reported
to Dag and fixed ASAP.
Dag, please check :
http://www.pasta.cs.uit.no/pipermail/linux-irda/2000-November/002005.html
What's the issue there ?
Now, another message for Dag :
Would it be possible to enable to following syntax in irattach :
> irattach nsc-ircc -s 1
> irattach smc-ircc -s 1
This would make things a bit simpler for people, make it more
uniform with SIR dongles, and avoid the kind of problems we are
seeing...
Have fun...
Jean
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
