> Btw, I'm wondering whether there would be some general need to provide > access to the traffic on the physical layer without having an IrDA stack > on top of the driver. Something like raw SIR byte stream. Sure, we have > this available for all the systems which use irtty - but not for FIR-style > drivers, IIRC. Would it make sense to define such an interface? It would > be helpful for people using peer devices without any IrDA stack at all, so > they can not even use Ultra sockets. I was asked this for the VLSI and it > should be possible to do - options are either significant code duplication > or adding a generic interface but for VLSI alone I doubt it's worth the > effort.
i think this would be a nice feature, but i think it would require something more than a small change in the kernel. the way i'm reading this is that you want to have an api that allows you to access stats from low level communication interfaces without necessarily having a stack attached to that interface, correct? actually, i really think this might be the right way to go because it provides a common underlying layer for the irda stack. implementing this might actually be the first step to moving the irda stack completely out of the kernel. if a generic irda interface were defined for both sir and fir ports, the stack could move to user space and use the interfaces provided by the sir/fir drivers to implement stack functionality. hmm... interesting :) Andrew Sutton [EMAIL PROTECTED] _______________________________________________ Linux-IrDA mailing list - [EMAIL PROTECTED] http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
