From: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: U-Boot Mailing List <u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.org>
Cc: Albert ARIBAUD
<albert.u.boot-LhW3hqR2+23R7s880joybQ@public.gmane.org>,
Devicetree Discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Jerry Van Baren
<vanbaren-He//nVnquyzQT0dZR+AlfA@public.gmane.org>,
Tom Warren <twarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH v3 05/16] arm: fdt: Ensure that an embedded fdt is word-aligned
Date: Tue, 6 Dec 2011 17:24:04 -0800 [thread overview]
Message-ID: <1323221055-20113-6-git-send-email-sjg@chromium.org> (raw)
In-Reply-To: <1323221055-20113-1-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
By putting the fdt blob into a distinctive area we can ensure that it appears
at the start of the data section and is word-aligned.
Note: It does not seem to be possible to get objcopy to honour its
--section-alignment flag, which would otherwise provide an easier fix
for this problem.
Signed-off-by: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
---
arch/arm/cpu/armv7/u-boot.lds | 5 +++++
dts/Makefile | 2 +-
2 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/arch/arm/cpu/armv7/u-boot.lds b/arch/arm/cpu/armv7/u-boot.lds
index 40ecf78..793e51b 100644
--- a/arch/arm/cpu/armv7/u-boot.lds
+++ b/arch/arm/cpu/armv7/u-boot.lds
@@ -43,6 +43,11 @@ SECTIONS
. = ALIGN(4);
.data : {
+ /*
+ * Sadly objcopy seems to ignore --section-alignment.
+ * Put any embedded device tree first so it is aligned.
+ */
+ *(.dts.data)
*(.data)
}
diff --git a/dts/Makefile b/dts/Makefile
index 5792afd..83547d4 100644
--- a/dts/Makefile
+++ b/dts/Makefile
@@ -79,7 +79,7 @@ $(obj)dt.o: $(DT_BIN)
\
cd $(dir ${DT_BIN}) && \
$(OBJCOPY) -I binary -O $${oformat} -B $${oarch} \
- $(notdir ${DT_BIN}) $@
+ --prefix-sections=.dts $(notdir ${DT_BIN}) $@
rm $(DT_BIN)
OBJS-$(CONFIG_OF_EMBED) := dt.o
--
1.7.3.1
next prev parent reply other threads:[~2011-12-07 1:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1323221055-20113-1-git-send-email-sjg@chromium.org>
[not found] ` <1323221055-20113-1-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2011-12-07 1:24 ` [PATCH v3 01/16] fdt: Tidy up a few fdtdec problems Simon Glass
2011-12-07 1:24 ` [PATCH v3 02/16] fdt: Add functions to access phandles, arrays and bools Simon Glass
2011-12-07 1:24 ` [PATCH v3 04/16] fdt: Add basic support for decoding GPIO definitions Simon Glass
2011-12-07 1:24 ` Simon Glass [this message]
2011-12-07 1:24 ` [PATCH v3 06/16] arm: fdt: Add skeleton device tree file from kernel Simon Glass
2011-12-07 1:24 ` [PATCH v3 07/16] tegra: fdt: Add Tegra2x " Simon Glass
2011-12-07 1:24 ` [PATCH v3 08/16] tegra: fdt: Add device tree file for Tegra2 Seaboard " Simon Glass
2011-12-07 1:24 ` [PATCH v3 09/16] tegra: usb: fdt: Add additional device tree definitions for USB ports Simon Glass
2011-12-07 1:24 ` [PATCH v3 10/16] tegra: usb: fdt: Add USB definitions for Tegra2 Seaboard Simon Glass
2011-12-07 1:24 ` [PATCH v3 16/16] tegra: fdt: Enable FDT support for Seaboard Simon Glass
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=1323221055-20113-6-git-send-email-sjg@chromium.org \
--to=sjg-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
--cc=albert.u.boot-LhW3hqR2+23R7s880joybQ@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=twarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.org \
--cc=vanbaren-He//nVnquyzQT0dZR+AlfA@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;
as well as URLs for NNTP newsgroup(s).