From owner-cvs-all  Fri Nov 22 10:14:29 2002
Delivered-To: cvs-all@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0D7D137B401; Fri, 22 Nov 2002 10:14:28 -0800 (PST)
Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 87D0B43EBE; Fri, 22 Nov 2002 10:14:27 -0800 (PST)
	(envelope-from jhb@FreeBSD.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.12.6/8.12.6) with ESMTP id gAMIBDmV073001;
	Fri, 22 Nov 2002 10:11:13 -0800 (PST)
	(envelope-from jhb@repoman.freebsd.org)
Received: (from jhb@localhost)
	by repoman.freebsd.org (8.12.6/8.12.6/Submit) id gAMIBD6m073000;
	Fri, 22 Nov 2002 10:11:13 -0800 (PST)
Message-Id: <200211221811.gAMIBD6m073000@repoman.freebsd.org>
From: John Baldwin <jhb@FreeBSD.org>
Date: Fri, 22 Nov 2002 10:11:13 -0800 (PST)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/dev/acpica acpi_pcib_acpi.c
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

jhb         2002/11/22 10:11:13 PST

  Modified files:
    sys/dev/acpica       acpi_pcib_acpi.c 
  Log:
  According to the ACPI spec, the bus number of the child PCI bus of a host
  to PCI bridge can be read be evaluating the _BBN method of the host to PCI
  device.  Unfortunately, there appear to be some lazy/ignorant/moronic/
  whatever BIOS writers that return 0 for _BBN for all host to PCI bridges in
  the system.  On a system with a single host to PCI bridge this is not a
  problem as the child bus of that single bridge will be bus 0 anyway.
  However, on systems with multiple host to PCI bridges and l/i/m/w BIOS
  writers this is a major problem resulting in all but the first host to
  PCI bridge failing to attach.  So, this adds a workaround.
  
  If the _BBN of a host to PCI bridge is zero and pcib0 already exists
  and is not us, the we use _ADR to look up our PCI function and slot
  (we currently assume we are on bus 0) and use that to call
  host_pcib_get_busno() to try and extract our bus number from config
  registers on the host to PCI bridge device.  If that fails, then we make
  an evil assumption that ACPI's _SB_ namespace lays out the host to PCI
  bridges in ascending order and use our pcib unit number as our bus
  number.
  
  Approved by:    re
  
  Revision  Changes    Path
  1.26      +52 -7     src/sys/dev/acpica/acpi_pcib_acpi.c

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message