On Wed, 27 Jan 2010 16:01:21 -0800 (PST) David Miller <davem@xxxxxxxxxxxxx> wrote: > From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> > Date: Thu, 28 Jan 2010 09:00:12 +1100 > > > On Wed, 2010-01-27 at 08:26 -0800, Jesse Barnes wrote: > >> > >> Thanks Ben. Any refactoring we need to handle this stuff better is > >> fine with me too. I guess on some platforms calling pci_setup_device > >> may cause problems with special platform devices? > > > > Well, we don't call pci_setup_device() because part of the deal is to > > avoid all of that config space reading that it does :-) Especially in > > the case of some of the IBM EADS bridges which don't let you access > > everything we may want. > > Same problem on sparc64, it's not safe to poke config space > arbitrarily. Some PCI controllers even have bugs which cause them to > hang if you try to access some parts of the host controller's PCI > config space. Ok, that's what I thought. We'll need to make these functions available then... -- Jesse Barnes, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
