From: Paul Ionescu <paul-f7LjuT9/YZU@public.gmane.org>
To: acpi
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
alex.williamson-VXdhtT5mjnY@public.gmane.org
Subject: Re: [RFC] filling in ACPI files in sysfs
Date: Thu, 08 Apr 2004 00:36:21 +0300 [thread overview]
Message-ID: <1081373781.23176.30.camel@t40> (raw)
Hi Alex,
I patch-ed a 2.6.5 kernel, and boot-ed an IBM T30 Thinkpad Laptop.
It looks nice at first sight, and now I want _Qxx methods in /EC to play
with :)
What I found strange is the following behaviour:
If I boot with my second battery inserted, I have the corresponding
entries for BAT1 in /proc/acpi/battery and /sys/.../EC/BAT1
If I boot without my second battery inserted, and I insert it later on,
I don't have the corresponding BAT1 directory for it in /proc/acpi and
/sys/.../EC/.
And this is true for other acpi devices too.
I think that the problem is that it does not (yet) update the list of
active devices in real time, but uses the list with devices detected at
boot time.
Anyway, this is a good start, and I am waiting for more patches to test.
Thanks,
Paul
> Seems like it's about time the ACPI sysfs namespace started >doing
>more than looking pretty. Here's a stab at adding in some basic
>functionality. I'd like to get some feedback before I start filling in
>the more complicated features. This has been lightly tested on a
>sampling of HP ia64 boxes. Does this seem like a reasonable start?
>Comments and reports from other platforms welcome. Thanks,
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-04-07 21:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 21:36 Paul Ionescu [this message]
[not found] ` <1081373781.23176.30.camel-LjAuIDrFwz0@public.gmane.org>
2004-04-07 22:13 ` [RFC] filling in ACPI files in sysfs Alex Williamson
[not found] ` <1081376023.2748.15.camel-Wmjt7DDUnIVxnVILBQAtiA@public.gmane.org>
2004-04-08 5:56 ` Paul Ionescu
2004-04-08 15:46 ` Paul Ionescu
[not found] ` <1081439217.23176.70.camel-LjAuIDrFwz0@public.gmane.org>
2004-04-08 16:41 ` Alex Williamson
2004-04-08 16:53 ` Paul Ionescu
2004-04-08 17:25 ` Matthew Wilcox
[not found] ` <20040408172548.GH18329-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2004-04-08 17:33 ` Alex Williamson
[not found] ` <1081536801.26073.120.camel@t40>
[not found] ` <1081537175.2694.11.camel@patsy.fc.hp.com>
[not found] ` <1081537175.2694.11.camel-Wmjt7DDUnIVxnVILBQAtiA@public.gmane.org>
2004-04-10 10:03 ` Paul Ionescu
[not found] ` <1081536489.23178.113.camel@t40>
[not found] ` <1081537087.2694.8.camel@patsy.fc.hp.com>
[not found] ` <1081537087.2694.8.camel-Wmjt7DDUnIVxnVILBQAtiA@public.gmane.org>
2004-04-10 11:36 ` Paul Ionescu
-- strict thread matches above, loose matches on Subject: below --
2004-04-08 8:14 Paul Ionescu
[not found] ` <20040408081455.52935.qmail-BuYeCebq3BaA/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2004-04-08 14:36 ` Alex Williamson
2004-04-06 15:56 Alex Williamson
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=1081373781.23176.30.camel@t40 \
--to=paul-f7ljut9/yzu@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=alex.williamson-VXdhtT5mjnY@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