From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: RE: generic ACPI video and hotkey drivers vs. platform-specificdrivers
Date: Wed, 18 May 2005 17:51:39 +0100 [thread overview]
Message-ID: <1116435099.10344.58.camel@tyrosine> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84041AC149@pdsmsx403>
On Sun, 2005-03-06 at 22:02 +0800, Yu, Luming wrote:
> Please take a look at the prototype filed at http://bugzilla.kernel.org/show_bug.cgi?id=3887
> The basic idea is to supply interfaces to configure generic hotkey driver to make it work on any specific platform that requires the execution of some specific AML methods.
I've tried playing with this (why does it disable the existing drivers
all the time, rather than just when it's loaded?), but the documentation
seems to be lacking - I haven't figured out how to drive it at all. It'd
be really helpful to have a set of sample configurations to mimic the
behaviour of existing drivers.
I'm also not entirely clear on how userspace is meant to interface with
this. Am I right in thinking that it's something like the following:
a) register hotkey event
b) this causes event in /proc/acpi/event
c) userspace picks up on that and then triggers an acpi method that's
been registered beforehand
?
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
prev parent reply other threads:[~2005-05-18 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 14:02 generic ACPI video and hotkey drivers vs. platform-specificdrivers Yu, Luming
2005-05-18 16:51 ` Matthew Garrett [this message]
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=1116435099.10344.58.camel@tyrosine \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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