From: Borislav Deianov <borislav-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ibm-acpi-0.6 - ACPI driver for IBM ThinkPad laptops
Date: Wed, 20 Oct 2004 19:38:43 -0700 [thread overview]
Message-ID: <20041021023843.GO17013@aero.ensim.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8405DCA922@pdsmsx403>
On Wed, Oct 20, 2004 at 11:18:08AM +0800, Yu, Luming wrote:
>
> I'm working on a generic hotkey driver, which will move configurable
> stuff to user space.
[snip]
> 1. add a new hotkey:
> echo "0 : _SB.VGA : _SB.VGA.LCD._BCM :0x86 : 0x86" >
> /proc/acpi/ev_config
How would user space know what devices and methods to use? In the
kernel, you can use HIDs where available, or check for specific
objects with acpi_get_handle(). Are you going to expose these to user
space somehow?
Boris
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-21 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 3:18 [PATCH] ibm-acpi-0.6 - ACPI driver for IBM ThinkPad laptops Yu, Luming
2004-10-21 2:38 ` Borislav Deianov [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-21 9:04 Yu, Luming
2004-10-19 5:59 Borislav Deianov
[not found] ` <20041019055951.GI17013-AKoe11r2kkOzaBltdDZI6w@public.gmane.org>
2004-10-19 23:52 ` Len Brown
2004-10-20 0:08 ` Len Brown
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=20041021023843.GO17013@aero.ensim.com \
--to=borislav-rn4veauk+akrv+lv9mx5uipxlwaovq5f@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-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