From: Dag Bakke <dag@bakke.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: video (VGA) object-files unconditionally built/included?
Date: Sat, 11 Apr 2009 13:51:48 +0200 [thread overview]
Message-ID: <49E08454.2060205@bakke.com> (raw)
In-Reply-To: <49E016EB.3000800@zytor.com>
H. Peter Anvin wrote, On 04/11/2009 06:04 AM:
> Andrew Morton wrote:
>>>
>>> The video* objects sums up to 87kB. Can I get rid of that somehow? I am
>>> using current git.
>>>
>>> This is my .config:
>>> http://tapas.homeip.net/~dagb/tiny.config
>>
>> I don't think those video things end up consuming memory after the
>> kernel has booted?
>>
>
> They aren't. Plus, they don't add up to 87K -- more like 13K.
>
First, I was more concerned about the size of the kernel image in the
flash memory, not runtime size. Is there an intrinsic reason these bits
must be part of the kernel image?
Second, my reasoning for the claim of 87k:
The build process goes like this:
[.....]
LZMA arch/x86/boot/compressed/vmlinux.bin.lzma
[....]
CC arch/x86/boot/video.o
CC arch/x86/boot/video-mode.o
CC arch/x86/boot/version.o
CC arch/x86/boot/video-vga.o
CC arch/x86/boot/video-vesa.o
CC arch/x86/boot/video-bios.o
[... no further compression? ...]
BUILD arch/x86/boot/bzImage
So the videobits appear to be built and added on to the kernel image
after the main chunk gets compressed. And the size of the video*.o
objects sums up to 87k.
If my reasoning is too stupid for words, would you mind providing a
graphical illustration of my stupidity? :-)
Dag B
next prev parent reply other threads:[~2009-04-11 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 11:30 video (VGA) object-files unconditionally built/included? Dag Bakke
2009-04-11 3:43 ` Andrew Morton
2009-04-11 4:04 ` H. Peter Anvin
2009-04-11 11:51 ` Dag Bakke [this message]
2009-04-11 20:49 ` H. Peter Anvin
2009-04-12 11:53 ` Dag Bakke
2009-04-12 23:06 ` H. Peter Anvin
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=49E08454.2060205@bakke.com \
--to=dag@bakke.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox