HAL, sound cards and laptops
mzuny at 0pointer.de
Mon Aug 7 16:52:08 PDT 2006
On Tue, 08.08.06 00:25, Matthew Garrett (mjg59 at srcf.ucam.org) wrote:
> > 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).
> Hm. Unfortunately we start running out of space quite quickly around
> then. This is probably going to have to be brought up with the input
Apparently the rfkill patch already defines KEY_RFKILL. So no point
in defining our own KEY_WIRELESS. The other two keys still do make
> > 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.
> hotkey-setup in Debian and Ubuntu. It's just a bunch of shell scripts,
> but it works nicely.
Looks frigthening. But good enough, I guess.
Lennart Poettering; lennart [at] poettering [dot] net
ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.net/lennart/
More information about the hal