Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753673AbZK1LUV (ORCPT ); Sat, 28 Nov 2009 06:20:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752079AbZK1LUU (ORCPT ); Sat, 28 Nov 2009 06:20:20 -0500 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 From: Krzysztof Halasa 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 Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system? References: <9e4733910911270757j648e39ecl7487b7e6c43db828@mail.gmail.com> <4B104971.4020800@s5r6.in-berlin.de> <1259370501.11155.14.camel@maxim-laptop> Date: Sat, 28 Nov 2009 12:20:22 +0100 In-Reply-To: <1259370501.11155.14.camel@maxim-laptop> (Maxim Levitsky's message of "Sat, 28 Nov 2009 03:08:21 +0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 588 Lines: 16 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/