linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: linuxppc-embedded@ozlabs.org, gd.smth@gmail.com
Subject: Re: Viable PPC platform?
Date: Wed, 10 May 2006 09:48:10 -0700	[thread overview]
Message-ID: <20060510164810.GB32200@gate.ebshome.net> (raw)
In-Reply-To: <20060510121141.0a866b8f.ajz@cambridgebroadband.com>

On Wed, May 10, 2006 at 12:11:41PM +0100, Alex Zeffertt wrote:
> On Tue, 9 May 2006 10:15:20 -0700
> Eugene Surovegin <ebs@ebshome.net> wrote:
> 
> > On Tue, May 09, 2006 at 05:41:01PM +0100, Alex Zeffertt wrote:
> > > On Tue, 09 May 2006 10:38:19 -0400
> > > geneSmith <gd.smth@gmail.com> wrote:
> > > 
> > > > I have a ppc405gpr system with 64M ram and 4Meg flash in a
> > > > AM29LV320. Is this a viable platform for linux? Can a filesystem
> > > > (JFFS2?) be put this flash type?
> > > > 
> > > 
> > > I would create an initrd and put every file that doesn't need
> > > to be changed persistently into it instead of JFFS2.
> > 
> > After many years of doing embedded Linux stuff I still don't 
> > understand why people are so fond of initrd.
> > 
> > For temporary stuff - tempfs is much better and flexible. For r/o 
> > stuff - just make separate MTD partition (cramfs, squashfs) and
> > mount it directly as root. Both options will waste significantly
> > less memory.
> > 
> 
> Okay, let me qualify my answer.  It depends on whether you need to
> make persistent changes to the filesystem in flash.  If so, and given
> that your flash is only 4MB, I would recommend moving files to
> somewhere else, e.g. an initrd, because if when a JFFS2 FS is
> approaching full, you often find that writes to flash hang
> while JFFS2 searches for blocks to use as a scratchpad.  This has been
> my experience anyway.
> 
> If you don't need to make persistent changes to files, then I'm sure
> cramfs in flash as a rootfs would work well, with a tmpfs partition
> mounted on /tmp and /var.

You missed my point. initrd should be stored somewhere - in the same 
flash . In this case there is no reason to actually use initrd instead 
of just direct mount from flash.

-- 
Eugene

  reply	other threads:[~2006-05-10 16:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 14:38 Viable PPC platform? geneSmith
2006-05-09 15:34 ` Matt Porter
2006-05-09 16:41 ` Alex Zeffertt
2006-05-09 17:15   ` Eugene Surovegin
2006-05-09 22:31     ` Wolfgang Denk
2006-05-22 21:51       ` David Woodhouse
2006-05-22 22:15         ` Wolfgang Denk
2006-05-22 22:21           ` David Woodhouse
2006-05-10 11:11     ` Alex Zeffertt
2006-05-10 16:48       ` Eugene Surovegin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-09 22:52 Howard, Marc
2006-05-09 23:00 ` Eugene Surovegin
2006-05-09 23:11 Howard, Marc

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=20060510164810.GB32200@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=ajz@cambridgebroadband.com \
    --cc=gd.smth@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).