Itai Nahshon <[EMAIL PROTECTED]> writes:
> The possibility of having kernel version 2.4 out in a couple
> of months has two aspects. The first is that there isn't anything
> urgent about getting things into 2.2 (but then it may take longer).
> The other is that everything planned for the next stable kernel
> has to be ready and there isn't much time.
>
> What's left on the kernel-side todo list? (bug fixes, new features,
> cleanup) that's planned for kernel 2.4?
Some todo for kernel side of Linux-IrDA for Linux-2.3/2.4:
1) Fix the sockets interface so it confirms to WinSock (better to be the
same, instead of slightly different). This is important if we want
companies to port their IrDA applications to Linux.
2) Fix LM-IAS so you get an error if you try to register the same service
twice.
3) Fix the UIRCC driver (I've got some new docs from Sharp that might help
me).
4) Fix the SMC driver (I don't have any machines with the SMC chipset)
5) Make sure network devices are never (un)registered from interrupt context
6) Fix IrLAP flow control for incomming data while using IrCOMM 3-wire raw
mode (really needs IrLMP exclusive mode as well).
---- Less important ---
7) Create a kernel thread that can help with timing in the device/dongle
drivers. Right now we use irmanager for this, but a kernel thread would
be better. The reason for wanting a process context is that it's much
easier for making delays. The dongle drivers would be _very_ hairy if you
implemented them using kernel timers.
8) IrLAN cleanup
-- Dag
--
/ Dag Brattli | The Linux-IrDA Project /
// University of Tromsoe, Norway | Infrared communication for Linux //
/// http://www.cs.uit.no/~dagb | http://www.cs.uit.no/linux-irda/ ///
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
