From: Corey Minyard <minyard@acm.org>
To: "Brown, Len" <len.brown@intel.com>
Cc: linux-acpi@vger.kernel.org, ambx1@neo.rr.com,
Matt Domsch <Matt_Domsch@dell.com>
Subject: Re: Extra ACPI objects from an acpi PNP device?
Date: Wed, 10 May 2006 15:53:45 -0500 [thread overview]
Message-ID: <446252D9.7090407@acm.org> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB669C15D@hdsmsx411.amr.corp.intel.com>
Brown, Len wrote:
>>I have a situation where I need to get an ACPI device. The PNP system
>>seems like the way to go for this, but I need some extra objects from
>>the ACPI namespace for this device (_IFT and _SRV to be specific,
>>supposidly added in ACPI 3.0). There doesn't seem to be a clean way to
>>do this right now. What would be the best way to get these?
>>
>>
>
>If your code knows about specific AML methods, then it is by-definition,
>ACPI-aware, and can't be hidden (completely) behind PNP.
>
>
True, but the PNP stuff does a lot of the work :)
>Either that, or some ACPI-aware code needs to exist to intervene to
>allow your code to know know anything about ACPI.
>
>
I was thinking of some way to determine if it is ACPI and get the
handle, or a new call to get resources.
>So you could make it ACPI aware like 8250_acpi.c was, before it was
>deleted...
>
>
So just use ACPI directly. This will bypass the PNP port reservation
for that particular ACPI device, I assume.
Thanks,
-Corey
next prev parent reply other threads:[~2006-05-10 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 19:54 Extra ACPI objects from an acpi PNP device? Brown, Len
2006-05-10 20:53 ` Corey Minyard [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-10 19:14 Corey Minyard
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=446252D9.7090407@acm.org \
--to=minyard@acm.org \
--cc=Matt_Domsch@dell.com \
--cc=ambx1@neo.rr.com \
--cc=len.brown@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.