linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: ubi question
Date: Wed, 2 Jun 2010 11:22:46 +0200	[thread overview]
Message-ID: <4C0622E6.7070203@parrot.com> (raw)

Hi,

I have some question about ubi implementation.
I have read most of the "drivers/mtd/ubi/ubi-media.h" documentation.

The doc is not very clear about the case when data_size is set for
dynamic volume. From my understanding it is set in case copy_flag is set 
and the value is the logical eraseblock size.

When a block with copy_flag set, when we append data (and make the crc 
invalid), do we make sure that all previous version of this logical 
eraseblock are removed from flash ?

Why layout volume isn't a static volume with one eraseblock and update 
done with atomic leb update (copy flag) ?
This would have :
- make the crc ckeck done by generic code (static volume one)
- make the handling of update by generic code
- avoid to having to handle dynamic volume in minimalist implementation 
(bootloader)
Do I miss something ?


Matthieu

             reply	other threads:[~2010-06-02  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02  9:22 Matthieu CASTET [this message]
2010-06-02 11:10 ` ubi question 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=4C0622E6.7070203@parrot.com \
    --to=matthieu.castet@parrot.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;
as well as URLs for NNTP newsgroup(s).