public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] Fix _STA checking in acpi_bus_add
Date: Mon, 26 Jan 2004 09:15:02 -0700	[thread overview]
Message-ID: <200401260915.02308.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <1074919407.14755.6.camel-D2Zvc0uNKG8@public.gmane.org>

On Friday 23 January 2004 9:43 pm, Len Brown wrote:
> Applied.

Thanks!

> ps. did you find this because you've got a system where the actual
> get_status failed, or the _STA returned !present and that was ignored?

Umm...  let's see... the latter, I guess.  I found this because
ia64 linux was complaining about some invalid ranges in _CRS on
the Intel Tiger box.  It turned out that the ranges all had
_LEN==0, and we should have been ignoring them anyway.

But somebody from HP-UX noticed that we were complaining about
ranges on a bridge that should have been !present according to
the _STA.

Now that you've applied this, we have to resolve the next issue
I found while investigating this: the chipset config interface
(CBN/CSFF) is reported as _STA==0x8, i.e., "functioning, but not
present".  We can't find anything in the spec on how to interpret
this.

The problem here is that since CBN/CSFF is !present, we won't
enumerate devices under them.  Therefore, we will no longer find
the AGP bridge on Big Sur.

Bjorn



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  parent reply	other threads:[~2004-01-26 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 23:35 [PATCH] Fix _STA checking in acpi_bus_add Bjorn Helgaas
     [not found] ` <200401021635.25419.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2004-01-12 19:47   ` Bjorn Helgaas
2004-01-24  4:43   ` Len Brown
     [not found]     ` <1074919407.14755.6.camel-D2Zvc0uNKG8@public.gmane.org>
2004-01-26 16:15       ` Bjorn Helgaas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-26 17:20 Brown, Len

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=200401260915.02308.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@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