From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH] i.MX5 internal NAND update fixes/cleanup
Date: Thu, 24 Jul 2014 08:48:09 +0200 [thread overview]
Message-ID: <1406184493-29225-1-git-send-email-s.hauer@pengutronix.de> (raw)
The internal NAND update handler for i.MX5 is broken since:
| commit 15ee30138f59eac95379a4b94c538c1fcc338ed5
| Author: Sascha Hauer <s.hauer@pengutronix.de>
| Date: Fri Jul 26 10:52:25 2013 +0200
|
| ARM: i.MX: bbu-internal: optionally use DCD data from image
|
| We used to pass the DCD data from the boards. This patch allows
| to optionally skip passing DCD data. In this case the DCD data
| from the flash image is used if present.
|
| Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
This fixes it and also cleans up the code a bit.
Sascha
----------------------------------------------------------------
Sascha Hauer (4):
ARM: i.MX5: internal NAND update: Use variable for pre_image_size
ARM: i.MX5: internal NAND update: Fix firmware start page for internal nand boot
ARM: i.MX5: internal NAND update: Use variables for some constants
ARM: i.MX5: internal NAND update: simplify code
arch/arm/mach-imx/imx-bbu-internal.c | 63 +++++++++++++++++-------------------
1 file changed, 29 insertions(+), 34 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-07-24 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 6:48 Sascha Hauer [this message]
2014-07-24 6:48 ` [PATCH 1/4] ARM: i.MX5: internal NAND update: Use variable for pre_image_size Sascha Hauer
2014-07-24 6:48 ` [PATCH 2/4] ARM: i.MX5: internal NAND update: Fix firmware start page for internal nand boot Sascha Hauer
2014-07-24 6:48 ` [PATCH 3/4] ARM: i.MX5: internal NAND update: Use variables for some constants Sascha Hauer
2014-07-24 6:48 ` [PATCH 4/4] ARM: i.MX5: internal NAND update: simplify code Sascha Hauer
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=1406184493-29225-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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