linux-kernel - Re: video (VGA) object-files unconditionally built/included?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090410204308.155b7d65.akpm@linux-foundation.org>
Date:	Fri, 10 Apr 2009 20:43:08 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Dag Bakke <dag@...ke.com>
Cc:	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: video (VGA) object-files unconditionally built/included?

On Fri, 10 Apr 2009 13:30:22 +0200 Dag Bakke <dag@...ke.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?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/