public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Bernard Blackham <bernard@largestprime.net>
To: u-boot-users@lists.sourceforge.net, linux-mtd@lists.infradead.org
Subject: Re: [U-Boot-Users] ubi and u-boot
Date: Sat, 19 Apr 2008 01:49:47 +0800	[thread overview]
Message-ID: <4808DF3B.2080702@largestprime.net> (raw)
In-Reply-To: <20080418165957.GG31520@shareable.org>

Jamie Lokier wrote:
> Josh Boyer wrote:
>>> Is anyone working on ubi/ubifs support in u-boot?
>> I am not aware of anyone actively working on porting UBI to upstream
>> U-Boot at this exact moment.
> 
> Is it even a good idea?

 From what I've seen, UBI is the first solution with the potential for 
reliably booting from NAND flash - specifically, dealing with 
read-disturbance from adjacent blocks causing bit errors in critical 
boot blocks. This could save useful things like your kernel image (where 
it's rarely written, but it and blocks around it are read often enough 
to cause an annoying bitflip or two). The rewriting can be done once 
userspace boots, but having it in UBI to begin with makes this easier.

(Unless there's a much easier way to deal with read-disturbance that 
I've missed, in which case please lart me).

Wolfgang showed some interest briefly too.[1]

 > The UBI (version 1 :-) initial scan is not
> fast for large flash, and if the bootloader does it too, that's twice
> as much time to boot.
 >
> However, if there was a protocol for bootloader to pass the scan
> results to the booted kernel, that would be very nice.

If there's no compelling reasons not to, I'll try and find some time to 
work on ubi in uboot. I'm not expecting it to be easy though :)

Cheers,
Bernard.

[1] http://article.gmane.org/gmane.comp.boot-loaders.u-boot/32602

  reply	other threads:[~2008-04-18 17:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 14:21 ubi and u-boot Bernard Blackham
2008-04-18 16:40 ` [U-Boot-Users] " Josh Boyer
2008-04-18 16:59   ` Jamie Lokier
2008-04-18 17:49     ` Bernard Blackham [this message]
2008-04-20 22:22       ` Wolfgang Denk
2008-04-21 12:05         ` Artem Bityutskiy
2008-04-21 13:36           ` Ricard Wanderlof
2008-04-21 13:44             ` Josh Boyer
2008-04-21 13:50               ` Artem Bityutskiy
2008-04-21 14:01                 ` Artem Bityutskiy
2008-04-22 11:44                 ` Ricard Wanderlof
2008-04-22 12:30               ` Jamie Lokier
2008-04-18 19:19     ` Josh Boyer
2008-04-20 16:04       ` Jamie Lokier
2008-04-20 16:44         ` Josh Boyer
2008-04-20 17:29           ` Jamie Lokier
2008-04-21  1:05         ` Hamish Moffatt
2008-04-19  9:25 ` Artem Bityutskiy

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=4808DF3B.2080702@largestprime.net \
    --to=bernard@largestprime.net \
    --cc=linux-mtd@lists.infradead.org \
    --cc=u-boot-users@lists.sourceforge.net \
    /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