From: Nethra <nethra_gmit@yahoo.co.in>
To: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] jffs2 file system
Date: Thu, 22 Feb 2007 20:28:57 -0800 (PST) [thread overview]
Message-ID: <9113399.post@talk.nabble.com> (raw)
In-Reply-To: <200702221229.51830.juergen.beisert@weihenstephan.org>
thanks...
what are the steps to create jffs2 image?
do i need to disable nfs option in kernel?
what r steps for jffs2 mounting after nfs mounting on the board?
nethra
> do i need to mention mtdparts in command line....i thought that it is
> enabled in case if we want we can specify partitions in command line
> itself.
The kernel does not know anything about your flash partitioning. Where is
mtd0
starting in your flash? At the baseaddress of the flash?
> do i need to disable ramdisk option in kernel config for jffs2 booting?
No.
On my MPC5200 based system I start the kernel with this partition command:
mtdparts=phys_mapped_flash:256k(ubootl),1792k(kernel),13312k(jffs2),256k(uboot)ro,-(space)
root=/dev/mtdblock2 rootfstype=jffs2
Juergen
--
View this message in context: http://www.nabble.com/jffs2-file-system-tf3271928.html#a9113399
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-02-23 4:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 10:16 jffs2 file system Nethra
2007-02-22 10:27 ` Juergen Beisert
2007-02-22 10:58 ` [PATCH] " Nethra
2007-02-22 11:29 ` Juergen Beisert
2007-02-23 4:28 ` Nethra [this message]
2007-02-23 14:55 ` Ben Warren
2007-02-24 3:19 ` Nethra
2007-02-24 3:25 ` Ben Warren
2007-02-24 3:38 ` Nethra
2007-02-24 3:45 ` Nethra
2007-02-22 11:44 ` Josh Boyer
2007-02-24 8:38 ` [PATCH] " Nethra
2007-02-24 17:30 ` Juergen Beisert
2007-02-26 3:28 ` Nethra
2007-02-24 22:15 ` Ben Warren
2007-02-26 3:04 ` Nethra
2007-02-26 9:14 ` Nethra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9113399.post@talk.nabble.com \
--to=nethra_gmit@yahoo.co.in \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.