| 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
| ||
|
Message-ID: <20071016130053.GA20010@srcf.ucam.org> Date: Tue, 16 Oct 2007 14:00:54 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: Henrique de Moraes Holschuh <hmh@....eng.br> Cc: Jeremy Katz <katzj@...hat.com>, linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org, davej@...hat.com Subject: Re: [PATCH] Map volume and brightness events on thinkpads On Mon, Oct 15, 2007 at 07:07:37PM -0200, Henrique de Moraes Holschuh wrote: > And the input subsystem maintainer has made it extremely clear in various > threads that the input devices are *not* to be used as a notification > service for on-screen-display or other such stuff. If you send volume and > brightness *key* events to userspace, it is supposed to act on them and > raise/lower brightness/volume, which is the wrong thing to do on thinkpads. > Never mind that HAL is ignoring the input maintainer's directions and > violating this. Reality disagrees. There are already several cases where notifications are sent via the keyboard controller, such as the wireless and touchpad disable keys on my HP. There are Dells that do the same for brightness keys. Unless you want to make the argument that sending keyboard controller events through the input layer is the wrong thing to do, it's impossible to standardise on a setup where we never see notifications through it. -- 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/
Powered by blists - more mailing lists