mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: "Barbier, Renaud" <renaud.barbier@abaco.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: barebox ubifs support
Date: Thu, 27 May 2021 08:48:37 +0200	[thread overview]
Message-ID: <20210527064837.GA19819@pengutronix.de> (raw)
In-Reply-To: <MN2PR16MB31351A1EC23941D33584F27291249@MN2PR16MB3135.namprd16.prod.outlook.com>

Hi Renaud,

On Wed, May 26, 2021 at 12:53:55PM +0000, Barbier, Renaud wrote:
> Question on the UBIFS support
> 
> Is barebox doing the full bad block management?
> i.e before booting the system to the Linux prompt, will barebox fix bad blocks?
> 
> I am asking this question because some customers may want to boot a
> initramfs image from NAND. In this case Linux will not mount the NAND
> to do the bad block fixing.

Bad block management is done in UBI, not UBIFS. The UBI code is derived
from Linux and is expected to do the same job. This includes checking
the amount of bitflips and rewriting the data on a fresh block if the
number of bitflips exceeds a certain threshold. Suspicious blocks are
tortured with r/w cycles to see if they are bad and the blocks are
marked as bad when they are.

However, are you saying the whole NAND is readonly most of the time?
Aren't there any other partitions?

Sascha


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
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


      reply	other threads:[~2021-05-27  6:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 12:53 Barbier, Renaud
2021-05-27  6:48 ` 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=20210527064837.GA19819@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=renaud.barbier@abaco.com \
    --subject='Re: barebox ubifs support' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox