All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Crowe <mac@mcrowe.com>
To: linux-mtd@lists.infradead.org
Cc: Mike Crowe <mac@mcrowe.com>
Subject: [PATCH 0/2] Support skipping bad blocks when seeking to start address
Date: Wed,  4 Jan 2017 14:18:04 +0000	[thread overview]
Message-ID: <1483539486-16165-1-git-send-email-mac@mcrowe.com> (raw)

I found myself needing to write and verify part of a partition that
will be read by the bootloader by skipping blocks from the start of
the partition. Initially I added separate --input-skip and
--output-skip options but David Oberhollenzer suggested in
<cdfdbe5d-1aa8-e424-7691-338d0d63f7b1@sigma-star.at> that a simple
flag to indicate that the start address should skip bad blocks would
avoid ambiguity.

David also suggested that I skip the bad blocks in a separate step
before the already-cluttered main loop.

Mike Crowe (2):
  nandwrite: Add --skip-bad-blocks-to-start option
  nanddump: Add --skip-bad-blocks-to-start option

 nand-utils/nanddump.c  | 23 +++++++++++++++++++++++
 nand-utils/nandwrite.c | 26 ++++++++++++++++++++++++++
 2 files changed, 49 insertions(+)

-- 
2.1.4

             reply	other threads:[~2017-01-04 14:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 14:18 Mike Crowe [this message]
2017-01-04 14:18 ` [PATCH 1/2] nandwrite: Add --skip-bad-blocks-to-start option Mike Crowe
2017-01-04 14:18 ` [PATCH 2/2] nanddump: " Mike Crowe
2017-01-05 13:38 ` [PATCH 0/2] Support skipping bad blocks when seeking to start address goliath
2017-01-05 14:18   ` Mike Crowe
2017-01-05 14:48     ` Boris Brezillon
2017-01-05 15:04       ` Mike Crowe
2017-01-09 12:18         ` David Oberhollenzer
2017-01-09 14:51           ` Mike Crowe
2017-01-11 16:22             ` Mike Crowe
2017-01-17 11:54 Mike Crowe
2017-01-23  6:47 ` David Oberhollenzer

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=1483539486-16165-1-git-send-email-mac@mcrowe.com \
    --to=mac@mcrowe.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.