From: twebb <taliaferro62@gmail.com>
To: Darwin Rambo <drambo@broadcom.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Lauren Del Giudice <lauren@wyplay.com>
Subject: Re: UBI - exclude bootloader blocks from wear levelling
Date: Mon, 21 Dec 2009 17:51:43 -0500 [thread overview]
Message-ID: <dbdb2ea60912211451vda39800t803891a2acf9528a@mail.gmail.com> (raw)
In-Reply-To: <B125D8217ABC4B43826503DE00A2D44910DFC17584@SJEXCHCCR01.corp.ad.broadcom.com>
> Wear levelling is done across a "ubi device" (not the whole nand device) which is associated with a mtd partition. Your bootloader and kernel mtd partitions will not be wear levelled, only your ubi file system partitions. i.e. ubi doesn't know about non-ubi mtd partitions.
>
> I think that's the gist of it.
>
> Darwin
>
That's my understanding also.
Could you maybe clarify another point? If I wanted to exclude some
blocks that contain boot code (like Lauren's question), and the
leftover space on the NAND device was ultimately going to be used for
four different volumes, does it make the most sense to...
a) define one MTD partition that includes all NAND space (except the
blocks reserved for boot code); and then define one UBI device that
attaches to the MTD device and includes the four volumes (ubi0_0,
ubi0_1, ubi0_2, ubi0_3)
OR
b) define four MTD partitions that include all NAND space (except the
blocks reserved for boot code); and then define four UBI devices that
attach to the MTD devices and each UBI device has one volume
associated with it (ubi0_0, ubi1_0, ubi2_0, ubi3_0)?
Thanks,
twebb
next prev parent reply other threads:[~2009-12-21 22:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 16:46 UBI - exclude bootloader blocks from wear levelling Lauren Del Giudice
2009-12-21 21:30 ` Darwin Rambo
2009-12-21 22:51 ` twebb [this message]
2009-12-21 23:12 ` Darwin Rambo
2010-01-09 23:18 ` Artem Bityutskiy
2009-12-22 8:08 ` Lauren Del Giudice
2009-12-22 14:03 ` Darwin Rambo
2009-12-23 6:32 ` Wolfgang Denk
2009-12-23 17:12 ` Darwin Rambo
2009-12-23 21:08 ` Lauren Del Giudice
2009-12-23 21:40 ` Wolfgang Denk
2009-12-23 23:39 ` Darwin Rambo
2010-01-09 23:14 ` 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=dbdb2ea60912211451vda39800t803891a2acf9528a@mail.gmail.com \
--to=taliaferro62@gmail.com \
--cc=drambo@broadcom.com \
--cc=lauren@wyplay.com \
--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