mtd/html/tech nand.html,1.13,1.14

[gleixner at infradead.org]

Update of /home/cvs/mtd/html/tech
In directory phoenix.infradead.org:/tmp/cvs-serv23371/mtd/html/tech

Modified Files:
	nand.html 
Log Message:
tglx declares himself healed from temporary brain damage and comes back to the original plan of passing
oob-layout structures. This implies minor changes to filesystem layers, but removes file system dependend
code in nand.c/.h. For userspace apps ioctl (MEMSETOOBSEL) can pass a structure with the layout, which 
has to be used for functions  like read/write, which have no knowledge about oob-layout. see util/nandwrite.c
 



Index: nand.html
===================================================================
RCS file: /home/cvs/mtd/html/tech/nand.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- nand.html	18 Feb 2003 10:06:56 -0000	1.13
+++ nand.html	18 Feb 2003 20:53:55 -0000	1.14
@@ -368,7 +368,7 @@
 no partitions are used</i><br>
 SNIP<br>
 }</p>
-<p>If you use paritions, you should initialize the default oob-layout for each partition.
+<p>If you use paritions, you should initialize the default oob-layout for each partition.<br>
 static struct mtd_partition partition_info16k[] = {<br>
 	{ name: "YOURBOARD flash partition 1",<br>
 	  offset:  0,<br>
@@ -380,7 +380,7 @@
 	  oobsel:  NAND_YAFFS_OOB }<br>
 };<br>
 These settings are useful, if you write data from userspace to your chip, e.g. a filesystem image.
-The userspace functions don't know anything about NAND oob. A write would not calc ECC, if you 
+The userspace functions don't know anything about NAND oob. A write would not calc ECC. If you 
 set it for your desired fs-type, ECC will be calculated and written at the appropriate place on
 your chip. Same applies for read functions.</p> 
 
@@ -532,7 +532,8 @@
 <h4>Can I copy a JFFS2 Image to NAND via /dev/mtdX ?</h4>
 <p>Yes, as long as your chip does not contain bad blocks. Make sure, that the erasesize you set to mkfs.jffs2 
 is the same as the erasesize of your chip. Data will only be written with ECC, if your default settings for
-oob-layout selection are set for JFFS2. For bad block aware copying, use nandwrite from mtd-utils.
+oob-layout selection are set for JFFS2. For bad block aware copying, use nandwrite from mtd-utils.<br>
+nandwrite -j /dev/mtdX image
 </p>
 
 <h4>Can I use mtdutils erase / eraseall</h4>