linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Jeff Angielski" <jangiels@speakeasy.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux hanging on Xilinx SystemACE
Date: Wed, 16 Aug 2006 17:28:54 -0600	[thread overview]
Message-ID: <528646bc0608161628t2dc068d0g8862d8e8dd202170@mail.gmail.com> (raw)
In-Reply-To: <1155766078.10357.16.camel@sumo-jaa>

On 8/16/06, Jeff Angielski <jangiels@speakeasy.net> wrote:
> And like somebody else mentioned, if you are really going to use this
> for an embedded system, you are going to want to rethink your
> partitioning scheme.
>
> Maybe something like:
>
> p1 fat12 - kernel and binary image
> p2 ext2 - read only rootfs
> p3 ext3 - non volatile, slow rate data rootfs
> p4 tmpfs - volatile, high rate data rootfs

Or, if you have enough ram (and a small enough rootfs footprint); put
the rootfs into an initramfs and leave the CF alone entirely after
boot.  On small systems, I store all config parameters in a flat file
on the fat partition, and only write it out when it needs to save a
new configuration.  That way the entire system consists of three
files; a kernel, a rootfs image and a config file.  Makes managing
updates very easy.  :)

g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

      reply	other threads:[~2006-08-16 23:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 21:06 Linux hanging on Xilinx SystemACE Clint Thomas
2006-08-16 21:48 ` Grant Likely
2006-08-17  0:51   ` Jeff Angielski
2006-08-17  1:40     ` Grant Likely
2006-08-16 22:01 ` Keith J Outwater
2006-08-21 20:45   ` Clint Thomas
2006-08-21 21:16     ` Keith J Outwater
2006-08-16 22:07 ` Jeff Angielski
2006-08-16 23:28   ` Grant Likely [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=528646bc0608161628t2dc068d0g8862d8e8dd202170@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=jangiels@speakeasy.net \
    --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).