public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sun, 12 Apr 2009 13:53:21 +0200	[thread overview]
Message-ID: <49E1D631.7080801@bakke.com> (raw)
In-Reply-To: <49E1026F.3030006@zytor.com>

H. Peter Anvin wrote, On 04/11/2009 10:49 PM:
> Dag Bakke wrote:
>> 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?  :-)
>>
> 
> It's not our job to do yours for you.

Subtle hinting does the job, too. :-)


> *.o files contain a LOT of metadata.  The "size" command tells you the
> real size.

Probably.
Hand-editing the video*.o-files out of the Makefile and dropping the
call to set_video in main.c gained me 4768 bytes. Definitely less than
87kB, but posibly worth the effort. To me, anyway.

Sorry about the noise, thank you for replying.

For the benefit of other readers working on small kernelimages, this URL
may prove helpful:
http://elinux.org/Kernel_Size_Tuning_Guide


Dag B

  reply	other threads:[~2009-04-12 11:53 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
2009-04-11 20:49       ` H. Peter Anvin
2009-04-12 11:53         ` Dag Bakke [this message]
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=49E1D631.7080801@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