Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272872AbTHKS7I (ORCPT ); Mon, 11 Aug 2003 14:59:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272988AbTHKS6F (ORCPT ); Mon, 11 Aug 2003 14:58:05 -0400 Received: from smtp-out2.iol.cz ([194.228.2.87]:23253 "EHLO smtp-out2.iol.cz") by vger.kernel.org with ESMTP id S272975AbTHKS40 (ORCPT ); Mon, 11 Aug 2003 14:56:26 -0400 Date: Mon, 11 Aug 2003 20:55:19 +0200 From: Pavel Machek To: Johannes Stezenbach , Gerd Knorr , Flameeyes , Pavel Machek , Christoph Bartelmus , LIRC list , LKML , vojtech@suse.cz Subject: Re: [PATCH] lirc for 2.5/2.6 kernels - 20030802 Message-ID: <20030811185519.GI2627@elf.ucw.cz> References: <1060616931.8472.22.camel@defiant.flameeyes> <20030811163913.GA16568@bytesex.org> <20030811175642.GC2053@convergence.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030811175642.GC2053@convergence.de> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.3i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1738 Lines: 44 Hi! > > > We can drop /dev/lirc*, and use input events with received codes, but I > > > think that lircd is still needed to translate them into userland > > > commands... > > > > That translation isn't done by lircd, but by the lirc_client library. > > This is no reason for keeping lircd as event dispatcher, the input layer > > would do equally well (with liblirc_client picking up events from > > /dev/input/event instead of lircd). > > IMHO there's one problem: > > If a remote control has e.g. a "1" key this doesn't mean that a user > wants a "1" to be written into your editor while editing source code. > The "1" key on a remote control simply has a differnt _meaning_ than > the "1" key on your keyboard -- depending of course on what the user > thinks this key should mean. That only means that the key on remote should be labeled "KEY_PROGRAM1" not "KEY_1". > - users should be able to prevent remote keys from being fed into > the normal keyboard input queue; non lirc aware programs should > not recieve these events > (OTOH, if you use an IR keyboard...) This is same as multimedia keys on PS/2 keyboards. > - IR events should reach the applications independant of X keyboard > focus (well, maybe; the user should be able to decide) Again this is the same as multimedia keys on PS/2 keyboards. It may need to be solved, but we'd have to solve that anyway. Pavel -- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] - 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/