Re: [Xen-devel] Bug in devicetree_for_each_node() in xen/arch/arm/bootfdt.c ?

[Julien Grall <julien.grall@xxxxxxxxxx>]

Hi,

On 23/06/2015 00:02, Chris (Christopher) Brand wrote:
> I’ve been trying to figure out why Xen only reports 2GB on my ARM
> platform that actually has 3GB, and I think I’ve found a bug, but I’m
> not familiar enough with the Xen code to fix it.
> /dts-v1/;
>
> / {
>
>       model = "Broadcom STB (7445d0)";
>
>       compatible = "brcm,bcm7445d0", "brcm,brcmstb";
>
>       #address-cells = <0x2>;
>
>       #size-cells = <0x2>;
>
>       interrupt-parent = <0x1>;
>
>       memory {
>
>             #address-cells = <0x1>;
>
>             #size-cells = <0x1>;
>
>             device_type = "memory";
>
>             reg = <0x0 0x0 0x0 0x40000000 0x0 0x40000000 0x0 0x40000000>;
As said by David, Xen will parse "reg" using the #address-cells and 
#size-cells of the parent. So it's normal to see 2GB. Does the same 
device tree reports 3GB on Linux? I suspect no.
Although, what the rest of the node used for? Do we expect to parse it? 
I wasn't able to find a suitable bindings in the docs...
Regards,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel