From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [PATCH] Input: document the proper usage of EV_KEY and KEY_UNKNOWN Date: Fri, 1 Jun 2007 00:33:27 +0100 Message-ID: <20070531233326.GA1947@srcf.ucam.org> References: <11802004861625-git-send-email-hmh@hmh.eng.br> <20070531005305.GC6883@khazad-dum.debian.net> <200705310033.51230.dtor@insightbb.com> <20070531222814.GB4076@khazad-dum.debian.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20070531222814.GB4076@khazad-dum.debian.net> Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: Henrique de Moraes Holschuh Cc: Dmitry Torokhov , Richard Hughes , linux-acpi@vger.kernel.org, linux-input@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org List-Id: linux-input@vger.kernel.org On Thu, May 31, 2007 at 07:28:14PM -0300, Henrique de Moraes Holschuh wrote: > We have all the pieces needed to have sane, generic userland keyboard handling > in place for a while now, but it was not sufficiently documented (or used!). > > If EV_KEY input drivers always generate scan codes that can be used to > reprogram their keycode maps, and always generate EV_MSC MSC_SCAN events when > they output an EV_KEY KEY_UNKNOWN event, userspace can trap those and feed it > to a generic helper that can ask the user to assign a key code and function to > that key. I still disagree that this is the best approach. Userspace already has the functionality to map keys if they produce a keycode. Producing KEY_UNKNOWN would require the implementation of a stack of extra code. -- Matthew Garrett | mjg59@srcf.ucam.org