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:18:09 +0100 Message-ID: References: <200910200956.33391.jarod@redhat.com> <200910200958.50574.jarod@redhat.com> <4B0A765F.7010204@redhat.com> <4B0A81BF.4090203@redhat.com> <4B0AB60B.2030006@s5r6.in-berlin.de> <4B0AC8C9.6080504@redhat.com> <4B0E71B6.4080808@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <4B0E71B6.4080808@redhat.com> (Mauro Carvalho Chehab's message of "Thu, 26 Nov 2009 10:16:54 -0200") Sender: linux-kernel-owner@vger.kernel.org To: Mauro Carvalho Chehab Cc: Stefan Richter , Jarod Wilson , Dmitry Torokhov , linux-kernel@vger.kernel.org, Mario Limonciello , linux-input@vger.kernel.org, linux-media@vger.kernel.org, Janne Grunau , Christoph Bartelmus List-Id: linux-input@vger.kernel.org Mauro Carvalho Chehab writes: > Technically, it is not hard to port this solution to the other > drivers, but the issue is that we don't have all those IR's to know > what is the complete scancode that each key produces. So, the hardest > part is to find a way for doing it without causing regressions, and to > find a group of people that will help testing the new way. We don't want to "port it" to other drivers. We need to have a common module which does all RCx decoding. The individual drivers should be as simple as possible, something that I outlined in a previous mail. -- Krzysztof Halasa