From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Michael D. Burkey" <mdburkey@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: i.MX6Q Boot from NAND
Date: Thu, 27 Feb 2014 08:38:35 +0100 [thread overview]
Message-ID: <20140227073835.GD17250@pengutronix.de> (raw)
In-Reply-To: <CAO6XYUt7KaraGNUkTuEkQXKbh0f6MH4Ywn8dDJQpo1RkT2CaSw@mail.gmail.com>
On Wed, Feb 26, 2014 at 03:49:37PM -0500, Michael D. Burkey wrote:
> >Hi ANdreas,
>
> PS...
> Out of curiosity, which SOM are you using that boots from NAND?
> I'm currently working with Variscite's SOM -- and life would have been
> much simpler if someone had just put a SPI NOR on it!
+1
Booting from Nand is always a pain, not only on i.MX. SoC vendors are
always very creative when it comes to bad block handling and ECC layout.
Since it's the ROM code that reads the initial portion you are forced to
put on Nand whatever the ROM code wants to have, even if you want to use
a completely different ECC layout / Bad block table on your Nand.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-02-27 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 20:49 Michael D. Burkey
2014-02-27 7:38 ` Sascha Hauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-26 6:30 andreas.willig
2014-02-26 7:06 ` 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=20140227073835.GD17250@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=mdburkey@gmail.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