Now that /proc/acpi/events will soon be removed, are there any plans to
port acpid to the evdev/netlink interfaces?
thanks
tom
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majord
Oops, the link to the tarball:
http://dbservice.com/ftpdir/tom/acpid-ng.tar.gz
tom
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
What is it?
=
An acpi deamon that processes events from various sources, passes these
to scripts for further processing and also broadcasts dbus events.
Currently it contains drivers for (generic-)netlink and evdev event
sources. Configuration and event processing is done in Lua,
Andrew Morton wrote:
> 2.6.24-rc4 on a Lenovo t61p, using FC8 config.
>
> echo mem > /sys/power/state while running X.
>
> It appears to suspend OK but then it instantly resumes and runs
> OK except the display is blank.
http://bugzilla.kernel.org/show_bug.cgi?id=9258
I have a X61 tablet, and t
Len Brown wrote:
I am okay with defining OSI strings for the benefit of BIOS vendors that
need to know about Linux capabilities. But the string must
identify that specific capability (or lack of a capability).
Is there a chance this will be added to future ACPI specs, or have it
stan
Len Brown wrote:
On Sunday 20 January 2008 07:03, Tomas Carnecky wrote:
Len Brown wrote:
I am okay with defining OSI strings for the benefit of BIOS vendors that
need to know about Linux capabilities. But the string must
identify that specific capability (or lack of a capability).
Is
Thomas Renninger wrote:
Hi,
please correct me if I am wrong or missed something:
osi=linux was an ability for vendors to provide Linux specific BIOS
updates/quirks.
_OSI("Linux") returned true until kernel version 2.6.23 (included?).
This has been replaced by rather huge black+white lists (at
Lukas Hejtmanek wrote:
On Mon, Feb 25, 2008 at 06:01:13PM -0300, Henrique de Moraes Holschuh wrote:
Not even over the new netlink socket? Or the thinkpad-acpi input device?
how can I check this?
A while ago I worked on a new acpi daemon that could receive events from
both netlink and /dev/