public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Brijesh Singh <brijesh.s.singh@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Why is PEB not erased before writing???
Date: Tue, 20 Feb 2007 10:34:28 +0100	[thread overview]
Message-ID: <1171964069.30834.220.camel@localhost.localdomain> (raw)
In-Reply-To: <6b5362aa0702192237o69e7efe9wf5844bfaff91e2ff@mail.gmail.com>

On Tue, 2007-02-20 at 12:07 +0530, Brijesh Singh wrote:
> I tried to overwrite same block.
> Ubi should call erase before overwriting the data block.But it didn't.
> UBI simply wrote the block again.That will write garbage for a flash.
> So who will call erase??Is it the application's responsibility to call
> erase before writing at same  location???
> 
> I am stuck here because my concept was,
> ubi will check if we are re-writing the same PEB.
> If yes,UBI will erase the block and then write the same block.

Applications and UBI kernel users have no access to physical erase
blocks. They look at logical erase blocks. UBI manages the translation
of logical to physical blocks. If you write to the same logical erase
block again UBI will just write to a different physical erase block and
erase the previous PEB later on. The internal management guarantees that
the application looks only at the newest written block and not at the
older one.

	tglx

  reply	other threads:[~2007-02-20  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20  6:37 Why is PEB not erased before writing??? Brijesh Singh
2007-02-20  9:34 ` Thomas Gleixner [this message]
2007-02-20  9:49   ` brijesh.singh
2007-02-20 10:44     ` Thomas Gleixner
2007-02-20 11:08       ` Brijesh Singh
2007-02-20 11:11       ` Brijesh Singh
2007-02-20 11:17         ` Thomas Gleixner
2007-02-20 21:48           ` Gavin Lambert
2007-02-20 22:29             ` Thomas Gleixner

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=1171964069.30834.220.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=brijesh.s.singh@gmail.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