From: Daniel Hellstrom <daniel@xxxxxxxxxxx> Date: Fri, 20 May 2011 10:01:11 +0200 > David Miller wrote: > >>From: Daniel Hellstrom <daniel@xxxxxxxxxxx> >>Date: Thu, 19 May 2011 15:13:14 +0200 >> >> >>>The PowerPC for example assign resources >>>(arch/powerpc/kernel/pci-common.c), and PowerPC may also have a >>>OpenBoot loader: >>> >> >>On some powerpc systems, like sparc64 Niagara, you can't blindly go >>poking around the PCI config space at all and must rely completely >>and entirely upon the OpenBoot device tree. >> > I see, that may be because IRQ routing or resource allocation is done > in a non-standard way I guess, perhaps because of bugs on some of the > motherboards. Or because PCI accesses have to go through a hypervisor. The point is that having it all setup in OpenBoot is a great abstraction because you don't have to care. It also allows things like being able to disable devices with things like "pcia-probe-list" and "pcib-probe-list" properties in the PCI host controller node, which we end up honoring on sparc64 simply because we never directly probe PCI space to probe devices. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
