From: Tim Deegan <tim@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH 4/8] arm: link a device tree blob into the xen image
Date: Fri, 10 Feb 2012 16:50:58 +0000 [thread overview]
Message-ID: <20120210165058.GH32107@ocelot.phlegethon.org> (raw)
In-Reply-To: <1328881958.6133.268.camel@zakaz.uk.xensource.com>
At 13:52 +0000 on 10 Feb (1328881958), Ian Campbell wrote:
> On Fri, 2012-02-10 at 13:40 +0000, David Vrabel wrote:
> > On 10/02/12 13:35, Ian Campbell wrote:
> > > On Fri, 2012-02-10 at 13:03 +0000, David Vrabel wrote:
> > >> From: David Vrabel <david.vrabel@citrix.com>
> > >>
> > >> Link a device tree blob (DTB) into the xen image. This is loaded
> > >> immediately after Xen and xen_start() is called with the correct
> > >> address in atag_paddr.
> > >
> > > Is platform.dtb supposed to be included in this patch/series or is it
> > > intended that I should supply it from somewhere? (in which case, how and
> > > where etc).
> >
> > I make a symlink to vexpress-v2p-aem-v7a.dtb built in my Linux tree.
> >
> > Would it be better build the DTB from source included in Xen?
>
> I guess that's what Linux has done but I don't know if we want to
> replicate all that and keep syncing etc. On the flip side I suppose it's
> currently only a single platform.
I think we should take it into our tree in some form, unless there's a
way to automatically extract it from the dom0 kernel at boot. It should
be possible to recompile Xen without needing to configure and build a
linux kernel.
In theory this will eventually be provided by the bootloader or
firmware, right?
Tim.
next prev parent reply other threads:[~2012-02-10 16:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 13:03 [PATCH 0/8] arm: initial device tree support (#2) David Vrabel
2012-02-10 13:03 ` [PATCH 1/8] libfdt: add version 1.3.0 David Vrabel
2012-02-10 13:38 ` Ian Campbell
2012-02-10 13:03 ` [PATCH 2/8] libfdt: fixup libfdt_env.h for xen David Vrabel
2012-02-10 13:03 ` [PATCH 3/8] libfdt: add to build David Vrabel
2012-02-10 13:03 ` [PATCH 4/8] arm: link a device tree blob into the xen image David Vrabel
2012-02-10 13:35 ` Ian Campbell
2012-02-10 13:40 ` David Vrabel
2012-02-10 13:52 ` Ian Campbell
2012-02-10 16:50 ` Tim Deegan [this message]
2012-02-10 17:38 ` David Vrabel
2012-02-10 17:46 ` Ian Campbell
2012-02-10 13:03 ` [PATCH 5/8] arm: map device tree blob in initial page tables David Vrabel
2012-02-10 13:03 ` [PATCH 6/8] arm: add early_printk() David Vrabel
2012-02-10 13:03 ` [PATCH 7/8] arm, device tree: parse the DTB for RAM location and size David Vrabel
2012-02-10 13:25 ` Tim Deegan
2012-02-10 13:03 ` [PATCH 8/8] arm: setup MM using information from the device tree David Vrabel
-- strict thread matches above, loose matches on Subject: below --
2012-02-13 13:18 [PATCH 0/8] arm: initial device tree support (#3) David Vrabel
2012-02-13 13:18 ` [PATCH 4/8] arm: link a device tree blob into the xen image David Vrabel
2012-02-17 17:13 ` Ian Campbell
2012-02-17 17:22 ` David Vrabel
2012-02-20 17:20 ` Ian Campbell
2012-02-22 14:34 ` 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=20120210165058.GH32107@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).