HAL, sound cards and laptops
Lennart Poettering
mzuny at 0pointer.de
Mon Aug 7 16:21:59 PDT 2006
On Mon, 07.08.06 23:25, Matthew Garrett (mjg59 at srcf.ucam.org) wrote:
> Sounds like an argument for standardisation. How about:
>
> diff --git a/include/linux/input.h b/include/linux/input.h
> index b3253ab..5812552 100644
> --- a/include/linux/input.h
> +++ b/include/linux/input.h
> @@ -348,6 +348,7 @@ #define KEY_SAVE 234
> #define KEY_DOCUMENTS 235
>
> #define KEY_BATTERY 236
> +#define KEY_WIRELESS 237
>
> #define KEY_UNKNOWN 240
>
> to the kernel and then set the correct mapping based on DMI data?
Sounds like a good idea. Although I would add seperate KEY_WIRELESS,
KEY_WLAN, KEY_BLUETOOTH definitions (as some laptops have this
seperately and others all-in-one as in
KEY_WIRELESS=KEY_BLUETOOTH+KEY_WLAN).
And while we are at it: KEY_POWERPLUG, KEY_POWERUNPLUG would be cool
too, because my MSI S270 passes these events as keypress events as
well.
I will prepare a patch and send it to the Linux input subsystem maintainer.
BTW: is there any project that sets scan code translation tables based
on DMI data? A while ago I wrote a tool "keyfuzz" which something like
this, but lacks DMI integration
(http://0pointer.de/lennart/projects/keyfuzz/). I might work on
expanding it adding DMI support, but only if there is no other project
around doing just that. A quick search on google didn't yield anything
useful.
Lennart
--
Lennart Poettering; lennart [at] poettering [dot] net
ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.net/lennart/
More information about the hal
mailing list