From: Andrew Morton <akpm@linux-foundation.org>
To: Dag Bakke <dag@bakke.com>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: video (VGA) object-files unconditionally built/included?
Date: Fri, 10 Apr 2009 20:43:08 -0700 [thread overview]
Message-ID: <20090410204308.155b7d65.akpm@linux-foundation.org> (raw)
In-Reply-To: <49DF2DCE.5050102@bakke.com>
On Fri, 10 Apr 2009 13:30:22 +0200 Dag Bakke <dag@bakke.com> wrote:
> Hi.
>
> I am putting together a tiny kernel for an embedded x86 target. Space is
> tight, so I try to shave every kB I can get rid of.
> I don't have anything resembling VGA or graphics, and my .config
> reflects that. (Serial console.)
>
> Yet, when building the kernel I see:
>
> 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
>
> # strings arch/x86/boot/bzImage | egrep -i 'vesa|vga|bios|mode'
> +VESA
> 0123456789ABCDEFPress <ENTER> to see video modes available, <SPACE> to
> continue, or wait 30 sec
> Mode: Resolution: Type:
> Enter a video mode or "scan" to scan for additional modes:
> Undefined video mode number: %x
> VESA
> BIOS
>
>
> 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?
next prev parent reply other threads:[~2009-04-11 3:45 UTC|newest]
Thread overview: 8+ 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 [this message]
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
2009-04-12 23:06 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2009-04-10 16:55 Dag Bakke
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=20090410204308.155b7d65.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dag@bakke.com \
--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 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.