summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorWolfgang Denk <wd@denx.de>2012-05-20 22:47:40 +0200
committerWolfgang Denk <wd@denx.de>2012-05-20 22:47:40 +0200
commit8fa3d2b8161bb73b759c9db5c811c885ca5ec60c (patch)
treef7aab3c7e50e90c22338450b2f417b3fff12b8a3 /doc
parent8bd07c9aaf4628931ab8da6eb0f83e517d9381a7 (diff)
parente52fee9b04157c3f5bd73bb122e95d0c6ebb2270 (diff)
downloadu-boot-artik-8fa3d2b8161bb73b759c9db5c811c885ca5ec60c.tar.gz
u-boot-artik-8fa3d2b8161bb73b759c9db5c811c885ca5ec60c.tar.bz2
u-boot-artik-8fa3d2b8161bb73b759c9db5c811c885ca5ec60c.zip
Merge branch 'master' of git://git.denx.de/u-boot-nand-flash
* 'master' of git://git.denx.de/u-boot-nand-flash: NAND: Remove ONFI detection message to from bootup log driver/mtd:IFC: Fix possible memory leak driver/mtd: IFC NAND: Add support of ONFI NAND flash mtd, nand: move some printfs to debug output. nand_util: correct YAFFS image write function powerpc/85xx: fix NAND boot linker scripts for -fpic nand: extend .raw accesses to work on multiple pages
Diffstat (limited to 'doc')
-rw-r--r--doc/README.nand16
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/README.nand b/doc/README.nand
index 04a87c991..1602b5eee 100644
--- a/doc/README.nand
+++ b/doc/README.nand
@@ -94,14 +94,14 @@ Commands:
of data for one 512-byte page or 2 256-byte pages. There is no check
for bad blocks.
- nand read.raw addr ofs|partition
- Read page from `ofs' in NAND flash to `addr'. This reads the raw page,
- so ECC is avoided and the OOB area is read as well.
-
- nand write.raw addr ofs|partition
- Write page from `addr' to `ofs' in NAND flash. This writes the raw page,
- so ECC is avoided and the OOB area is written as well, making the whole
- page written as-is.
+ nand read.raw addr ofs|partition [count]
+ nand write.raw addr ofs|partition [count]
+ Read or write one or more pages at "ofs" in NAND flash, from or to
+ "addr" in memory. This is a raw access, so ECC is avoided and the
+ OOB area is transferred as well. If count is absent, it is assumed
+ to be one page. As with .yaffs2 accesses, the data is formatted as
+ a packed sequence of "data, oob, data, oob, ..." -- no alignment of
+ individual pages is maintained.
Configuration Options: