[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3k4x42cd3.fsf@intrepid.localdomain>
Date: Thu, 03 Dec 2009 18:31:20 +0100
From: Krzysztof Halasa <khc@...waw.pl>
To: lirc@...telmus.de (Christoph Bartelmus)
Cc: jonsmirl@...il.com, awalls@...ix.net, 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, lirc-list@...ts.sourceforge.net,
mchehab@...hat.com, superm1@...ntu.com
Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system?
lirc@...telmus.de (Christoph Bartelmus) writes:
> Currently I would tend to an approach like this:
> - raw interface to userspace using LIRC
> - fixed set of in-kernel decoders that can handle bundled remotes
I'd modify it a bit:
- raw interface to userspace using LIRC
- fixed set of in-kernel decoders
Longer term:
Removing the key assignment tables from the kernel. Plug-and-play can be
then achieved with udev. The only thing needed from the kernel is
indicating the tuner/sensor type, udev can guess the bundled remote type.
Porting the in-kernel drivers (such as ir-common) to LIRC interface
(while not removing the input layer mode).
--
Krzysztof Halasa
--
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