Hi Ian, On 24/10/14 10:58, Ian Campbell wrote: > These properties are defined in ePAPR and the OpenFirmware PCI Bus Binding > Specification (IEEE Std 1275-1994). > > This replaces the xgene specific mapping. Tested on Mustang and on a model > with > a PCI virtio controller.
I'm wondering why you choose to map everything at Xen boot time rather than implementing PHYSDEVOP_pci_device_add to do the job? This would allow us to re-use most of the interrupts/mmio decoding provided in the device tree library. It would also avoid missing support of cascade ranges/interrupt-map. Regards, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
