From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Make nboot skip bad blocks
Date: Sun, 15 Mar 2009 17:59:28 -0400 [thread overview]
Message-ID: <200903151759.28668.vapier@gentoo.org> (raw)
In-Reply-To: <20090313133819.GB6797@localhost.localdomain>
On Friday 13 March 2009 09:38:19 Ladislav Michl wrote:
> nboot command currently does not skip bad blocks and gives read error when
> loading image stored over bad block. With patch applied, nboot works as
> expected:
iirc, some people proposed a new command or an option to nboot to get skip
behavior (e.g. nboot.jffs2), but i dont see the value in nboot never skipping
bad blocks. when would anyone ever want to use a boot command and have bad
blocks attempt to be processed ?
i.e. your patch sounds good to me ;)
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090315/feae4342/attachment.pgp
next prev parent reply other threads:[~2009-03-15 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 13:38 [U-Boot] [PATCH] Make nboot skip bad blocks Ladislav Michl
2009-03-15 21:59 ` Mike Frysinger [this message]
2009-03-16 15:15 ` Ladislav Michl
2009-03-16 19:59 ` Wolfgang Denk
2009-03-17 17:00 ` Scott Wood
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=200903151759.28668.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox