From mboxrd@z Thu Jan 1 00:00:00 1970 From: Krzysztof Halasa Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system? Date: Sat, 28 Nov 2009 12:20:22 +0100 Message-ID: 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=us-ascii Return-path: Received: from khc.piap.pl ([195.187.100.11]:57801 "EHLO khc.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751977AbZK1LUT (ORCPT ); Sat, 28 Nov 2009 06:20:19 -0500 In-Reply-To: <1259370501.11155.14.camel@maxim-laptop> (Maxim Levitsky's message of "Sat, 28 Nov 2009 03:08:21 +0200") Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Maxim Levitsky 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 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. -- Krzysztof Halasa