From: Karim Yaghmour <karim@opersys.com>
To: Jack Lu <jlu@rdmcorp.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: the procedure setting up jffs2
Date: Thu, 12 Sep 2002 18:37:53 -0400 [thread overview]
Message-ID: <3D811741.FB5178A@opersys.com> (raw)
In-Reply-To: DFEAJMIABOLKNEBOPGDHAECJCBAA.jlu@rdmcorp.com
Jack Lu wrote:
> I am using RPX850 Lite with 16MB flash(4 chips of Am29Lv320MB) with buswidth
> 32 and interleave 4.
> I have complied the MTD and JFFS2 module into the kernel.
> When I start up the Linux, Linux found the 16MB flash, the whole flash
> corresponds to /dev/mtd0.
>
> 1. where can I get the mkfs.jffs2 excutable for MPC850?
Hmm... There are quite a few places that provide pre-packaged PPC tools,
Denx (denx.de) is one of those. If you have the cross-compiling tools
already, then building it on your own should be fairly easy also.
> 2. the bottom 256KB is the boot loader code of the 16MB flash. the rest si
> for storing data
> if I do
> #cat jffs2.image > /dev/mtd0
> will the bootloader be erased?
The chip you mention is bottom-boot, so the above will very likely wipe-out
the bootloader. You probably want to partition your MTD device by modifying
the mapping driver and then write the JFFS2 image to another partition then
/dev/mtd0. Check drivers/mtd/tqm8xxl.c for an example.
Karim
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
next prev parent reply other threads:[~2002-09-12 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 8:37 the procedure setting up jffs2 Jack Lu
2002-09-12 22:37 ` Karim Yaghmour [this message]
2002-09-12 23:14 ` Wolfgang Denk
2002-09-13 0:15 ` Karim Yaghmour
2002-09-13 8:35 ` Marius Groeger
2002-09-13 9:07 ` David Woodhouse
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=3D811741.FB5178A@opersys.com \
--to=karim@opersys.com \
--cc=jlu@rdmcorp.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