From: "Andrew Victor" <avictor.za@gmail.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
Andrew Victor <linux@maxim.org.za>,
Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: [patch 2.6.27-rc2] MTD: make dataflash write-verify be optional
Date: Thu, 7 Aug 2008 12:40:47 +0200 [thread overview]
Message-ID: <cd73a99e0808070340s29932337o74293afc91d128f4@mail.gmail.com> (raw)
In-Reply-To: <200808062155.14366.david-b@pacbell.net>
hi,
> It doesn't seem to add a
> lot in terms of reliability, and wouldn't detect errors which
> crop up when transferring data to the on-chip SRAM buffer.
Yes, it was originally added for detecting bad/dead bits on the flash.
[I think some (obsolete) DataFlash revisions (C?) didn't have the
compare functionality, though revision B did. Or atleast it wasn't
defined in the rev C datasheets. It did return "success" on those
chips though].
Acked-by: Andrew Victor <linux@maxim.org.za>
prev parent reply other threads:[~2008-08-07 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 4:55 [patch 2.6.27-rc2] MTD: make dataflash write-verify be optional David Brownell
2008-08-07 10:34 ` Haavard Skinnemoen
2008-08-07 10:40 ` Andrew Victor [this message]
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=cd73a99e0808070340s29932337o74293afc91d128f4@mail.gmail.com \
--to=avictor.za@gmail.com \
--cc=david-b@pacbell.net \
--cc=dwmw2@infradead.org \
--cc=hskinnemoen@atmel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@maxim.org.za \
/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