From: Baruch Chaikin <bchaikin@il.marvell.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-mips@linux-mips.org, Rabeeh Khoury <rabeeh@galileo.co.il>,
Baruch Chaikin <bchaikin@galileo.co.il>
Subject: Building a stand-alone FS on a very limited flash (newbie question)
Date: Mon, 09 Jun 2003 19:37:19 +0200 [thread overview]
Message-ID: <3EE4C5CF.3050607@galileo.co.il> (raw)
In-Reply-To: 20030609154408.GA1781@nevyn.them.org
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.
WARNING: multiple messages have this Message-ID (diff)
From: 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: Building a stand-alone FS on a very limited flash (newbie question)
Date: Mon, 09 Jun 2003 19:37:19 +0200 [thread overview]
Message-ID: <3EE4C5CF.3050607@galileo.co.il> (raw)
Message-ID: <20030609173719.BcFtRz5qBDSMhjxc18c4qPBh2zQtK0rfEi7yp-MLJNs@z> (raw)
In-Reply-To: 20030609154408.GA1781@nevyn.them.org
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.
next prev parent reply other threads:[~2003-06-09 16:36 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 ` Baruch Chaikin [this message]
2003-06-09 16:56 ` Building a stand-alone FS on a very limited flash (newbie question) 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
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=3EE4C5CF.3050607@galileo.co.il \
--to=bchaikin@il.marvell.com \
--cc=bchaikin@galileo.co.il \
--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