On Thu, Mar 14, 2013 at 09:38:58PM +0100, Thierry Reding wrote:
> > pci@1,0 {
> > device_type = "pci";
> > assigned-addresses = <0x82000000 0 0x80000000 0 0x1000>;
Sorry, I missed this. The b,d,f bits should be set:
assigned-addresses = <0x82000800 0 0x80000000 0 0x1000>;
> > reg = <0x000800 0 0 0 0>;
> > }
> > pci@2,0 {
> > device_type = "pci";
> > assigned-addresses = <0x82000000 0 0x80001000 0 0x1000>;
assigned-addresses = <0x82001000 0 0x80001000 0 0x1000>;
The 'ranges' stays the same, the PCI 3/2 parse will ignore the b,d,f
bits when comparing against ranges.
The use of r == 0 for assigned-addresses should be enough to
disambiguate this case from any future use of assigned-addresses - the
normal case has r == offset of the associated BAR != 0.
Cheers,
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
