public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Hughes <hughsient-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Yu Luming <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>,
	Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>,
	linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	desktop_portables-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
	gnome-power-manager-list-rDKQcyrBJuzYtjvyW6yDsg@public.gmane.org
Subject: Re: [Desktop_portables] Re: [gpm] Untangling the sleep hotkey mess
Date: Mon, 09 Jan 2006 09:48:06 +0000	[thread overview]
Message-ID: <1136800086.19776.18.camel@localhost> (raw)
In-Reply-To: <200601091547.43439.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

On Mon, 2006-01-09 at 15:47 +0800, Yu Luming wrote:
> On Monday 09 January 2006 15:14, Karol Kozimor wrote:
> > 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...
> 
> I just want to say the hot-keys on keyboard for brightness, sound
> volume, display output switching won't change too much, 
> because user needs these buttons. And almost all laptops implement them.
> 
> For each ODM, if they implement hot-keys with dedicated ACPI devices and
> dedicated AML methods. It doesn't make any sense to change
> the name on new platforms for supporting same hot-keys.
> >
> >  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.
> >
> We need a hotkey spec for those well-know hot-keys now,
> Then, we can look forward to a clean hotkey driver in the future.

What spec would that be? Surely we *just* need a way to get the hotkeys
to userspace as early as possible? Be they KEY_BRIGHTNESSDOWN or some
random value like 0x140.
Why make this complicated, or am I missing a trick?

Thanks, Richard.

-
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

  parent reply	other threads:[~2006-01-09  9:48 UTC|newest]

Thread overview: 16+ 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
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 [this message]
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

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=1136800086.19776.18.camel@localhost \
    --to=hughsient-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=desktop_portables-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=gnome-power-manager-list-rDKQcyrBJuzYtjvyW6yDsg@public.gmane.org \
    --cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org \
    --cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@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