From: David Vrabel <david.vrabel@citrix.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 0/7] RFC: arm: (really) minimal device tree support
Date: Fri, 3 Feb 2012 19:15:08 +0000 [thread overview]
Message-ID: <1328296515-25876-1-git-send-email-david.vrabel@citrix.com> (raw)
This set of patches adds libfdt and some minimal infrastructure for
parsing a DTB. The DTB is linked into the Xen image since there isn't
a bootloader when running on the model. Information on available RAM
is obtained and used to get the address to relocate Xen to (the MM is
still initialized with hard-coded values, I'll be fixing this next).
I also added an early_printk() function since its needed when doing
the early scan of the DTB. It's not very platform-independant but it
should do for now.
So, not really a lot here but I think it would be useful to get the
basic infrastructure reviewed a bit before making more use of it.
David
next reply other threads:[~2012-02-03 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 19:15 David Vrabel [this message]
2012-02-03 19:15 ` [PATCH 1/7] libfdt: add version 1.3.0 David Vrabel
2012-02-03 19:15 ` [PATCH 2/7] libfdt: add to build David Vrabel
2012-02-03 19:15 ` [PATCH 3/7] arm: link a device tree blob into the xen image David Vrabel
2012-02-03 20:22 ` Tim Deegan
2012-02-03 19:15 ` [PATCH 4/7] arm: map device tree blob in initial page tables David Vrabel
2012-02-03 21:18 ` Tim Deegan
2012-02-06 17:36 ` David Vrabel
2012-02-07 9:28 ` Tim Deegan
2012-02-03 19:15 ` [PATCH 5/7] libfdt: fixup libfdt_env.h for xen David Vrabel
2012-02-03 19:15 ` [PATCH 6/7] arm: add early_printk() David Vrabel
2012-02-03 19:15 ` [PATCH 7/7] arm, device tree: parse the DTB for RAM location and size David Vrabel
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=1328296515-25876-1-git-send-email-david.vrabel@citrix.com \
--to=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).