From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Nand: Implement raw read/write and biterr
Date: Mon, 19 Oct 2009 13:10:38 -0500 [thread overview]
Message-ID: <20091019181038.GA19293@loki.buserror.net> (raw)
In-Reply-To: <4AC3AFE1.2030506@windriver.com>
On Wed, Sep 30, 2009 at 02:22:09PM -0500, Tom wrote:
> John Rigby wrote:
>> @@ -494,13 +600,16 @@ U_BOOT_CMD(nand, CONFIG_SYS_MAXARGS, 1, do_nand,
>> "nand write - addr off|partition size\n"
>> " read/write 'size' bytes starting at offset 'off'\n"
>> " to/from memory address 'addr', skipping bad blocks.\n"
>> + " .oob - reads/writes oob only.\n"
>> + " .raw - reads/writes both main and oob with no error\n"
>> + " detection or correction\n"
>
> Writing the oob area directly is UNSAFE.
> Having done to myself, it was a pain to undo.
> You should put at least document that.
If we warn about oob being unsafe, the same warning should be made for
raw.
-Scott
next prev parent reply other threads:[~2009-10-19 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 18:11 [U-Boot] [PATCH] Nand: Implement raw read/write and biterr John Rigby
2009-09-30 19:22 ` Tom
2009-09-30 21:34 ` John Rigby
2009-10-19 18:10 ` Scott Wood [this message]
2009-10-19 19:04 ` Scott Wood
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=20091019181038.GA19293@loki.buserror.net \
--to=scottwood@freescale.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 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.