From: Conn Clark <clark@esteem.com>
To: Ken Applebaum <applebaumk@embeddedplanet.com>,
May Ling List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: kernel size
Date: Thu, 11 Apr 2002 09:40:17 -0700 [thread overview]
Message-ID: <3CB5BC71.AABD12C7@esteem.com> (raw)
In-Reply-To: D73A25AA6E54D511AD74009027B1110F237353@ORION
Ken Applebaum wrote:
>
> I know that this list is usually reserved for discussions of bringing up
> kernels, but I have a question on kernel size.
>
> What is the smallest size of kernel (including tcp/ip) that people have been
> able to build? Do the folks on this list see the large size as an issue to
> further adoption of linux on the PowerQuicc processors?
>
> Ken
>
It all depends on what size you are refering to. Is it the size
of the compressed zImage, the compressed bzImage , the uncompressed
image, or the runtime RAM usage?
Our zImage is just about 400,000 bytes. Our uncompressed image
is about 1 MB. The others sizes I haven't looked at. Our kernel could
be smaller if we left out fpu emulation and other modules.
I see this as an issue that is becoming less and less
important as RAM and flash storage technology increase in size and
drop in price.
See what Wolfgang accomplished here.
http://www.denx.de/embedded-ppc-en.html
Its about mid page under the heading "PowerPC based Web Server" .
Hope this is helpful
Conn
--
*****************************************************************
If you live at home long enough, your parents will move out.
*****************************************************************
Conn Clark
Engineering Stooge clark@esteem.com
Electronic Systems Technology Inc. www.esteem.com
Stock Ticker Symbol ELST
"clark@esteem.com" Copyright 2000 By Electronic Systems Technology
This email address may be used to communicate to Conn Clark
provided it is not being used for advertisement purposes, unless
prior written consent is given. This email address may not be
sold under any circumstances. All other rights reserved.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-11 16:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 15:38 kernel size Ken Applebaum
2002-04-11 16:40 ` Conn Clark [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-13 4:38 Kernel size rohit prasad
2001-12-07 8:53 kernel size rohit prasad
2001-12-07 16:46 ` Eli Carter
2001-10-09 14:16 VDA
2001-10-09 13:26 ` [solid]
2001-10-09 13:28 ` Nikita Danilov
2001-10-09 14:16 ` Richard B. Johnson
2001-10-09 14:43 ` Ingo Oeser
2001-10-09 14:52 ` Richard B. Johnson
2001-10-09 15:43 ` Horst von Brand
2001-10-09 15:53 ` Richard B. Johnson
2001-10-10 1:29 ` Keith Owens
2001-10-10 13:00 ` Richard B. Johnson
2001-10-10 14:47 ` vda
2001-10-11 12:41 ` vda
2001-10-10 1:30 ` Kenneth Johansson
2001-10-09 15:55 ` Jakub Jelinek
2001-10-10 1:27 ` Keith Owens
2001-10-04 13:11 Security question: "Text file busy" overwriting executables but not shared libraries? Eric W. Biederman
2001-10-04 14:24 ` Kernel size Richard B. Johnson
2001-10-13 20:35 ` Aaron Lehmann
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=3CB5BC71.AABD12C7@esteem.com \
--to=clark@esteem.com \
--cc=applebaumk@embeddedplanet.com \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.