On Mon, Jan 28, 2013 at 11:18:29PM +0100, Thomas Petazzoni wrote: > > That would simplify the question of PCI IDs - for Marvell's case and > > the sw root port bridge we can just copy the IDs from the bogus config > > space of the HW. > > Not sure what you mean in this last paragraph. In this second version, > I really rely on the emulated PCI-to-PCI bridges for the resource I'm refering to your earlier question about what PCI IDs to use for the SW emulated devices. If there is no need for the host bridge then you only need 1 PCI ID (for the root port bridge) and you can probably fairly safely re-use the one in the Marvell config space of the HW. > allocation. I give the Linux PCI core a global range of addresses for > memory regions and a global range of addresses for I/O regions, and > then I let Linux do the allocation of ranges on a per bridge basis, > depending on the devices detected downstream. And at the end, I use > those allocated ranges to set up the address decoding windows. Yes, that all seems OK to me. Jason -- 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
