linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Fabien Oriede <fabien.oriede@yahoo.fr>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: suffisant space for U-Boot, Linux and an initrd image ? (4MB SDRAM)
Date: Tue, 05 Aug 2008 00:59:57 +0200	[thread overview]
Message-ID: <20080804225958.0827524848@gemini.denx.de> (raw)
In-Reply-To: Your message of "Mon, 04 Aug 2008 12:54:00 -0000." <789365.58211.qm@web27401.mail.ukl.yahoo.com>

In message <789365.58211.qm@web27401.mail.ukl.yahoo.com> you wrote:
>
> I would like to know if this is possible to port U-Boot, Linux and an initrd image on a board with 4MB of SDRAM ?

In Theory it may be possible, but just for very tiny demo
applications. Probably not for a useful device.

> When Linux try to boot, there is this line on the terminal :
> "Memory : 2036k available (1036k kernel code, 256k data, 80k init, 0k highmem)"
> So I have 2036k memory available for my initrd image but I don't know if this is suffisant.

Note that a ramdisk is NOT an efficient way to use memory. See fro
example http://www.denx.de/wiki/view/DULG/RootFileSystemSelection
which shows that for example a cramfs image is not only faster to boot
but also needs less RAM.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Keep your head and your heart going in the right  direction  and  you
will not have to worry about your feet.

      parent reply	other threads:[~2008-08-04 23:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 12:54 suffisant space for U-Boot, Linux and an initrd image ? (4MB SDRAM) Fabien Oriede
2008-08-04 13:43 ` Marco Stornelli
2008-08-04 22:59 ` Wolfgang Denk [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=20080804225958.0827524848@gemini.denx.de \
    --to=wd@denx.de \
    --cc=fabien.oriede@yahoo.fr \
    --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).