public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nate Lawson <nate@root.org>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: acpi@FreeBSD.org, ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: acpi-ca reports \_SB as a device
Date: Mon, 10 Jan 2005 13:03:27 -0800	[thread overview]
Message-ID: <41E2ED9F.1080602@root.org> (raw)
In-Reply-To: <971FCB6690CD0E4898387DBF7552B90E3900E6@orsmsx403.amr.corp.intel.com>

Ok, your rationale seems sound.  We'll keep the workaround of skipping 
such namespace system objects when scanning from the root.

-Nate

Moore, Robert wrote:
> For _SB_, this allows the _SB_._INI method to be run.
> 
> For _TZ, this allows notifies on the _TZ object.  Some ASL code does
> this.
> 
> 
> 
>>-----Original Message-----
>>From: Nate Lawson [mailto:nate@root.org]
>>Sent: Saturday, January 08, 2005 1:05 AM
>>To: ACPI Developers
>>Cc: acpi@FreeBSD.org
>>Subject: acpi-ca reports \_SB as a device
>>
>>If you call AcpiGetType on \_SB, you get "device" and \_TZ gives
>>"thermal".  I don't think this is valid since these are system scopes,
>>not devices and thermal zones.
>>
>>I found this while testing a patch that scans the whole namespace (\)
>>for devices.  It turns out some systems put PCI link devices (PNP0C0F)
>>in \, so we weren't probing them.

  reply	other threads:[~2005-01-10 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 18:12 acpi-ca reports \_SB as a device Moore, Robert
2005-01-10 21:03 ` Nate Lawson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-08  9:05 Nate Lawson

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=41E2ED9F.1080602@root.org \
    --to=nate@root.org \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=acpi@FreeBSD.org \
    --cc=robert.moore@intel.com \
    /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