From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] freescale i.MX28 mxsboot NAND booting on mx28evk bad blocks
Date: Sat, 13 Apr 2013 16:42:01 +0200 [thread overview]
Message-ID: <201304131642.02046.marex@denx.de> (raw)
In-Reply-To: <516601B6.2050801@acm.org>
Dear Paul B. Henson,
> Let me just preface this reply with the disclaimer that I'm fairly new
> to embedded development, and it sounds like you know a lot more about
> what you're talking about than I do ;).
[...]
I'm not reading the thread as it -- again -- contains loads of baseless "is
broken" and "doesn't work" accusations left and right, sorry. I am CCing Fabio.
The issue with the bad sectors is known. This is because the kobs-ng scans the
NAND and fills the DBBT. This is not something that can be done off-line, so the
mxsboot can never generate such a image per-se. It can on the other hand
generate a bootable image. Note that the mxsboot is by default configured for
2048+64 bps flashes.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-04-13 14:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 0:50 [U-Boot] freescale i.MX28 mxsboot NAND booting on mx28evk bad blocks Paul B. Henson
2013-03-19 23:23 ` Scott Wood
2013-03-20 21:20 ` Paul B. Henson
2013-03-20 21:24 ` Scott Wood
2013-04-04 10:09 ` Trent Piepho
2013-04-06 4:28 ` Paul B. Henson
2013-04-06 7:18 ` Trent Piepho
2013-04-11 0:20 ` Paul B. Henson
2013-04-11 12:03 ` Trent Piepho
2013-04-11 18:33 ` Paul B. Henson
2013-04-11 23:25 ` Trent Piepho
2013-04-20 1:03 ` Paul B. Henson
2013-04-20 1:22 ` Trent Piepho
2013-04-23 0:42 ` Paul B. Henson
2013-04-26 1:13 ` Marek Vasut
2013-04-29 20:54 ` Paul B. Henson
2013-04-29 21:01 ` Marek Vasut
2013-05-04 0:08 ` Marek Vasut
2013-05-04 6:21 ` Trent Piepho
2013-05-04 13:20 ` Marek Vasut
2013-04-13 14:42 ` Marek Vasut [this message]
2013-04-13 16:31 ` Trent Piepho
2013-04-13 18:26 ` Marek Vasut
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=201304131642.02046.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.