From: Pantelis Antoniou <panto@intracom.gr>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: looking for a model for building CRAMFS(?)-based system
Date: Thu, 17 Mar 2005 16:12:06 +0200 [thread overview]
Message-ID: <42399036.3010609@intracom.gr> (raw)
In-Reply-To: <Pine.LNX.4.61.0503161125560.5095@localhost.localdomain>
Robert P. J. Day wrote:
> i'm hoping someone has an example of the following that they're
> willing to share.
>
> currently, the system i've built for our 850 board incorporates
>
> - boot loader (sadly, not u-boot, but i'm working on it)
> - standard zImage.initrd.bin kernel+initrd image
> ... mountable JFFS2 filesystem with persistent stuff ...
>
> obviously, with this layout, it's kind of a nuisance to update
> anything individually in the initrd portion of the system, so i'd like
> to at least experiment with a layout that has separate
>
> - boot loader (ideally, u-boot)
> - kernel image
> - updateable (normally mounted read-only?) root filesystem
> ... rest of stuff the same ...
>
> i'm going to start over at DENX with their docs since that seems to
> be the canonical place to get the scoop on this but, in the meantime,
> if anyone has built something like this and is willing to share, say,
> their makefile so i can see how it goes together, i'd be thrilled.
>
> if your example happens to *require* u-boot, well, perhaps so much
> the better since that will give me the incentive to switch. :-)
We use a scheme on NAND with redundant cramfs rootfs partitions
that also contain the proper kernel image(s).
It is u-boot specific since it depends on u-boot loading the
cramfs kernel image.
For persistent storage we use a small JFFS2 partition.
>
> thanks.
>
> rday
Regards
Pantelis
next prev parent reply other threads:[~2005-03-17 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 16:33 looking for a model for building CRAMFS(?)-based system Robert P. J. Day
2005-03-17 14:12 ` Pantelis Antoniou [this message]
2005-03-17 14:59 ` Patrick Huesmann
2005-03-17 15:14 ` Robert P. J. Day
2005-03-17 15:42 ` Patrick Huesmann
2005-03-17 16:32 ` Wolfgang Denk
2005-03-17 16:35 ` Robert P. J. Day
2005-03-17 22:52 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-03-17 16:17 Fillod Stephane
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=42399036.3010609@intracom.gr \
--to=panto@intracom.gr \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rpjday@mindspring.com \
/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.