[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1259676635.18599.5.camel@maxim-laptop>
Date: Tue, 01 Dec 2009 16:10:35 +0200
From: Maxim Levitsky <maximlevitsky@...il.com>
To: Andy Walls <awalls@...ix.net>
Cc: Christoph Bartelmus <lirc@...telmus.de>, 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 06:38 -0500, Andy Walls wrote:
> 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.
I also agree with this approach.
This way, there will be no need for configfs hacks, but just static
table for bundled remotes, and in fact this is very clean approach.
Also, since bundled remotes use standard protocols, there will be no
problem to add decoders for them.
For the rest, the remotes that were never meant to be used with the
computer, lircd will do just fine.
So, it a deal?
Best regards,
Maxim Levitsky
--
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