linux-kernel - Re: [RFC PATCH] Quickstart Button ACPI driver to serve PNP0C32 ACPI devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100528211156.GA3883@srcf.ucam.org>
Date:	Fri, 28 May 2010 22:11:56 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Thomas Renninger <trenn@...e.de>
Cc:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-input@...r.kernel.org, Angelo Arrifano <miknix@...il.com>
Subject: Re: [RFC PATCH] Quickstart Button ACPI driver to serve PNP0C32
	ACPI devices

On Fri, May 28, 2010 at 07:40:09PM +0200, Thomas Renninger wrote:

> 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.
> There should be 2 situations that perfectly are triggered via userspace:

They're logically buttons, so the right mechanism is for them to be 
configured via the standard keymap ioctls. There's already 
infrastructure for setting this via udev - see /lib/udev/keymaps on 
recent systems. That should let you avoid the need to 
unregister/reregister.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/