From: Alan Hourihane <alanh@fairlite.demon.co.uk>
To: linux-acpi@vger.kernel.org
Subject: obtaining acpi details outside of drivers/acpi
Date: Thu, 06 Sep 2007 11:16:09 +0100 [thread overview]
Message-ID: <1189073769.7969.32.camel@localhost> (raw)
I'm looking at the currently exported function calls to other kernel
modules to obtain ACPI data.
For example, if I want to access _DOD for graphics, the pathname would
be something like...
\\_SB_.PCI0.GFX0._DOD
And I'm currently doing this...
status = acpi_evaluate_object(NULL, PATHNAME, NULL, &buffer);
where PATHNAME is the path above.
But there's no guarantees that it's called PCI0, or even GFX0.
What's the best way to search the namespace and get this data ??
Alan.
next reply other threads:[~2007-09-06 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 10:16 Alan Hourihane [this message]
2007-09-06 11:43 ` obtaining acpi details outside of drivers/acpi Len Brown
2007-09-06 11:47 ` Alan Hourihane
2007-09-06 13:22 ` Len Brown
2007-09-06 13:27 ` Alexey Starikovskiy
2007-09-06 13:53 ` Alan Hourihane
2007-09-06 13:57 ` Alan Hourihane
2007-09-06 14:17 ` Alexey Starikovskiy
2007-09-06 14:33 ` Alan Hourihane
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=1189073769.7969.32.camel@localhost \
--to=alanh@fairlite.demon.co.uk \
--cc=linux-acpi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).