Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759775AbZKYUoo (ORCPT ); Wed, 25 Nov 2009 15:44:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759754AbZKYUon (ORCPT ); Wed, 25 Nov 2009 15:44:43 -0500 Received: from khc.piap.pl ([195.187.100.11]:42318 "EHLO khc.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754802AbZKYUom (ORCPT ); Wed, 25 Nov 2009 15:44:42 -0500 From: Krzysztof Halasa To: Jarod Wilson Cc: lirc@bartelmus.de (Christoph Bartelmus), 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] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure References: Date: Wed, 25 Nov 2009 21:44:45 +0100 In-Reply-To: (Jarod Wilson's message of "Wed, 25 Nov 2009 13:07:06 -0500") 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: 759 Lines: 20 Jarod Wilson writes: > Took me a minute to figure out exactly what you were talking about. > You're referring to the current in-kernel decoding done on an ad-hoc > basis for assorted remotes bundled with capture devices, correct? Yes. > Well, is there any reason most of those drivers with > currently-in-kernel-but-badly-broken decoding can't be converted to > use the lirc interface if its merged into the kernel? For many of them "lirc mode" can be easily _added_. -- 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/