From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Hiroshi Miura <miura-yiisDzvROlQdnm+yROfE0A@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: generic hotkey driver
Date: Tue, 7 Sep 2004 10:49:10 +0200 [thread overview]
Message-ID: <20040907084910.GA27074@hell.org.pl> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84056B57EE@pdsmsx403>
Thus wrote Yu, Luming:
> We don't need to care about the format of event. Since it is
> configurable,
> we just need to understand the internal meaning. So maybe we
> need to define the internal event number, which stands for a
> special purpose. such as:
>
> 001 turn off display
> 002 inc brightness
> 003 dec brightness
> 004 s3
> ......
Hmm, ASUS laptops support some 16 distinct events, I don't see your
solution maintainable.
> >Lcd brightness control is defined in ACPI spec apendix.
> >I'm starting implement that.
> Be careful, there has a video extension driver
> filed at http://bugzilla.kernel.org/show_bug.cgi?id=1944
Sadly, most OEMs don't give a damn about the spec and implement this in
their own way.
> >Bluetooth, dock, and other device settings are not common.
> >So these may be implement in each extra drivers. eg)
> >ibm_acpi.c has these functions.
> But , it is still meaningful to standardize the event format.
Sure, but what can be done apart from agreeing on the name of the first
field?
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
next prev parent reply other threads:[~2004-09-07 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 8:14 generic hotkey driver Yu, Luming
2004-09-07 8:49 ` Karol Kozimor [this message]
2004-09-14 20:42 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2004-09-08 15:42 Yu, Luming
2004-09-07 7:54 Yu, Luming
2004-09-07 13:13 ` John Belmonte
2004-09-01 10:32 Yu, Luming
2004-09-03 11:16 ` Hiroshi Miura
2004-09-04 8:45 ` John Belmonte
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=20040907084910.GA27074@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=miura-yiisDzvROlQdnm+yROfE0A@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