public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Lauren Del Giudice <lauren@wyplay.com>
To: Darwin Rambo <drambo@broadcom.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBI - exclude bootloader blocks from wear levelling
Date: Tue, 22 Dec 2009 09:08:08 +0100	[thread overview]
Message-ID: <4B307E68.90901@wyplay.com> (raw)
In-Reply-To: <B125D8217ABC4B43826503DE00A2D44910DFC17584@SJEXCHCCR01.corp.ad.broadcom.com>

Good news, thank you Darwin. May I suggest then to change the
sentence in the (excellent) documentation from:

"you may continuously write/erase only one logical eraseblock of an
UBI volume, but UBI will spread this to all physical eraseblocks of
the flash chip"
<http://www.linux-mtd.infradead.org/doc/ubi.html#L_overview>

to something more explicit/accurate?

Lauren.

Darwin Rambo wrote:
> 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
> 
> 
> 
> -----Original Message-----
> From: linux-mtd-bounces@lists.infradead.org [mailto:linux-mtd-bounces@lists.infradead.org] On Behalf Of Lauren Del Giudice
> Sent: Monday, December 21, 2009 8:46 AM
> To: linux-mtd@lists.infradead.org
> Subject: UBI - exclude bootloader blocks from wear levelling
> 
> I'm new to UBI... I understood that static wear levelling is applied
> accross the whole device (a NAND device in my case); If so, how can
> I exclude blocks reserved for the bootloader from wear levelling?
> 
> Thanks for your help,
> Lauren.
> ----
> This message contains confidential information and may contain information that is legally privileged.  If you have received this message by mistake, please immediately notify us and delete the original message. Thank you.  
> 
> Ce message contient des informations confidentielles.  S'il vous est parvenu par erreur, merci de bien vouloir nous en aviser par retour, de n'en faire aucun usage et de n'en garder aucune copie.
> ----
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 
> 
----
This message contains confidential information and may contain information that is legally privileged.  If you have received this message by mistake, please immediately notify us and delete the original message. Thank you.  

Ce message contient des informations confidentielles.  S'il vous est parvenu par erreur, merci de bien vouloir nous en aviser par retour, de n'en faire aucun usage et de n'en garder aucune copie.
----

  parent reply	other threads:[~2009-12-22  8:12 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
2009-12-21 23:12     ` Darwin Rambo
2010-01-09 23:18       ` Artem Bityutskiy
2009-12-22  8:08   ` Lauren Del Giudice [this message]
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=4B307E68.90901@wyplay.com \
    --to=lauren@wyplay.com \
    --cc=drambo@broadcom.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