From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Levitsky Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system? Date: Sat, 28 Nov 2009 16:42:48 +0200 Message-ID: <1259419368.18747.0.camel@maxim-laptop> References: <9e4733910911270757j648e39ecl7487b7e6c43db828@mail.gmail.com> <4B104971.4020800@s5r6.in-berlin.de> <1259370501.11155.14.camel@maxim-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Krzysztof Halasa Cc: Stefan Richter , Jon Smirl , Christoph Bartelmus , jarod@wilsonet.com, awalls@radix.net, dmitry.torokhov@gmail.com, j@jannau.net, jarod@redhat.com, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, mchehab@redhat.com, superm1@ubuntu.com List-Id: linux-input@vger.kernel.org On Sat, 2009-11-28 at 12:20 +0100, Krzysztof Halasa wrote: > Maxim Levitsky 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. This is nonsense.