From mboxrd@z Thu Jan 1 00:00:00 1970 From: Krzysztof Halasa Subject: Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure Date: Thu, 26 Nov 2009 19:13:08 +0100 Message-ID: References: <4B0EABF8.9000902@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from khc.piap.pl ([195.187.100.11]:56893 "EHLO khc.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750973AbZKZSNE (ORCPT ); Thu, 26 Nov 2009 13:13:04 -0500 In-Reply-To: <4B0EABF8.9000902@redhat.com> (Mauro Carvalho Chehab's message of "Thu, 26 Nov 2009 14:25:28 -0200") Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Mauro Carvalho Chehab Cc: 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, superm1@ubuntu.com Mauro Carvalho Chehab writes: > 1) the developer that adds the hardware also adds the IR code. He has > the hardware and the IR for testing, so it means a faster development > cycle than waiting for someone else with the same hardware and IR to > recode it on some other place. You should remember that not all > developers use lirc; It's fine, but please - no keymaps in the kernel (except for fixed receivers, i.e. the ones which can only work with their own dedicated remote, and which don't pass RC5/etc. code). The existing keymaps (those which can be used with lirc) have to be moved to userspace as well. -- Krzysztof Halasa