src/sys/i386/include/legacyvar.h, branch release/7.0.0_cvs

This commit was manufactured by cvs2svn to create tag

2008-02-24T05:45:17+00:00

'RELENG_7_0_0_RELEASE'.

This commit was manufactured to restore the state of the 7.0-RELEASE image.

Make the PCI code aware of PCI domains (aka PCI segments) so we can

2007-09-30T11:05:18+00:00

support machines having multiple independently numbered PCI domains
and don't support reenumeration without ambiguity amongst the
devices as seen by the OS and represented by PCI location strings.
This includes introducing a function pci_find_dbsf(9) which works
like pci_find_bsf(9) but additionally takes a domain number argument
and limiting pci_find_bsf(9) to only search devices in domain 0 (the
only domain in single-domain systems). Bge(4) and ofw_pcibus(4) are
changed to use pci_find_dbsf(9) instead of pci_find_bsf(9) in order
to no longer report false positives when searching for siblings and
dupe devices in the same domain respectively.
Along with this change the sole host-PCI bridge driver converted to
actually make use of PCI domain support is uninorth(4), the others
continue to use domain 0 only for now and need to be converted as
appropriate later on.
Note that this means that the format of the location strings as used
by pciconf(8) has been changed and that consumers of 
potentially need to be recompiled.

Suggested by:	jhb
Reviewed by:	grehan, jhb, marcel
Approved by:	re (kensmith), jhb (PCI maintainer hat)

Expose legacy_pcib_alloc_resource, and use it in the mptable pci bus

2005-09-17T23:57:53+00:00

implementation, like other routines in the legacy bus.

This should fix problems with resource allocation on MP systems without
ACPI enabled.

With pc98/include, we can have pc98 and i386 specific bus space

2005-04-03T17:47:03+00:00

implementations in their own files named $MACHINE/include/bus.h.  Copy
the contents appropriately.

Make the legacy_pcib_attach() function static.

2004-05-03T14:49:43+00:00

- Rename nexus_pcib to legacy_pcib. I've been meaning to do this for a

2003-06-06T17:56:30+00:00

  while after the legacy device was added since this driver hangs from
  legacy and not nexus.
- Make several methods non-static so they can be reused in a mptable
  host -> pci bridge driver that will be added at a later date.
- Let legacy_pcib() use pcibios_pcib_route_interrupt() directly instead of
  wrapping it in a private function.  Originally, I thought I was going to
  have the nexus_pcib() driver make a runtime APIC vs. 8259A check and call
  the appropriate routing method (MPTable vs. PIR) that way, but it ended
  up being cleaner to make nexus_pcib() just work with PIR and have a
  separate host -> pci bridge driver for the mptable/apic case.

Add a new legacy(4) device driver for use on machines that do not have

2002-09-23T15:50:06+00:00

ACPI or for when ACPI support is disabled or not present in the kernel.
Basically, the nexus device is now split into two with some parts
(such as adding default ISA, MCA, and EISA busses if they aren't found
as well as support for PCI bus device ivars) being moved to the legacy
driver.

Use the __BUS_ACCESSOR macro for NEXUS_ACCESSOR

2002-08-20T13:50:17+00:00

instead of rolling our own implementation.

Reviewed by:	tmm

Get out the roto-rooter and clean up the abuse of nexus ivars by the

2000-09-28T00:37:32+00:00

i386/isa/pcibus.c.  This gets -current running again on multiple host->pci
machines after the most recent nexus commits.  I had discussed this with
Mike Smith, but ended up doing it slightly differently to what we
discussed as it turned out cleaner this way.  Mike was suggesting creating
a new resource (SYS_RES_PCIBUS) or something and using *_[gs]et_resource(),
but IMHO that wasn't ideal as SYS_RES_* is meant to be a global platform
property, not a quirk of a given implementation.  This does use the ivar
methods but does so properly.  It also now prints the physical pci bus that
a host->pci bridge (pcib) corresponds to.