quoted

-		ranges = <0 f8000000 00100000>;
-		reg = <f8000000 00100000>;	// CCSRBAR 1M
+		ranges = <00001000 f8001000 000ff000

[...]

quoted

+		reg = <f8000000 00001000>;	// CCSRBAR

This can't be right, and I suspect it will break any kernel access to
the first 0x1000 bytes of the CCSR_BAR space.  reg should actually
describe the register space of the SOC.  If ranges needs to specify
that, too, they should be able to be redundant.  But this looks like
a big hack, to me.  Am I missing something?

"reg" and "ranges" can never overlap really.

Is this the special case where the PHB is visible in
PCI configuration space?

Or, please explain what CCSR_BAR is...


Segher