From: Marc Reilly <marc@cpdesign.com.au>
To: barebox@lists.infradead.org
Subject: [PATCH] Put the explicit flash header sections back in.
Date: Wed, 5 Jan 2011 09:57:56 +1100 [thread overview]
Message-ID: <1294181876-16619-2-git-send-email-marc@cpdesign.com.au> (raw)
In-Reply-To: <1294181876-16619-1-git-send-email-marc@cpdesign.com.au>
This (re)enables boards to have multiple boot headers so that the one
image can be used for booting from multiple boot sources.
Signed-off-by: Marc Reilly <marc@cpdesign.com.au>
---
| 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
--git a/arch/arm/mach-imx/include/mach/imx-flash-header.h b/arch/arm/mach-imx/include/mach/imx-flash-header.h
index f1054da..b8f5176 100644
--- a/arch/arm/mach-imx/include/mach/imx-flash-header.h
+++ b/arch/arm/mach-imx/include/mach/imx-flash-header.h
@@ -20,6 +20,18 @@
#define FLASH_HEADER_OFFSET 0x0400
#endif
+#define __flash_header_0x1000 __section(.flash_header_0x1000)
+#define __dcd_entry_0x1000 __section(.dcd_entry_0x1000)
+#define __image_len_0x1000 __section(.image_len_0x1000)
+
+#define __flash_header_0x0100 __section(.flash_header_0x0100)
+#define __dcd_entry_0x0100 __section(.dcd_entry_0x0100)
+#define __image_len_0x0100 __section(.image_len_0x0100)
+
+#define __flash_header_0x0400 __section(.flash_header_0x0400)
+#define __dcd_entry_0x0400 __section(.dcd_entry_0x0400)
+#define __image_len_0x0400 __section(.image_len_0x0400)
+
/*
* NOR is not automatically copied anywhere by the boot ROM
*/
--
1.7.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-01-04 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 22:57 imx: Put flash header position specific " Marc Reilly
2011-01-04 22:57 ` Marc Reilly [this message]
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=1294181876-16619-2-git-send-email-marc@cpdesign.com.au \
--to=marc@cpdesign.com.au \
--cc=barebox@lists.infradead.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