[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m37hta28w9.fsf@intrepid.localdomain>
Date: Sat, 28 Nov 2009 12:20:22 +0100
From: Krzysztof Halasa <khc@...waw.pl>
To: Maxim Levitsky <maximlevitsky@...il.com>
Cc: Stefan Richter <stefanr@...6.in-berlin.de>,
Jon Smirl <jonsmirl@...il.com>,
Christoph Bartelmus <christoph@...telmus.de>,
jarod@...sonet.com, awalls@...ix.net, dmitry.torokhov@...il.com,
j@...nau.net, jarod@...hat.com, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
mchehab@...hat.com, superm1@...ntu.com
Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system?
Maxim Levitsky <maximlevitsky@...il.com> writes:
> If we add in-kernel decoding, we still will end up with two different
> decoding, one in kernel and one in lirc.
And that's good. Especially for a popular and simple protocol such as
RC5.
Actually, it's not about adding the decoder. It's about fixing it.
I can fix it.
--
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