diff options
| author | Stefan Roese <sr@denx.de> | 2006-10-28 15:55:52 +0200 | 
|---|---|---|
| committer | Stefan Roese <sr@denx.de> | 2006-10-28 17:11:10 +0200 | 
| commit | 856f054410cef52d868feb330168b2a4c4091328 (patch) | |
| tree | 75995d4bfa2f99852917e5ca035406dd91f6953f /doc/README.nand | |
| parent | 07a69a18c2ecfda904231fdf23e2523ea7792eb6 (diff) | |
| download | olio-uboot-2014.01-856f054410cef52d868feb330168b2a4c4091328.tar.xz olio-uboot-2014.01-856f054410cef52d868feb330168b2a4c4091328.zip | |
[PATCH] NAND: Partition name support added to NAND subsystem
chpart, nboot and NAND subsystem related commands now accept also partition
name to specify offset.
Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
Signed-off-by: Stefan Roese <sr@denx.de>
Diffstat (limited to 'doc/README.nand')
| -rw-r--r-- | doc/README.nand | 29 | 
1 files changed, 17 insertions, 12 deletions
| diff --git a/doc/README.nand b/doc/README.nand index 5279a4f2b..b5171f4d4 100644 --- a/doc/README.nand +++ b/doc/README.nand @@ -34,14 +34,19 @@ Commands:     nand device num        Make device `num' the current device and print information about it. -   nand erase off size -   nand erase clean [off size] -      Erase `size' bytes starting at offset `off'.  Only complete erase -      blocks can be erased. +   nand erase off|partition size +   nand erase clean [off|partition size] +      Erase `size' bytes starting at offset `off'. Alternatively partition +      name can be specified, in this case size will be eventually limited +      to not exceed partition size (this behaviour applies also to read +      and write commands). Only complete erase blocks can be erased. + +      If `erase' is specified without an offset or size, the entire flash +      is erased. If `erase' is specified with partition but without an +      size, the entire partition is erased.        If `clean' is specified, a JFFS2-style clean marker is written to -      each block after it is erased. If `clean' is specified without an -      offset or size, the entire flash is erased. +      each block after it is erased.        This command will not erase blocks that are marked bad. There is        a debug option in cmd_nand.c to allow bad blocks to be erased. @@ -51,28 +56,28 @@ Commands:     nand info        Print information about all of the NAND devices found. -   nand read addr ofs size +   nand read addr ofs|partition size        Read `size' bytes from `ofs' in NAND flash to `addr'. If a page        cannot be read because it is marked bad or an uncorrectable data        error is found the command stops with an error. -   nand read.jffs2 addr ofs size +   nand read.jffs2 addr ofs|partition size        Like `read', but the data for blocks that are marked bad is read as        0xff. This gives a readable JFFS2 image that can be processed by        the JFFS2 commands such as ls and fsload. -   nand read.oob addr ofs size +   nand read.oob addr ofs|partition size        Read `size' bytes from the out-of-band data area corresponding to        `ofs' in NAND flash to `addr'. This is limited to the 16 bytes of        data for one 512-byte page or 2 256-byte pages. There is no check        for bad blocks or ECC errors. -   nand write addr ofs size +   nand write addr ofs|partition size        Write `size' bytes from `addr' to `ofs' in NAND flash. If a page        cannot be written because it is marked bad or the write fails the        command stops with an error. -   nand write.jffs2 addr ofs size +   nand write.jffs2 addr ofs|partition size        Like `write', but blocks that are marked bad are skipped and the        is written to the next block instead. This allows writing writing        a JFFS2 image, as long as the image is short enough to fit even @@ -80,7 +85,7 @@ Commands:        produced by mkfs.jffs2 should work well, but loading an image copied        from another flash is going to be trouble if there are any bad blocks. -   nand write.oob addr ofs size +   nand write.oob addr ofs|partition size        Write `size' bytes from `addr' to the out-of-band data area        corresponding to `ofs' in NAND flash. This is limited to the 16 bytes        of data for one 512-byte page or 2 256-byte pages. There is no check |