On Wed, 2014-04-09 at 08:02 -0600, Bjorn Helgaas wrote: > It's possible we could manage domain numbers in the core. On ACPI > systems, we currently we use the ACPI _SEG value as the domain. In > some cases, e.g., on ia64, config space access is done via firmware > interfaces, and those interfaces expect the _SEG values. We could > conceivably maintain a mapping between _SEG and domain, but I'm not > sure there's an advantage there. I'd rather keep the ability for the architecture to assign domain numbers. I'm working on making them relate to the physical slot numbers on our new systems so we get predictable PCI IDs which helps with some stuff like the new network device naming scheme etc... Predictability is a good thing :-) > I probably don't understand what you intend by reversing the order. > Are you suggesting something like new pcibios_*() interfaces the arch > can use to get the host bridge apertures and domain number? Cheers, Ben. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
