public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] mtd: add writebufsize field to mtd_info struct
Date: Thu, 27 Jan 2011 17:18:28 +0100	[thread overview]
Message-ID: <m2ipxaxquj.fsf@ohwell.denx.de> (raw)
In-Reply-To: <1295540225-11083-1-git-send-email-holger.brunck@keymile.com> (Holger Brunck's message of "Thu, 20 Jan 2011 17:17:00 +0100")

Hi Stefan,

do you have any comment on this series?  I delegated the patches to you
in patchwork already :)  No seriously, the patches look sane and are in
accordance to what is done in Linux....

> This field will be used to indicate the write buffer size
> of the MTD device. UBI will set it's minimal I/O unit size
> (min_io_size) to the indicated write buffer size. By this
> change we intend to fix failed recovery of UBIFS partitions
> we currently observe on NOR flash when mounting the partition
> after unclean unmount.
>
> Currently the min_io_size is set to mtd->writesize (which is 1
> byte for NOR flash). But flash programming is often done from
> prepared write buffer containing multiple bytes and is performed
> in one programming operation which could be interrupted by a power
> cut or a system reset causing corrupted (partially written) areas
> in a flash sector. Knowing the size of potentially corrupted areas
> UBIFS scanning and recovery algorithms are able to perform
> successful recovery.
>
> Signed-off-by: Holger Brunck <holger.brunck@keymile.com>

Thanks
  Detlev

-- 
vi vi vi - the roman numeral of the beast.
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

  parent reply	other threads:[~2011-01-27 16:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 16:17 [U-Boot] [PATCH 1/6] mtd: add writebufsize field to mtd_info struct Holger Brunck
2011-01-20 16:17 ` [U-Boot] [PATCH 2/6] cfi_mtd: add writebufsize initialization Holger Brunck
2011-01-20 16:17 ` [U-Boot] [PATCH 3/6] mtd, nand: add mtd->writebufsize initialization Holger Brunck
2011-01-20 16:17 ` [U-Boot] [PATCH 4/6] mtd, onenand: add mtd writebufsize initialization Holger Brunck
2011-01-20 16:17 ` [U-Boot] [PATCH 5/6] mtd: initialize writebufsize in the MTD object of a partition Holger Brunck
2011-01-20 16:17 ` [U-Boot] [PATCH 6/6] UBI: use mtd->writebufsize to set minimal I/O unit size Holger Brunck
2011-01-27 16:18 ` Detlev Zundel [this message]
2011-02-01  8:26   ` [U-Boot] [PATCH 1/6] mtd: add writebufsize field to mtd_info struct Holger Brunck
2011-02-01  9:28     ` Stefan Roese
2011-02-01 12:18       ` Holger Brunck

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=m2ipxaxquj.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox