From: John Rigby <john.rigby-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: [RFC PATCH 0/3] *** Add device tree support for ARM to U-Boot ***
Date: Wed, 28 Jul 2010 15:59:52 -0600 [thread overview]
Message-ID: <1280354395-9128-1-git-send-email-john.rigby@linaro.org> (raw)
These patches add device tree support to the bootm command in u-boot
for the ARM. I'm sending the patches to this list first for comments
before sending it to the wider audience on the u-boot list.
The only testing so far has shown that this patch does not break non-dt
booting. I don't have a dt enabled beagle kernel so I have not tried that
yet.
John Rigby (3):
FDT: Add fixup support of multiple banks of memory
ARM: WIP: add flat device tree support
ARM: add config for beagle with fdt enabled
MAKEALL | 1 +
arch/arm/include/asm/config.h | 1 +
arch/arm/lib/bootm.c | 128 ++++++++++++++-
boards.cfg | 1 +
common/cmd_bootm.c | 5 +-
common/fdt_support.c | 86 +++++-----
common/image.c | 7 +-
include/configs/omap3_beagle_dt.h | 344 +++++++++++++++++++++++++++++++++++++
include/fdt_support.h | 1 +
include/image.h | 2 +-
10 files changed, 531 insertions(+), 45 deletions(-)
create mode 100644 include/configs/omap3_beagle_dt.h
next reply other threads:[~2010-07-28 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 21:59 John Rigby [this message]
[not found] ` <1280354395-9128-1-git-send-email-john.rigby-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2010-07-28 21:59 ` [RFC PATCH 1/3] FDT: Add fixup support of multiple banks of memory John Rigby
2010-07-28 21:59 ` [RFC PATCH 2/3] ARM: WIP: add flat device tree support John Rigby
2010-07-28 21:59 ` [RFC PATCH 3/3] ARM: add config for beagle with fdt enabled John Rigby
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=1280354395-9128-1-git-send-email-john.rigby@linaro.org \
--to=john.rigby-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox