From: Sascha Hauer <s.hauer@pengutronix.de>
To: gcleary@sightlogix.com
Cc: barebox@lists.infradead.org
Subject: Re: booting kernel from ubi volume in nand flash
Date: Fri, 2 Oct 2015 09:02:37 +0200 [thread overview]
Message-ID: <20151002070237.GM7858@pengutronix.de> (raw)
In-Reply-To: <CAK+b6Lsn6xLG30xK5-9XVLaAGDyDYiPdkfSh-92HcO5fONm_HQ@mail.gmail.com>
Hi Geoff,
On Thu, Oct 01, 2015 at 04:25:59PM -0400, Geoff Cleary wrote:
> Hi,
>
> I cannot find documentation regrading scrubbing of ubi volumes in barebox.
> Is this feature implemented in barebox?
>
> In the case where our kernel is stored in a ubi volume, should we expect
> the possibility that barebox may try to "scrub" (move) a block during boot
> of the kernel, if that block required ECC correction?
I think that should not happen, at least not as long as you only do
readonly accesses to UBI. In this case scrubbing work may be added
to the list of pending works, but that list is never processed. This
can change though if you create/delete volumes or if you write to
volumes. In this case produce_free_peb() or ubi_wl_flush() may be called
which both process the list of pending works.
I hope that helps. If in doubt you should familiarize with the code
yourself.
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
prev parent reply other threads:[~2015-10-02 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 20:25 Geoff Cleary
2015-10-02 7:02 ` Sascha Hauer [this message]
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=20151002070237.GM7858@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=gcleary@sightlogix.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