[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1259667480.3100.10.camel@palomino.walls.org>
Date: Tue, 01 Dec 2009 06:38:00 -0500
From: Andy Walls <awalls@...ix.net>
To: Christoph Bartelmus <lirc@...telmus.de>
Cc: jonsmirl@...il.com, dmitry.torokhov@...il.com, j@...nau.net,
jarod@...hat.com, jarod@...sonet.com, khc@...waw.pl,
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?
On Tue, 2009-12-01 at 08:45 +0100, Christoph Bartelmus wrote:
> Hi Jon,
>
> on 30 Nov 09 at 16:35, Jon Smirl wrote:
> 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
>
> That would allow zero configuration for simple use cases and full
> flexibility for more advanced use cases.
>
> Christoph
I'd also prefer that approach.
That probably comes as no surprise, but I may not be able to keep
following/kibitzing in this thread. Christoph's statement sums up my
preference.
Regards,
Andy
--
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