Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jeff Baitis <baitisj@evolution.com>
To: Baruch Chaikin <bchaikin@il.marvell.com>
Cc: linux-mips@linux-mips.org, Rabeeh Khoury <rabeeh@galileo.co.il>,
	Baruch Chaikin <bchaikin@galileo.co.il>
Subject: Re: Building a stand-alone FS on a very limited flash (newbie  question)
Date: Mon, 9 Jun 2003 11:49:51 -0700	[thread overview]
Message-ID: <20030609114951.O29389@luca.pas.lab> (raw)
In-Reply-To: <3EE4C5CF.3050607@galileo.co.il>; from bchaikin@il.marvell.com on Mon, Jun 09, 2003 at 07:37:19PM +0200

I highly recommend looking at the UClibC project. Erik's code is a pleasure to
work with.  http://www.uclibc.org/

It is even possible to build libstdc++ with UClibC, if you are so inclined...
And, a number of commercial projects use UClibC , such as Linksys:
http://lkml.org/archive/2003/6/7/164/index.html

and Belkin:

http://lkml.org/archive/2003/6/8/31/index.html

<shameless YRO plug>

-Jeff



On Mon, Jun 09, 2003 at 07:37:19PM +0200, Baruch Chaikin wrote:
> Hi all,
> 
> I'm using MIPS kernel 2.4.18 with NFS file system mounted on a RedHat 
> machine. This works fine, but is unsuitable for system deployment. Do 
> you have hints for me where to start, in order to put the file system on 
> flash? 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 !
> 
> Thanks for any tip,
> -    Baruch.
> 
> 
> 

-- 
         Jeffrey Baitis - Associate Software Engineer

                    Evolution Robotics, Inc.
                     130 West Union Street
                       Pasadena CA 91103

 tel: 626.535.2776  |  fax: 626.535.2777  |  baitisj@evolution.com 

  parent reply	other threads:[~2003-06-09 18:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 16:55 state of 64 bit support David Kesselring
2003-06-09 15:28 ` Maciej W. Rozycki
2003-06-09 15:44   ` Daniel Jacobowitz
2003-06-09 17:37     ` Building a stand-alone FS on a very limited flash (newbie question) Baruch Chaikin
2003-06-09 16:56       ` Thiemo Seufer
2003-06-10 12:26         ` Johannes Stezenbach
2003-06-10 12:38         ` Wolfgang Denk
2003-06-10 12:56           ` Thiemo Seufer
2003-06-10 13:15             ` Wolfgang Denk
2003-06-15 15:47               ` Baruch Chaikin
2003-06-15 15:47                 ` Baruch Chaikin
2003-06-17 12:16                 ` Johannes Stezenbach
2003-06-09 17:37       ` Baruch Chaikin
2003-06-09 18:49       ` Jeff Baitis [this message]
2003-06-09 19:01         ` Jeff Baitis
  -- strict thread matches above, loose matches on Subject: below --
2003-06-10 10:13 Tor Arntsen

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=20030609114951.O29389@luca.pas.lab \
    --to=baitisj@evolution.com \
    --cc=bchaikin@galileo.co.il \
    --cc=bchaikin@il.marvell.com \
    --cc=linux-mips@linux-mips.org \
    --cc=rabeeh@galileo.co.il \
    /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