Re: [gpm] Untangling the sleep hotkey mess

On Mon, Jan 09, 2006 at 11:55:24AM +0800, Yu Luming wrote:

> 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. 

Toshiba have entirely changed their ACPI hotkey setup with the new Tecra 
range. The BIOS bears almost no resemblance to the previous one. Sony 
have changed their brightness handling code in newer machines - it seems 
to be impossible to change it through ACPI now.

Rule 1 of laptops: Vendors will do unpredictable and hard to understand 
things. They don't consider what they're providing to be well-known. As 
far as vendors are concerned, it's an internal implementation detail and 
they'll change it whenever they feel like it.

If Intel would like a single driver able to support all future laptops, 
then Intel need to specify hotkey behaviour in the ACPI spec and refuse 
to allow people to claim ACPI compliance unless they implement it. Until 
that happens there's no way of claiming that this stuff will just carry 
on working.

> >  In the Windows world, vendors can provide customised distributions on a
> >  per-laptop basis. That's not practical in the Linux world.
> My points is that if hotkey.c become sucessful, then linux won't need those 
> platform specific hotkey drivers for common hotkeys  such as brightness 
> control, volume control, and output switch.. 

It *will*, it's just they'll all be in a single driver that special 
cases a bunch of manufacturers. The fact that all of this is in one file 
rather than 20 doesn't make it inherently better.
Matthew Garrett | mjg59 srcf ucam org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]