From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julien Grall <julien.grall@citrix.com>
Subject: Re: Bug in devicetree_for_each_node() in
 xen/arch/arm/bootfdt.c ?
Date: Tue, 23 Jun 2015 11:08:11 +0100
Message-ID: <5589300B.1020108@citrix.com>
References: <4EE5B48738DDED408878C97C8E050A8B1D7ABBB3@SJEXCHMB05.corp.ad.broadcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <prvs=609be8bc6=julien.grall@citrix.com>)
	id 1Z7LFi-0006fQ-An
	for xen-devel@lists.xenproject.org; Tue, 23 Jun 2015 10:16:26 +0000
In-Reply-To: <4EE5B48738DDED408878C97C8E050A8B1D7ABBB3@SJEXCHMB05.corp.ad.broadcom.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "Chris (Christopher) Brand" <chris.brand@broadcom.com>, "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: David Vrabel <david.vrabel@citrix.com>, Ian Campbell <ian.campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

Hi,

On 23/06/2015 00:02, Chris (Christopher) Brand wrote:
> I=92ve been trying to figure out why Xen only reports 2GB on my ARM
> platform that actually has 3GB, and I think I=92ve found a bug, but I=92m
> not familiar enough with the Xen code to fix it.
> /dts-v1/;
>
> / {
>
>       model =3D "Broadcom STB (7445d0)";
>
>       compatible =3D "brcm,bcm7445d0", "brcm,brcmstb";
>
>       #address-cells =3D <0x2>;
>
>       #size-cells =3D <0x2>;
>
>       interrupt-parent =3D <0x1>;
>
>       memory {
>
>             #address-cells =3D <0x1>;
>
>             #size-cells =3D <0x1>;
>
>             device_type =3D "memory";
>
>             reg =3D <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