From: Stas Sergeev <stsp@list.ru>
To: Gerhard Sittig <gsi@denx.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: nandwrite and contiguous space
Date: Tue, 01 Apr 2014 23:25:00 +0400 [thread overview]
Message-ID: <533B128C.7050603@list.ru> (raw)
In-Reply-To: <20140401182350.GS2775@book.gsilab.sittig.org>
01.04.2014 22:23, Gerhard Sittig пишет:
> On Tue, 2014-04-01 at 13:30 +0400, Stas Sergeev wrote:
>> I am looking for a NAND flasher that supports searching
>> for the contiguous region of good blocks (within a specified
>> range), and flashes an image to it. It seems nandwrite - the
>> default linux flasher - can only skip bad blocks, but the scenario
>> I need, doesn't seem to be supported.
> Isn't the point that the set of good blocks keeps changing over
> time? What might be good now, may be bad a second later or next
> year, doesn't matter as long as it won't stay good forever.
Hi, I think the point is that if they are no longer ever written,
they won't change its goodness...
Anyway, this is how the ST soc chips work.
They search NAND for a specific signature, and once
found, they map the contiguous block, starting from
that signature, to memory, which allows to run u-boot
in a nor-alike fashion. They do not do BBT lookups when
mapping, AFAIK, and so such a requirement for flasher
does exist.
>> Is there any other flasher that does support this?
>> Or maybe some trick with nandwrite exists?
>> If not, how difficult is it to implement such a capability into
>> nandwrite?
> If you want a sequence of good blocks, this very much sounds like
> the LEBs which UBI provides. Aren't you asking for an UBI
> volume? What am I missing?
Unfortunately, I don't think the aforementioned ST chips
can boot from UBI. Once booted, I want UBI for sure.
But the only alternative to the aforementioned requirement
would be to assume that 2 first blocks are good, and fit
u-boot there, and it they are bad - throw away such a nand.
I am considering this too, but I wonder how many nands
will be wasted this way... Likely none, but who knows. :)
next prev parent reply other threads:[~2014-04-01 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 9:30 nandwrite and contiguous space Stas Sergeev
2014-04-01 18:23 ` Gerhard Sittig
2014-04-01 19:25 ` Stas Sergeev [this message]
2014-04-02 4:19 ` Stas Sergeev
2014-04-04 22:00 ` Richard Weinberger
2014-04-12 8:30 ` Stas Sergeev
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=533B128C.7050603@list.ru \
--to=stsp@list.ru \
--cc=gsi@denx.de \
--cc=linux-mtd@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;
as well as URLs for NNTP newsgroup(s).