RE: generic ACPI video and hotkey drivers vs. platform-specificdrivers

RE: generic ACPI video and hotkey drivers vs. platform-specificdrivers

[Yu, Luming]

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.

Thanks
Luming 

>-----Original Message-----
>From: Timo Hoenig [mailto:thoenig@nouse.net] 
>Sent: 2005年3月4日 17:35
>To: Brown, Len
>Cc: John Belmonte; Andrew Morton; Karol Kozimor; Yu, Luming; 
>toshiba_acpi@memebeam.org; vojtech@suse.com; Stelian Pop; ACPI 
>Developers
>Subject: Re: generic ACPI video and hotkey drivers vs. 
>platform-specificdrivers
>
>Hi,
>
>thanks for opening this discussion.
>
>On Thu, 2005-03-03 at 16:08 -0500, Len Brown wrote:
>>It is great that programmers -- sometimes with little or no
>
>[...]
>
>>As I've said before, it is fine with me for exotic drivers
>>to handle exotic hardware -- nobody wants to muck-up generic
>>code for a few exotics.  But we need a design where
>>standard systems we've never heard of "just work";
>>and we need to make the use, administration, and support
>>of exotic systems as much like standard sytems
>>as possible.
>
>Yes.  What do you think of providing an API for specific drivers as
>proposed by Stelian on acpi-devel before?  We then could move the
>specific drivers out of the ACPI maintree.
>
>Regarding hotkeys for example we could provide an interface which is
>used by the specific drivers to report events.  Such events would be
>reported into user-space like the one's triggered by the 
>generic driver.
>Perhaps by using the Linux input core.  But I guess this still needs to
>be discussed thoroughly.
>
>[...]
>
>>I believe that Bruno's generic video driver (in tree)
>>is a step in this direction.  I believe that Luming's
>>generic hot key driver (on list, but not yet in tree)
>>is a step in this direction.  Are either of these
>>"final"?  heck no, but I'm confident that they're
>>heading us in the right direction.
>>
>>I plan to pull Luming's hot-key driver into the ACPI patch
>>soon -- the only reason we didnt' do it earlyer is because
>>the previous version would have immediately broken the
>>existing platform specific drivers...
>
>Luming, can you please give some comment on the state of your driver?
>
>>We also need to think about the kernel<->user interface
>>we've currently got.
>>
>>We need to think through the suggestion that hot keys
>>should appear to Linux like other keyboard keys -- and
>>wind their way throught the input layer.  I think the important
>>thing will be what the user or administrator has to do in
>>order to map which keys to which functions; and if this
>>can work automatically without a call to 1-800-distro.
>
>I will write some document which will pinpoint the current problems
>depending on vendor and/or machine.  For that purpose I'll have quite a
>few machines provided by the SUSE Labs. For other systems I will call
>users for help.
>
>[...]
>
>We still have to face the fact that we will not be able to cover all
>systems by a generic driver.  Vendors are -- and will -- go their own
>way. See Sony and Toshiba for example.  Since we do not want to clutter
>the generic driver with exceptions we will have to find a proper design
>for implementing specific drivers.
>
>Maybe the number of systems which require a specific driver will
>decrease -- but never to zero.
>
>I've added Andrew and John to cc.
>
>See you,
>
>  -- Timo
>
>..............................................................
>Timo Hönig <thoenig at nouse dot net>
>..................................................:: gpg ::...
>Fingerprint: 0998 0ACA A1D2 2612 4D96 DD8B E03F 084B B305 4066
>

Re: RE: generic ACPI video and hotkey drivers vs. platform-specificdrivers

[Matthew Garrett]

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