From: Pavel Troller <patrol-FIBU9iiavH4@public.gmane.org>
To: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Generic hotkey driver for dock ejecting
Date: Sun, 28 Aug 2005 06:37:51 +0200 [thread overview]
Message-ID: <20050828043751.GA7644@tangens.sinus.cz> (raw)
In-Reply-To: <20050827235547.GA18990-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
> It might actually be nice to have an interface that allows userspace to
> call arbitrary ACPI methods at any time, rather than simply in response
> to hotkey events.
>
Hi!
Such interface does exist! It's Alex Williamson's dev_acpi driver, which
loads as a kernel module, and an userspace utility.
I've written a small "acpicall" program based on his own utilities, allowing to
call any method without arguments or with a single integer. BTW, there is
a program called "acpiundock" in his package; did You Try it ? I didn't,
because I don't have nothing to dock/undock.
I think that the dev_acpi module is a hot candidate for inclusion to the
kernel tree, it exposes /dev/acpi character device, which interacts with the
ACPI subsystem by ioctls and read/write and allows really nice ACPI space
access.
It can be found at
http://free.linux.hp.com/~awilliam/acpi/dev_acpi/dev_acpi-20040803.tar.bz2 ;
I've sent him a patch which registers the driver with sysfs, thus automatically
creating the /dev/acpi node, but he didn't make a new release containing it yet,
I can send it if You want, as well as my experimental acpicall utility source.
With regards, Pavel Troller
> --
> Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-28 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 14:43 Generic hotkey driver for dock ejecting Yu, Luming
2005-08-27 23:55 ` Matthew Garrett
[not found] ` <20050827235547.GA18990-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2005-08-28 4:37 ` Pavel Troller [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-26 15:25 Matthew Garrett
[not found] ` <20050826152548.GA12991-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2005-08-27 12:24 ` Pavel Machek
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=20050828043751.GA7644@tangens.sinus.cz \
--to=patrol-fibu9iiavh4@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@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