public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Andrew Dixon <andrew.dixon@seranoa.com>
To: ppcboot-users <ppcboot-users@lists.sourceforge.net>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: PPCBoot can't read my jffs2 image
Date: Tue, 02 Apr 2002 09:28:11 -0500	[thread overview]
Message-ID: <3CA9BFFB.CDE0382B@seranoa.com> (raw)

Hi Everyone,

Sorry for the cross post but this a problem with the way the linux-mtd
layer and PPCBoot are interacting.

So here's the situation, I've got PPCBoot+Linux running on a custom
board.  I've formatted the flash to be one small raw partition for
PPCBoot and the rest is a jffs2 filesystem.  PPCBoot is reading Linux
and an initial ramdisk out of the jffs2.  In my original testing I was
booting the board via tftp and nfs and then copying copying the
filesystem onto the flash via /dev/mtdblock1.  This works great.  I
reboot and PPCBoot sees everything in the jffs2.  Now I'm trying to
automate this a little more so enhanced my build to give me a jffs2
image "wombat.jffs2".  I create this image with mkfs.jffs2 and put it
onto the flash by dd'ing it to /dev/mtd1:

	dd if=/wombat.jffs2 of=/dev/mtd1

now when I mount /dev/mtdblock1 I can see the filesystem that I've put
over there but when I reboot PPCBoot doesn't see any of the files that
are there.  But if I boot back up Linux can still see all of those files
OK.

Any ideas?  

Thanks,
Andy 
-- 
Andrew Dixon
Software Engineer
Seranoa Networks
978.897.3434 x231

             reply	other threads:[~2002-04-02 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 14:28 Andrew Dixon [this message]
2002-04-02 17:55 ` [Ppcboot-users] PPCBoot can't read my jffs2 image Nye Liu
2002-04-02 17:58 ` Jörn Engel

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=3CA9BFFB.CDE0382B@seranoa.com \
    --to=andrew.dixon@seranoa.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ppcboot-users@lists.sourceforge.net \
    /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