[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091129124011.4d8a6080@lxorguk.ukuu.org.uk>
Date: Sun, 29 Nov 2009 12:40:11 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Andy Walls <awalls@...ix.net>
Cc: Jon Smirl <jonsmirl@...il.com>, Krzysztof Halasa <khc@...waw.pl>,
Christoph Bartelmus <lirc@...telmus.de>,
dmitry.torokhov@...il.com, j@...nau.net, jarod@...hat.com,
jarod@...sonet.com, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
maximlevitsky@...il.com, mchehab@...hat.com,
stefanr@...6.in-berlin.de, superm1@...ntu.com
Subject: Re: [RFC] What are the goals for the architecture of an in-kernel
IR system?
> BTW, circa 1995 my serial mouse "Just Worked" in Linux. Sometime around
Correct X11 just talked to the serial ports. In fact that is still the
way to configure it if you want any sanity in life.
> and serial connected IRs. It's also too convenient to access USB IR
> hardware from existing userspace drivers to bother porting into the
> kernel.
Userspace needs a way to identify IR hardware and to interface with it
using the right protocol. It's not clear the kernel needs to provide
anything more than minimal hardware interfaces in most case - be that
serial, libusb, ...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists