Re: [Desktop_portables] Re: [gpm] Untangling the sleep hotkey mess

[Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>]

Thus wrote Yu Luming:
> >From practical point of view,  the acpi hotkey won't change for a quite 
> long period. For example, I cannot find too much changes on acpi hotkey from
> Thinkpad T21 and Thinkpad T42.  And, I don't see any reason for ODM to 
> change their well-know ACPI device PNP ID and well-know AML methods names for
> acpi hotkey on new platfrom, because they can just implement any platform 
> changes in AML code. 

Tell me more...

There's already 3 or 4 major variations of method layout for ASUS laptops
hotkey device, subtle differences like method name changes notwithstanding.
One of the reasons the driver's development lags so much is that the
support code has become such a mess. I really wish their BIOS teams would
settle on one scheme, and there was a point when I thought they'd done just
that, but in the end it just didn't happen.

Personally, I'd love to see all the model support code moved to userspace,
and while I think it might just be possible using the generic driver, I
still didn't manage to make the necessary changes.

So as not to be completely off-topic: users expect (and I'm speaking from
experience here) the buttons to be able to generate both system-wide (as in
suspend) and per-session (as in launch firefox) events and given that, I
think uinput is a good direction, provided we keep acpid or at least a
functional replacement.

Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html