From: Simon Schwarz <simonschwarzcor@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] NAND: Add nand read.raw and write.raw commands
Date: Fri, 26 Aug 2011 09:57:17 +0200 [thread overview]
Message-ID: <4E5751DD.3090203@gmail.com> (raw)
In-Reply-To: <1314309890-6613-1-git-send-email-marek.vasut@gmail.com>
Dear Marek,
On 08/26/2011 12:04 AM, Marek Vasut wrote:
> These commands should work around various "hardware" ECC and BCH methods. This
> is important for example in case where the user needs to write precisely what's
> in a buffer to a NAND page, with no interference of hardware ECC engine or such.
I think I don't get it :)
Where is the problem with writing this stuff to NAND now? If the ECC
interferes there was a problem with the NAND Flash therefore the data is
corrupted.
Regards
Simon
next prev parent reply other threads:[~2011-08-26 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 22:04 [U-Boot] [PATCH] NAND: Add nand read.raw and write.raw commands Marek Vasut
2011-08-26 7:57 ` Simon Schwarz [this message]
2011-08-26 14:49 ` Marek Vasut
2011-08-26 16:35 ` Simon Schwarz
2011-08-26 18:33 ` Wolfgang Denk
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=4E5751DD.3090203@gmail.com \
--to=simonschwarzcor@googlemail.com \
--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