[U-Boot-Users] nand write.jffs2 addr ofs size, what does size mean?

[Thomas Kuhlmann <maillist@fsforth.de>]

Hello README.nand says:
> nand write.jffs2 addr ofs 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
>  after skipping the bad blocks. Compact images, such as those
>  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.

a) Is ofs+size-1 the maximal address where the NAND is accessed while writing?
b) Is add+size-1 the maximal address where the RAM is accessed while reading?
c) how does this change if bad blocks are detected?

e.g. in RAM at 200.000 is a 100.000bytes long jffs2 image generated by 
mkfs.jffs2. I wan't to install a JFFS2 with this content in NAND at 400.000 
with 100.000bytes.
# nand write.jffs2 200.000 400.000 100.000

what happens if the NAND has some bad blocks, does the write command writes 
beyond 500.000 to the NAND, or does it abort since there is not enough space 
available?

thank you for any hints,
-- 
Thomas Kuhlmann, FS Forth-Systeme GmbH, www.fsforth.de
Kueferstrasse 8, D-79206 Breisach, Germany
Phone: +49 (7667) 908 144 Fax: +49 (7667) 908 244