From: Saravanan Chanemouganandam <schane@osmozis.com>
To: linux-mtd@lists.infradead.org
Subject: Re: transfer jffs2 rootFS to Nand flash
Date: Thu, 30 Aug 2007 17:58:55 +0200 [thread overview]
Message-ID: <200708301758.56358.schane@osmozis.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708301708240.4036@lnxricardw.se.axis.com>
Hi all,
I got my problem fix up by gurus. The work around solution to transfer jffs2
rootfs on the cm-x270 nand ( /dev/mtdblock1 ) is to have the following
kernel configuration setup.
CONFIG_ARMCORE_FLASH is not set
CONFIG_ARMCORE_NAND is not set
CONFIG_MTD_NAND_CM_X270 is set
The "compulab Nand flash" block driver CONFIG_ARMCORE_NAND initializes
(erases) nand contents on each reboot that causes the jffs2 rootfs mounting
failure.
Unconfig CONFIG_ARMCORE_NAND fixs the problem and the jffs2 rootfs on the
cm-x270 nand mounted succesfully.
IP-Config: Complete:
device=eth0, addr=192.168.6.203, mask=255.255.255.0, gw=192.168.6.1,
host=cm-x270, domain=, nis-domain=(none),
bootserver=192.168.6.1, rootserver=192.168.6.1, rootpath=
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 120K
Regards,
Sara
Le Jeudi 30 Août 2007 17:09, vous avez écrit :
> On Thu, 30 Aug 2007, Saravanan Chanemouganandam wrote:
> > I have unconfigured the compulab NAND flash block driver which
> > reinitialise (erases on reboot) each and everytime of reboot that
> > conflicts with MTD nand driver.
>
> That would definitely explain the symptoms you were seeing (no jffs2 nodes
> found when mounting the rootfs).
>
> > This fixed my problem and I can be able to successfully mount the jffs2
> > rootfs.
> >
> > IP-Config: Complete:
> > device=eth0, addr=192.168.6.202, mask=255.255.255.0, gw=192.168.6.1,
> > host=cm-x270, domain=, nis-domain=(none),
> > bootserver=192.168.6.1, rootserver=192.168.6.1, rootpath=
> > VFS: Mounted root (jffs2 filesystem).
> > Freeing init memory: 120K
> > INIT: version 2.86 booting
> >
> > Thanks a lot for your comments and your valuable time.
>
> Great!
>
> /Ricard
> --
> Ricard Wolf Wanderlöf ricardw(at)axis.com
> Axis Communications AB, Lund, Sweden www.axis.com
> Phone +46 46 272 2016 Fax +46 46 13 61 30
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2007-08-30 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 14:10 transfer jffs2 rootFS to Nand flash Saravanan Chanemouganandam
2007-08-29 14:42 ` Ricard Wanderlof
[not found] ` <200708301345.36832.schane@osmozis.com>
2007-08-30 11:51 ` Ricard Wanderlof
[not found] ` <200708301655.54224.schane@osmozis.com>
2007-08-30 15:09 ` Ricard Wanderlof
2007-08-30 15:58 ` Saravanan Chanemouganandam [this message]
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=200708301758.56358.schane@osmozis.com \
--to=schane@osmozis.com \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox