From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752907Ab0E1SBk (ORCPT ); Fri, 28 May 2010 14:01:40 -0400 Received: from mail-pw0-f46.google.com ([209.85.160.46]:54126 "EHLO mail-pw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751638Ab0E1SBg (ORCPT ); Fri, 28 May 2010 14:01:36 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=i+3WaicMIudncXxHPgC0ck4dRP5YNAt9zl4fT9yttW0/Hf9fvWg0P8sxEjJETRxCJP LJkTlKEFA9cKocpLuyRUmiuXP6ZDiRsHzlpfS4MwsrgqcA4VrNNMkEXjE1bIvnxKzvoy l87AtFYB2wRj9yUMtIL7xnnjv6T+8TnSFyLe8= Date: Fri, 28 May 2010 11:01:03 -0700 From: Dmitry Torokhov To: Thomas Renninger Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-input@vger.kernel.org, Angelo Arrifano Subject: Re: [RFC PATCH] Quickstart Button ACPI driver to serve PNP0C32 ACPI devices Message-ID: <20100528180103.GA2905@core.coreip.homeip.net> References: <201005281940.09925.trenn@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201005281940.09925.trenn@suse.de> User-Agent: Mutt/1.5.20 (2009-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 28, 2010 at 07:40:09PM +0200, Thomas Renninger wrote: > Hi, > > if you have a recent Microsoft Office format reader you find some > documentation here: > http://www.microsoft.com/whdc/system/platform/firmware/DirAppLaunch.mspx > > I finally got it converted and these should be readable in OpenOffice as well: > ftp.suse.com/pub/people/trenn/hotstart_quickstart_docu > > The idea of these buttons is that they are undefined from BIOS/kernel > point of view. Userspace has to map a functionality to them. > Therefore the idea to modify the input event keycode via sysfs file. What s wrong with using EVIOCSKEYCODE to adjust the mapping. Note that the issue of handlers not re-binding after keymap change should be solved regardless. > There should be 2 situations that perfectly are triggered via userspace: > - DMI match (or similar) and assign the correct buttons on the known > machine. I know that hal could do this rather well and had dmi > tables pre-defined. AFAIK hal is already obsolete? What userspace > tools/lists would be best to ask? udev/hal remap keys on laptop keyboards, they should have facilities to do that here as well. > > - If the button is undefined, a higher level userspace X application > could ask the user to set it to something useful. For this to > happen the usage id has to be passed somehow through the input > layer. Not sure how realistic such an implementation is and what > is still needed in X to make this happen. Yes, KEY_UNKNOWN is expected to cause such behavior. -- Dmitry