public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
[parent not found: <Pine.LNX.4.10.10011072027520.15254-100000@penguin.transmeta.com>]
* [RANT] Linux-IrDA status
@ 2000-11-08  1:14 Jean Tourrilhes
       [not found] ` <3A08AB56.10BD5007@mandrakesoft.com>
  0 siblings, 1 reply; 17+ messages in thread
From: Jean Tourrilhes @ 2000-11-08  1:14 UTC (permalink / raw)
  To: Linus Torvalds, Linux kernel mailing list, Alan Cox, Dag Brattli

	Hi,

	(I'm not on the Linux kernel mailing list)

	The IrDA stack in Linux is non functional and has some major
critical bugs :
                        http://linux24.sourceforge.net/
	Not only it doesn't work, but it can crash your kernel fast.

	Most might wonder why the IrDA stack is in such state of
disrepair. Is there no maintainers and nobody who cares ?
	The truth is that every 2 month, Dag Brattli, the official
maintainer of the IrDA stack (see MAINTAINERS), collect all our
patches and send the latest official Linux-IrDA patch to Linus.
	And every time the patch never materialise in the Linux
kernel. Of course, Dag never receive any answer, so doesn't know why
his patches are going directly to /dev/null.
	As we fix more bugs, the official IrDA patch get growing and
growing. The patch that Dag sent last week to Linus was 320k. It has
slowly accumulated over one year :-(

	On the other hand, what never cease to amaze me is that some
patches to the IrDA code gets into the kernel. Some of those patches
make things better, some make things worse. Those patches certainly
don't come from Dag or any of the most active Linux-IrDA hacker, and
none of us see those patches in advance so that we get a chance to
comment on them and test them.
	I guess that some people have trouble reading the MAINTAINERS
file :-( Or maybe there is another maintainer for the IrDA stack and
none of us knows about it.


	I think for us the only solution is to ignose what's happening
in the 2.4.X kernel and have Dag maintaining Linux-IrDA separate from
the kernel. I don't see why Dag should take the effort to send regular
patch to Linus if they get ignored.
	In other words, the chances to have IrDA working in kernel 2.4
are *very* slim at this point.
	So, if people are interested in IrDA and want to use it, they
should suscribe to the Linux-IrDA mailing list and can ask me the
latest patch (Dag is now too discouraged). We will put it in the usual
place on Sourceforge...

	I hope it clarify a few things...

	Jean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

^ permalink raw reply	[flat|nested] 17+ messages in thread

end of thread, other threads:[~2000-11-12 15:51 UTC | newest]

Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <Pine.LNX.4.10.10011072030070.15254-100000@penguin.transmeta.com>
2000-11-08  5:08 ` [RANT] Linux-IrDA status Michael Rothwell
2000-11-08  5:23   ` Linus Torvalds
     [not found]     ` <20001109192404.B25828@bougret.hpl.hp.com>
2000-11-10  3:50       ` The IrDA patches !!! (+ more flames) Jean Tourrilhes
2000-11-10 19:56       ` The IrDA patches !!! (was Re: [RANT] Linux-IrDA status) Linus Torvalds
2000-11-10 21:25         ` Jean Tourrilhes
2000-11-12  2:43           ` Linus Torvalds
2000-11-12  3:12             ` Jean Tourrilhes
2000-11-11 12:04         ` Horst von Brand
2000-11-08  7:26   ` [RANT] Linux-IrDA status Linus Torvalds
2000-11-08  8:14     ` Russell King
2000-11-08 12:15     ` [RANT] Linux-IrDA status, " Dag Brattli
2000-11-10 21:24       ` Pavel Machek
2000-11-08 12:31     ` Michael Rothwell
     [not found] <Pine.LNX.4.10.10011072027520.15254-100000@penguin.transmeta.com>
     [not found] ` <200011081204.MAA68767@tepid.osl.fast.no>
2000-11-08 18:20   ` Jean Tourrilhes
2000-11-08  1:14 Jean Tourrilhes
     [not found] ` <3A08AB56.10BD5007@mandrakesoft.com>
2000-11-08  1:38   ` Jean Tourrilhes
2000-11-08  8:12     ` Russell King

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox