From: Jari <jari.nguyen@serialsystem.com.sg>
To: Dan Malek <dan@mvista.com>
Cc: Prashant Patel <pmpatel@trinetcommunication.com>,
linuxppc-embedded@lists.linuxppc.org,
thanh_nguyen@smartstors.com
Subject: Re: 4MB DRAM is enough for linux kernel 2.2.13
Date: Wed, 20 Sep 2000 09:28:05 +0700 [thread overview]
Message-ID: <39C820B5.D34ADBE1@serialsystem.com.sg> (raw)
In-Reply-To: 39C7A03A.93075582@mvista.com
Hello,
I'm a newbie. Help me!!!!!
Can anybody tell me the minimum size of the linux kernel 2.2.13 that we can
reduce?
(this kernel doesn't need console, anything else ... just boot and run my own
program)
If I want to support only ftp, what is the minimum size of ramdisk ?
I think if I reduce the code of the kernel and the library libc6, 4MB is OK.
Is that right?
best regards,
Jari
ps: Hi Dan "grandfather of all of these", you wrote:
> I like MMUs because I don't have a real life.
How old are you in this life?
I've just had my full-month celebration. ;-))) just relax....
Dan Malek wrote:
> Prashant Patel wrote:
> >
> > Hello Everybody
> > Can someone tell me if 4MB DRAM is enough to boot linux kernel
> > 2.2.13. Note that the 8xx rom boot loader occupies around 500k.
>
> Yes, I can say it will not work.
>
> The code in the arch/ppc/mbxboot directory, which is used for
> all 8xx and 8260 processors, assumes there is memory above 4 MB
> it can use for buffer space while decompressing the kernel. You
> can play around with adjusting these addresses and sizes, and get
> a kernel to boot. You will get a shell prompt, and that is about
> all. You won't be able to use a ramdisk, you probably won't be
> able to execute any useful programs.
>
> -- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-20 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-19 17:03 4MB DRAM is enough for linux kernel 2.2.13 Prashant Patel
2000-09-19 17:19 ` Dan Malek
2000-09-20 2:28 ` Jari [this message]
2000-09-20 3:08 ` Graham Stoney
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=39C820B5.D34ADBE1@serialsystem.com.sg \
--to=jari.nguyen@serialsystem.com.sg \
--cc=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pmpatel@trinetcommunication.com \
--cc=thanh_nguyen@smartstors.com \
/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).