> > For those you would have bus->ops pointing to the old port code, > > for the others to the mmconfig code. > > Well, for that, I'll have to set the bus ops when they are discovered. > So the same callback I mentioned can be used for that (due to the need > to check the ranges in the MCFG table). I'll work on that too. > > Does the K8 box just not have MCFG entries for the northbridge busses? I believe so. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- [PATCH 00/04] PCI: add proper MCFG support to let AMD boxes support MMCONFIG
- From: Greg KH <[email protected]>
- Re: [PATCH 01/04] PCI: add proper MCFG table parsing to ACPI core.
- From: Greg KH <[email protected]>
- [PATCH 02/04] PCI: use the MCFG table to properly access pci devices (i386)
- From: Greg KH <[email protected]>
- Re: [PATCH 02/04] PCI: use the MCFG table to properly access pci devices (i386)
- From: Andi Kleen <[email protected]>
- Re: [PATCH 02/04] PCI: use the MCFG table to properly access pci devices (i386)
- From: Greg KH <[email protected]>
- Re: [PATCH 02/04] PCI: use the MCFG table to properly access pci devices (i386)
- From: Andi Kleen <[email protected]>
- Re: [PATCH 02/04] PCI: use the MCFG table to properly access pci devices (i386)
- From: Greg KH <[email protected]>
- [PATCH 00/04] PCI: add proper MCFG support to let AMD boxes support MMCONFIG
- Prev by Date: Re: 2.6.12-rc6-mm1 & 2K lun testing
- Next by Date: [-mm PATCH] signed vs unsigned cleanup in net/ipv4/raw.c
- Previous by thread: Re: [PATCH 02/04] PCI: use the MCFG table to properly access pci devices (i386)
- Next by thread: Re: [PATCH 02/04] PCI: use the MCFG table to properly access pci devices (i386)
- Index(es):