From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: "Thorsten Mühlfelder" <muehlfelder@enertex.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Some questions on bit-flips and JFFS2
Date: Tue, 11 May 2010 16:55:19 +0200 [thread overview]
Message-ID: <4BE96FD7.7020005@aimvalley.nl> (raw)
In-Reply-To: <201005111009.06724.muehlfelder@enertex.de>
Thorsten Mühlfelder wrote:
> Am Wednesday 05 May 2010 10:34:14 schrieb Norbert van Bolhuis:
>> It much more easier to let UBI/UBIFS deal with this suff. It's designed for
>> this.
>> u-boot support UBIFS (read-only). This means you can put a kernel image
>> on UBIFS and make u-boot read/boot it.
>
> How would I do this? The only thing I've found about it is this discussion of
> April 2008:
> http://lists.infradead.org/pipermail/linux-mtd/2008-April/021268.html
>
> Thanks for any tip
> Thorsten
>
What I meant was to keep the NAND flash partitions the same and
use UBIFS (i.s.o. JFFS2) and of course also put the kernel uImage on
UBIFS.
The goal here is to make u-boot read and boot the kernel image from UBIFS
(i.s.o. from bare NAND).
But I understand Linux cannot read whatever Sam-Ba 2.5 writes, so I guess
it's not even possible to read the kernel image and put it on UBIFS.
Or can you put a kernel image on it beforehand ? are we talking about
deployed systems or to be deployed systems ?
Maybe you first have to find a solution for the Sam-Ba Linux
incompatibility. I guess u-boot can read the kernel uImage, so u-boot
does seem to understand whatever Sam-Ba 2.5 writes.
Anyway, if you switch to UBIFS and *can* put the kernel image on UBIFS
fatal bit flips in the uImage on bare NAND don't matter.
On the other hand: fatal bit flips in bootstrap/u-boot/u-boot_env will still
prevent the system to boot. So maybe also refreshing those images is necessary.
You need a recent linux kernel and u-boot for them to support UBIFS.
Note that: if you would upgrade your system with a new u-boot/linux and
UBIFS i.s.o. JFFS2, *everything* on flash will change. If you want to do
this for deployed systems you need a huge upgrade script.
I don't use NAND+UBIFS myself, so I have no experience there.
The below pointers should have some relevant info though:
- u-boot home-page: http://www.denx.de/wiki/U-Boot/WebHome
- u-boot mailing list: http://lists.denx.de/pipermail/u-boot/
- u-boot source code GIT tree: http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=tree
(checkout boards with NAND and boot-from-NAND support)
- specialized GIT trees for NAND and UBI: http://www.denx.de/wiki/U-Boot/Custodians
Regards,
Norbert.
next prev parent reply other threads:[~2010-05-11 14:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 13:05 Some questions on bit-flips and JFFS2 Thorsten Mühlfelder
2010-05-04 9:28 ` Norbert van Bolhuis
2010-05-04 14:59 ` Thorsten Mühlfelder
2010-05-05 8:34 ` Norbert van Bolhuis
2010-05-05 8:40 ` Ricard Wanderlof
2010-05-05 8:51 ` Artem Bityutskiy
2010-05-05 9:20 ` Ricard Wanderlof
2010-05-11 7:59 ` Thorsten Mühlfelder
2010-05-11 9:35 ` Ricard Wanderlof
2010-05-12 11:21 ` Thorsten Mühlfelder
2010-05-12 12:22 ` Ricard Wanderlof
2010-05-19 7:45 ` Thorsten Mühlfelder
2010-05-05 9:29 ` Norbert van Bolhuis
2010-05-11 8:09 ` Thorsten Mühlfelder
2010-05-11 14:55 ` Norbert van Bolhuis [this message]
2010-05-12 10:48 ` Thorsten Mühlfelder
2010-05-05 6:59 ` Ricard Wanderlof
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=4BE96FD7.7020005@aimvalley.nl \
--to=nvbolhuis@aimvalley.nl \
--cc=linux-mtd@lists.infradead.org \
--cc=muehlfelder@enertex.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.