mtd/html/faq jffs2.xml,1.7,1.8

[jwboyer at infradead.org]

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

Modified Files:
	jffs2.xml 
Log Message:
Add a FAQ about mtdblock and JFFS2

Index: jffs2.xml
===================================================================
RCS file: /home/cvs/mtd/html/faq/jffs2.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- jffs2.xml	29 Mar 2006 16:48:06 -0000	1.7
+++ jffs2.xml	31 Mar 2006 14:38:41 -0000	1.8
@@ -45,6 +45,13 @@
 If you are desperate, then fix jffs2_dump to recreate the filesystem from the image. It's not hard. All the
 basics are done already.</p>
 
+<h3>Do I need to use mtdblock to mount my JFFS2 filesystem?</h3>
+<p>In general, mtdblock is not required to mount JFFS2 filesystems.  One can use the MTD device name or minor number to specify the MTD device that contains the JFFS2 filesystem.  For example, both:</p>
+<code>mount -t jffs2 mtd2 /foo</code><br />
+<code>mount -t jffs2 mtd:name_of_device /foo</code>
+<p>should both work assuming the device specified actually contains a valid JFFS2 filesystem.</p>
+<p>There are two cases where this does not work.  The first is when JFFS2 is used as a root filesystem.  For now, this requires the mtdblock device to be specified for <code>root=</code> on the kernel commandline.  The second case is when the mount binary that is being used does not play nicely with the above format.  The busybox version of mount is known to not work without the mtdblock device.</p>
+
 <h3>How do I get the 2.6 kernel to recognize JFFS2 as my rootfs?</h3>
 <p>With the 2.6 kernel, you will need to specify: <code>rootfstype=jffs2</code> on the kernel command line to use it as a root filesystem</p>