public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] PCI_BUSES_TO_SCAN off by 1?
Date: Tue, 22 Oct 2002 22:37:56 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805208@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701906005@msgid-missing>

>>>>> On Tue, 22 Oct 2002 16:20:52 -0600, Bjorn Helgaas <bjorn_helgaas@hp.com> said:

  Bjorn> To complete this thread, it looks like we can't do this.  My
  Bjorn> i2000 reports PCI root bridges for buses 0, 1, 2, and 3 via
  Bjorn> ACPI.  The 460GX chipset, including the CSRs for the AGP
  Bjorn> bridge, appears in config space on PCI bus 4.  ACPI doesn't
  Bjorn> tell us about bus 4, so we have to do the blind scan to find
  Bjorn> that stuff.

We no longer do the blind scan in 2.5.39 and it seems to work fine on
the big sur I tested it on:

	$ uname -v
	#33 SMP Sat Sep 28 10:58:07 PDT 2002
	$ dmesg|fgrep 'Probing PCI'
	PCI: Probing PCI hardware on bus (00)
	PCI: Probing PCI hardware on bus (01)
	PCI: Probing PCI hardware on bus (02)
	PCI: Probing PCI hardware on bus (03)
	PCI: Probing PCI hardware on bus (04)

Could it be that your i2000 has old firmware?  My big sur reports the
following firmware version (via Stephane's smbiosview utility):

	version      : W460GXBS2.86E.0117C.P09.200108091154

  --david


      parent reply	other threads:[~2002-10-22 22:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-30 20:45 [Linux-ia64] PCI_BUSES_TO_SCAN off by 1? Van Maren, Kevin
2002-08-30 21:11 ` Bjorn Helgaas
2002-08-30 21:14 ` Jack Steiner
2002-08-30 22:28 ` KOCHI, Takayoshi
2002-10-22 22:20 ` Bjorn Helgaas
2002-10-22 22:37 ` David Mosberger [this message]

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=marc-linux-ia64-105590709805208@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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