From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760158AbZKZJO1 (ORCPT ); Thu, 26 Nov 2009 04:14:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760142AbZKZJO0 (ORCPT ); Thu, 26 Nov 2009 04:14:26 -0500 Received: from mx1.redhat.com ([209.132.183.28]:58616 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760140AbZKZJOY (ORCPT ); Thu, 26 Nov 2009 04:14:24 -0500 Message-ID: <4B0E46E6.4030006@redhat.com> Date: Thu, 26 Nov 2009 10:14:14 +0100 From: Gerd Hoffmann User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4 MIME-Version: 1.0 To: Jarod Wilson CC: Dmitry Torokhov , Andy Walls , Christoph Bartelmus , khc@pm.waw.pl, 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: <1259024037.3871.36.camel@palomino.walls.org> <20091126054938.GH23244@core.coreip.homeip.net> <6619F77F-446F-47ED-B9F5-6CFC00E3EA49@wilsonet.com> In-Reply-To: <6619F77F-446F-47ED-B9F5-6CFC00E3EA49@wilsonet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/26/09 07:23, Jarod Wilson wrote: > Well, when mythtv was started, I don't know that there were many > input layer remotes around... lirc was definitely around though. lirc predates the input layer IR drivers by years, maybe even the input layer itself. The main reason for the input layer IR drivers appearing was lirc not being mainline. A in-kernel driver (bttv in that case) which depends on a out-of-tree subsystem for IR support was simply a pain in the ass for both maintainer (/me back then) and users. At least for IR hardware which allows access to the raw samples it certainly makes sense to support lirc, additional to the current (or improved) input layer support. > The lirc support in mythtv actually relies on mapping remote button > names as defined in lircd.conf to keyboard key strokes. As mentioned > elsewhere in this beast of a thread, mythtv doesn't currently support > things like KEY_PLAY, KEY_VOLUMEUP, KEY_CHANNELUP, etc. just yet, but > I intend on fixing that... lircd can handle the input layer as input as well, so you actually can remap things via lircd even for pure input layer drivers. mythtv handling KEY_VOLUMEUP directly would be more elegant though. cheers, Gerd