Darren Kenny wrote:
> A similar mechanism was provided using hal/libhal on Linux, and there was 
> quite
> a bit of traffic on the hal aliases at freedesktop.org to create patches for
> such keys from people who had unsupported laptops.

Current Gnome shortcuts application is based on standand key grabing 
from X, not HAL.

Regards,
Kerry

> 
> I'm not saying that hal is the right place to do it, I believe they have 
> changed
> this again, but it did help in gaining feedback and quickly adding support for
> new laptop types.
> 
> So if this was made easy, it wouldn't just provide a w/around, but would also
> allow users to log bugs/defects with a diff that could be used to patch our
> sources ultimately.
> 
> Darren.
> 
> Nicolas Williams wrote:
>> On Sun, Jan 11, 2009 at 08:01:10PM -0800, Phi Tran wrote:
>>> Since there is no generic ACPI specification for other hotkeys, most
>>> vendors just define their own specific ACPI based hotkey method. This
>>> case will also add Toshiba specific ACPI hotkey method support for:
>>> 1. Fn + ESC: audio mute On/Off
>>> 2. Fn + F1: screen lock
>>> 3. Fn + F3: suspend to RAM(on S3 capable platform)
>>> 4. Fn + F8: wireless LAN On/Off
>>> 5. Fn + F9: touchPad On/Off
>>>
>>> Other vendor specific hotkey method support can be added in future after
>>> we get the related documentations.
>> Would it be possible to let users create their own set of hotkeys?  Even
>> if the hotkeys are burned into the HW, it'd be nice to be able to let
>> the user input each one and assign a symbol to each.  This would be a
>> good workaround for lack of support for a specific laptop.
>>
>> At base what I'm asking for is that it be possible to provide a list of
>> hotkeys and their symbolic mappings via a method other than an ELF
>> kernel module -- a text file, say, read at boot time or at ttymon/Xorg
>> start time (so the parsing could be done in user-land).
>>
>> Nico

Reply via email to