Date: Mon, 12 Dec 2005 00:13:15 -0800
From: Andrew Morton <akpm@osdl.org>
To: Stefan Seyfried <seife@suse.de>
Cc: vojtech@suse.cz, dtor_core@ameritech.net, luming.yu@intel.com,
       torvalds@osdl.org, linux-kernel@vger.kernel.org, len.brown@intel.com,
       bero@arklinux.org
Subject: Re: [git pull 02/14] Add Wistron driver
Message-Id: <20051212001315.0e2c64f1.akpm@osdl.org>
References: <20051211224059.GA28388@midnight.suse.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1414
Lines: 26

Stefan Seyfried <seife@suse.de> wrote:
>
> In article <20051211224059.GA28388@midnight.suse.cz> you wrote:
> > On Sun, Dec 11, 2005 at 01:10:13PM +0000, Bernhard Rosenkraenzer wrote:
> >> I think routing them to the input layer makes most sense because they are keys 
> >> like everything else -- of course hacking acpid to pass on ACPI key events to 
> >> Xorg via the XTest extension is not exactly hard, but that would break the 
> >> keys in text mode (who knows, maybe someone wants to map his mail key to 
> >> "mutt[RETURN]"?), and of course launching an application from acpid is a bit 
> >> hard (acpid runs as root --> need to figure out which user is pressed the 
> >> button, switch user IDs, find the correct X display if any, .....) if it's an 
> >> input event, solutions for the expected functionality already exist - e.g. 
> >> khotkeys.
> > 
> > You also can hack acpid to use uinput to feed the events back to the
> > input subsystem, but I agree with you that going there directly is
> > probably the best way to go.
> 
> pcc_acpi already does this successfully and is a pleasure to use.

That's not in the tree any more.   Did something replace it?
-
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/