From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: Yu Luming <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Richard Hughes
<hughsient-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
gnome-power-manager-list-rDKQcyrBJuzYtjvyW6yDsg@public.gmane.org,
desktop_portables-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: [gpm] Untangling the sleep hotkey mess
Date: Mon, 9 Jan 2006 04:07:51 +0000 [thread overview]
Message-ID: <20060109040751.GA2880@srcf.ucam.org> (raw)
In-Reply-To: <200601091155.24380.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
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-1xO5oi07KQx4cg9Nei1l7Q@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
next prev parent reply other threads:[~2006-01-09 4:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 1:37 [gpm] Untangling the sleep hotkey mess Yu, Luming
2006-01-09 1:43 ` Matthew Garrett
[not found] ` <20060109014350.GA672-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2006-01-09 2:19 ` Yu Luming
[not found] ` <200601091019.01083.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2006-01-09 2:30 ` Matthew Garrett
[not found] ` <20060109023037.GA1316-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2006-01-09 3:13 ` Yu Luming
[not found] ` <200601091113.16092.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2006-01-09 3:27 ` Matthew Garrett
[not found] ` <20060109032717.GA2238-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2006-01-09 3:55 ` Yu Luming
[not found] ` <200601091155.24380.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2006-01-09 4:07 ` Matthew Garrett [this message]
2006-01-09 7:14 ` [Desktop_portables] " Karol Kozimor
[not found] ` <20060109071439.GA31974-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2006-01-09 7:47 ` Yu Luming
[not found] ` <200601091547.43439.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2006-01-09 9:48 ` Richard Hughes
2006-01-09 10:04 ` Richard Hughes
2006-01-09 21:14 ` Dmitry Torokhov
[not found] ` <d120d5000601091314g7cef73fk445976b14c549a04@mail.gmail.com>
2006-01-09 21:40 ` Matthew Garrett
[not found] ` <20060109214050.GA19974@srcf.ucam.org>
2006-01-09 21:52 ` Dmitry Torokhov
[not found] ` <d120d5000601091352m19ba5eb0n80c462cba49bd2a6@mail.gmail.com>
[not found] ` <d120d5000601091352m19ba5eb0n80c462cba49bd2a6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-01-09 22:04 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2006-08-31 1:49 Brown, Len
2006-08-31 2:53 ` Dmitry Torokhov
2006-08-31 3:03 ` Len Brown
[not found] ` <200608302303.38458.len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2006-08-31 3:07 ` Dmitry Torokhov
2006-09-18 7:55 ` Richard Hughes
[not found] ` <1158566150.2332.14.camel-Qvr7v16j6+Ap96r9Hs7rR1Kr0EmMEXJSn9A1Ff6Mc9Q@public.gmane.org>
2006-09-18 15:17 ` Dmitry Torokhov
2006-09-18 17:52 ` Richard Hughes
2006-07-26 23:41 Brown, Len
2006-07-26 23:52 ` Matthew Garrett
2006-07-27 4:12 ` Dmitry Torokhov
2006-01-07 17:24 Matthew Garrett
2006-01-08 12:58 ` [gpm] " Richard Hughes
2006-01-08 13:47 ` Matthew Garrett
[not found] ` <20060108134744.GA21538-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2006-01-08 14:13 ` Richard Hughes
2006-01-09 1:10 ` Yu Luming
2006-01-09 1:21 ` Richard Hughes
2006-01-09 1:14 ` Richard Hughes
2006-01-09 5:07 ` Dmitry Torokhov
[not found] ` <200601090007.43578.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2006-01-09 5:24 ` Matthew Garrett
2006-01-09 9:43 ` Richard Hughes
[not found] ` <20060109052407.GA4213@srcf.ucam.org>
[not found] ` <20060109052407.GA4213-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2006-01-09 6:09 ` Dmitry Torokhov
[not found] ` <200601090109.05791.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2006-01-09 9:44 ` Richard Hughes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060109040751.GA2880@srcf.ucam.org \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=desktop_portables-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=gnome-power-manager-list-rDKQcyrBJuzYtjvyW6yDsg@public.gmane.org \
--cc=hughsient-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox