From: Trevor Woerner <ppc339@vtnet.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] educate users about x86 specific kludges instead of hiding thier ignorance
Date: Thu, 15 May 2003 23:10:50 -0400 [thread overview]
Message-ID: <200305152310.50885.ppc339@vtnet.ca> (raw)
In-Reply-To: <20030515152245.A23204@forte.austin.ibm.com>
On May 15, 2003 04:22 pm, linas@austin.ibm.com wrote:
> On Thu, May 15, 2003 at 02:11:42PM -0500, Tony 'Nicoya' Mantler wrote:
> > Speaking of which, is it even possible these days to build a kernel
> > small enough for (non-b) zImage on x86? I think it's been a while
> > since I've even made one that can fit on a floppy.
>
> If you put most things into modules, then yes, its still very
> possible.
This might be hard to believe, but when I had to make small x86 kernels
(everything including compressed filesystem had to fit in 2MB) for a
little embedded device I was working with, I could usually make smaller
kernels by *not* turning on module support and simply including the
couple of modules I needed directly in the kernel. Being an embedded
device I didn't need very many extras. Enabling module support inflates
the kernel quite a bit, not to mention all the extra space for the
modules themselves and the modutils.
But yes, if you are trying to create a general kernel for a range of
devices (instead of one specific device) that have a lot of extras,
then building modules does keep the kernel size down.
I'm just trying to point out that there is a point where it makes more
sense to compile-in, rather than create modules, when trying to create
small kernels.
Trevor
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-05-16 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 7:42 [PATCH] educate users about x86 specific kludges instead of hiding thier ignorance Ethan Benson
2003-05-15 19:01 ` Tom Rini
2003-05-15 19:11 ` Tony 'Nicoya' Mantler
2003-05-15 20:22 ` linas
2003-05-16 3:10 ` Trevor Woerner [this message]
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=200305152310.50885.ppc339@vtnet.ca \
--to=ppc339@vtnet.ca \
--cc=linuxppc-dev@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.