linux-mips
[Top] [All Lists]

Re: Building a stand-alone FS on a very limited flash (newbie question)

To: Wolfgang Denk <wd@denx.de>
Subject: Re: Building a stand-alone FS on a very limited flash (newbie question)
From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Date: Tue, 10 Jun 2003 14:56:23 +0200
Cc: Baruch Chaikin <bchaikin@il.marvell.com>, linux-mips@linux-mips.org, Rabeeh Khoury <rabeeh@galileo.co.il>
In-reply-to: <20030610123843.CDE2EC5FD7@atlas.denx.de>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20030609165612.GE32450@rembrandt.csv.ica.uni-stuttgart.de> <20030610123843.CDE2EC5FD7@atlas.denx.de>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.4i
Wolfgang Denk wrote:
[snip]
> > > The platform I'm using is very limited - only one MTD block of 
> > > 2.5 MB is available for the file system, out of a 4 MB flash:
> > >    0.5 MB is allocated for the firmware code
> > >    1.0 MB for the compressed kernel image
> > >    2.5 MB for the (compressed?) file system
> > > 
> > > For example, I've noticed LibC itself is ~5 MB !
> > 
> > You'll need a smaller libc, dietlibc comes to mind.
> > http://www.dietlibc.org/
> 
> I don't really understand what all this discussion is about.
> 
> 2.5 MB is plenty of space for a compressed ramdisk  image  using  the
> standard  C  library. The ramdisk image included with our ELDK is 1.3
> MB:
[snip]
> # ls -l lib | grep -v '^[ld]'
> total 2433

I conclude ELDK consists of little more than the basic networking utilities,
and the libc-related parts eat up most of the space. A more feature-rich
system probably can't afford to waste that much.


Thiemo

<Prev in Thread] Current Thread [Next in Thread>