From: Ian Campbell <Ian.Campbell@citrix.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH 1/4] xen: Correction to module@1 (dom0 kernel) DT node.
Date: Mon, 17 Nov 2014 09:42:15 +0000 [thread overview]
Message-ID: <1416217335.27385.5.camel@citrix.com> (raw)
In-Reply-To: <20141116202606.GD9960@lvm>
On Sun, 2014-11-16 at 12:26 -0800, Christoffer Dall wrote:
> Hi Ian,
>
> On Mon, Nov 10, 2014 at 02:09:58PM +0000, Ian Campbell wrote:
> > - Include bootargs (kernel command line) property.
>
> Why?
>
> The logic I was going for was to reduce duplicate code/entries in the
> DT, and if I read docs/misc/arm/device-tree/booting.txt, the fact that
> we have xen,xen-bootargs but no xen,dom0-bootargs then bootargs added
> further down in Makefile.am will be used.
>
> Is this not correct or not preferred for some reason?
I thought it wasn't working for me, but it's possible I was tripping
over something else which I fixed by hacking around in this stuff around
the same time and misattributed the fix to this change.
Looking at it now I agree that the code looks like it should work
without this change, so why don't you drop this hunk and if I find
something not working right in the new version I'll investigate again
from scratch.
Ian.
>
> -Christoffer
>
> > - Update reg property to match #address-cells and #size-cells in the DTB (both
> > 2).
> >
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> > ---
> > Makefile.am | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/Makefile.am b/Makefile.am
> > index 9b6c7e3..ed5acbb 100644
> > --- a/Makefile.am
> > +++ b/Makefile.am
> > @@ -69,8 +69,9 @@ XEN_OFFSET := 0xA00000
> > DOM0_OFFSET := $(shell echo $$(($(PHYS_OFFSET) + $(KERNEL_OFFSET))))
> > XEN_BOOTARGS := xen,xen-bootargs = \"$(BOOTARGS)\"; \
> > module@1 { \
> > + bootargs = \"$(CMDLINE)\"; \
> > compatible = \"xen,linux-zimage\", \"xen,multiboot-module\"; \
> > - reg = <$(DOM0_OFFSET) 0x800000>; \
> > + reg = <0 $(DOM0_OFFSET) 0 0x800000>; \
> > };
> > endif
> >
> > --
> > 1.7.10.4
> >
next prev parent reply other threads:[~2014-11-17 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 12:48 xen/arm: Bootwrapper update to support PSCI and GICv3 Julien Grall
2014-11-10 11:34 ` Ian Campbell
2014-11-10 13:35 ` Christoffer Dall
2014-11-10 14:09 ` [PATCH 1/4] xen: Correction to module@1 (dom0 kernel) DT node Ian Campbell
2014-11-16 20:26 ` Christoffer Dall
2014-11-17 9:42 ` Ian Campbell [this message]
2014-11-10 14:09 ` [PATCH 2/4] Fix build when Xen is not enabled Ian Campbell
2014-11-16 21:03 ` Christoffer Dall
2014-11-17 9:44 ` Ian Campbell
2014-11-10 14:10 ` [PATCH 3/4] Select correct dom0 console depending on whether Xen is enabled or not Ian Campbell
2014-11-10 14:10 ` [PATCH 4/4] xen: Disable boot scrub Ian Campbell
2014-11-10 14:10 ` xen/arm: Bootwrapper update to support PSCI and GICv3 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=1416217335.27385.5.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=christoffer.dall@linaro.org \
--cc=xen-devel@lists.xen.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.