From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
David Vrabel <david.vrabel@citrix.com>,
"Chris (Christopher) Brand" <chris.brand@broadcom.com>
Subject: Re: Bug in devicetree_for_each_node() in xen/arch/arm/bootfdt.c ?
Date: Tue, 23 Jun 2015 11:27:08 +0100 [thread overview]
Message-ID: <1435055228.28264.198.camel@citrix.com> (raw)
In-Reply-To: <5589300B.1020108@citrix.com>
On Tue, 2015-06-23 at 11:08 +0100, Julien Grall wrote:
> > reg = <0x0 0x0 0x0 0x40000000 0x0 0x40000000 0x0 0x40000000>;
>
> 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...
A reg can encode multiple regions, by just listing them one after the
other. It'll be in the generic docs about reg properties I expect,
there's nothing special about a reg property in a memory node in this
regard.
Xen parses these just fine, via the loop and use of device_tree_get_reg
in process_memory_node
Ian.
next prev parent reply other threads:[~2015-06-23 10:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 23:02 Bug in devicetree_for_each_node() in xen/arch/arm/bootfdt.c ? Chris (Christopher) Brand
2015-06-23 9:44 ` David Vrabel
2015-06-23 9:57 ` Ian Campbell
2015-06-23 10:08 ` Ian Campbell
2015-06-23 10:10 ` Ian Campbell
2015-06-23 10:01 ` Julien Grall
2015-06-23 10:08 ` Julien Grall
2015-06-23 10:27 ` Ian Campbell [this message]
2015-06-23 10:32 ` Julien Grall
2015-06-23 10:43 ` Ian Campbell
2015-06-24 18:57 ` Chris (Christopher) Brand
2015-07-15 23:35 ` Chris (Christopher) Brand
2015-07-16 8:50 ` [PATCH] xen: arm: bootfdt: Avoid reading off the front of *_cells array Ian Campbell
2015-07-16 12:06 ` Julien Grall
2015-07-16 12:45 ` Ian Campbell
2015-07-16 15:52 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1435055228.28264.198.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=chris.brand@broadcom.com \
--cc=david.vrabel@citrix.com \
--cc=julien.grall@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.