From: Ben Gardiner <bengardiner@nanometrics.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/4] introduce nand write.trimffs
Date: Thu, 19 May 2011 12:49:21 -0400 [thread overview]
Message-ID: <cover.1305823168.git.bengardiner@nanometrics.ca> (raw)
This series adds a nand write variant which implements the procedure
reccomended in the UBI FAQ [1] of dropping trailing pages of eraseblocks
containing entirely 0xff's.
[1] http://www.linux-mtd.infradead.org/doc/ubi.html#L_flasher_algo
Changes since v1:
* renamed to 'trimffs' from 'ubi'
* wrapped the new feature in #ifdefs
* don't make it default for jffs -- patch dropped
* attribution of the drop_ffs() function from mtd-utils to Artem
Ben Gardiner (4):
[v2] nand_base: trivial: fix comment read/write comment
[v2] nand_util: convert nand_write_skip_bad() to flags
[v2] nand_util: drop trailing all-0xff pages if requested
[v2] cmd_nand: add nand write.trimffs command
common/cmd_nand.c | 22 +++++++++++++++++++-
drivers/mtd/nand/nand_base.c | 2 +-
drivers/mtd/nand/nand_util.c | 43 +++++++++++++++++++++++++++++++++++------
include/nand.h | 7 +++++-
4 files changed, 63 insertions(+), 11 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-05-19 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 16:49 Ben Gardiner [this message]
2011-05-19 16:49 ` [U-Boot] [PATCH 1/4] [v2] nand_base: trivial: fix comment read/write comment Ben Gardiner
2011-05-24 12:36 ` Detlev Zundel
2011-05-19 16:49 ` [U-Boot] [PATCH 2/4] [v2] nand_util: convert nand_write_skip_bad() to flags Ben Gardiner
2011-05-24 13:17 ` Detlev Zundel
2011-05-24 13:27 ` Ben Gardiner
2011-05-19 16:49 ` [U-Boot] [PATCH 3/4] [v2] nand_util: drop trailing all-0xff pages if requested Ben Gardiner
2011-05-24 13:23 ` Detlev Zundel
2011-05-19 16:49 ` [U-Boot] [PATCH 4/4] [v2] cmd_nand: add nand write.trimffs command Ben Gardiner
2011-05-24 13:22 ` Detlev Zundel
2011-05-24 13:30 ` Ben Gardiner
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=cover.1305823168.git.bengardiner@nanometrics.ca \
--to=bengardiner@nanometrics.ca \
--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