Shi-Ying Irene Huang wrote:
> 4.2 Implementation
>
> Keymap of a keyboard device is to be patched with a number of hotkey
> keysyms
> provided in HAL's fdi file with "input.x11_options.addmap" option under
> certain matching conditions. Keyboard driver does the patching after
> it loads
> basic keymap table.
How is this "patching" done? Does it depend on private interfaces of the
keyboard driver, like memory layout of certain structures?
> Hotkey device driver is to be launched by HAL using
> "input.x11_options.mdriver"
> option under certain matching conditions.
Is mdriver a typo or are you introducing a new HAL keyword?
> Hotkey driver only patches keymap
> table of "core keyboard" device because the latter is not launched by HAL.
The virtual core keyboard is not setup by HAL, but once HAL input device support
is functional, all physical keyboards will be initiated by HAL.
> To avoid race condition, hotkeys generated from hotkey device do not
> participate in keymap table switch.
What interfaces in the X server are used to accomplish this?
> Imported Interfaces:
> --------------------
> /usr/lib/(amd64)/libsysevent.so Volatile
> /kernel/drv/(amd64)/acpi_drv Volatile
> /kernel/drv/(amd64)/acpi_toshiba Volatile
> ACPI hotkey sub class: Volatile
> "ESC_acpiev_display_switch" Volatile
> "ESC_acpiev_sleep" Volatile
> "ESC_acpiev_screen_lock" Volatile
> "ESC_acpiev_audio_mute" Volatile
Since those are cross-consolidation dependencies, you will need an ARC contract
for all those interfaces specifying how changes to them will be coordinated
between ON & X.
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
