From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Vrabel <david.vrabel@citrix.com>
Subject: Re: Bug in devicetree_for_each_node() in
 xen/arch/arm/bootfdt.c ?
Date: Tue, 23 Jun 2015 10:44:51 +0100
Message-ID: <55892A93.905@citrix.com>
References: <4EE5B48738DDED408878C97C8E050A8B1D7ABBB3@SJEXCHMB05.corp.ad.broadcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <prvs=609013e1d=david.vrabel@citrix.com>)
	id 1Z7KlE-0001GO-U1
	for xen-devel@lists.xenproject.org; Tue, 23 Jun 2015 09:44:57 +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

On 23/06/15 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.
> =

> The relevant parts of my dts are:
> =

> /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>;

It's been a while since I've looked at device tree stuff but I think you
need 64-bit values for this reg property because the parent node has
#address-cells =3D=3D 0x2 and #size-cells =3D=3D 0x2.

David