[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9e4733910911280906if1191a1jd3d055e8b781e45c@mail.gmail.com>
Date: Sat, 28 Nov 2009 12:06:48 -0500
From: Jon Smirl <jonsmirl@...il.com>
To: Christoph Bartelmus <lirc@...telmus.de>
Cc: khc@...waw.pl, 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, 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?
On Sat, Nov 28, 2009 at 11:47 AM, Christoph Bartelmus <lirc@...telmus.de> wrote:
> @Maxim: I think Mauro is right. We need to find an approach that makes
> everybody happy. We should take the time now to discuss all the
> possibilities and choose the best solution. LIRC has lived so long outside
> the kernel, that we can wait another couple of weeks/months until we
> agreed on something which will be a stable API hopefully for many years to
> come.
Please do this. That's why I started this thread off with goals for
the implementation. After we settle on a set of goals we can move on
to how to implement those goals. The end result is almost certainly
going to combine aspects from all of the various proposals and the
LIRC code base is likely to be the largest contributor.
There are two very basic things that we need to reach consensus on first.
1) Unification with mouse/keyboard in evdev - put IR on equal footing.
2) Specific tools (xmodmap, setkeycodes, etc or the LIRC ones) or
generic tools (ls, mkdir, echo) for configuration
Once consensus is reached in those two areas everything else should be
much easier.
--
Jon Smirl
jonsmirl@...il.com
--
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