All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: large uImage size
Date: Sun, 13 Jan 2008 10:33:14 -0500	[thread overview]
Message-ID: <478A2F3A.4090402@balister.org> (raw)
In-Reply-To: <200801131718.55872.risto@wapice.com>

[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]

Risto Pajula wrote:
> Hello.
> 
> I am getting very large kernel image size (~4,5 MB) when using the 
> cross-compiler built with a recent version of openembedded. Normal kernel 
> image size is around 1,5 MB. The large kernel image size only happens when 
> building the kernel outside the openembedded build environment, when building 
> with the normal OE build (bitbake minimal-image) the resulting kernel image 
> size is normal.

The newer version of binutils does this. This patch should solve the 
problem. I put this copy in linux/linux-davinci. I believe it has been 
sent upstream ...

Philip

diff --git a/arch/arm/kernel/vmlinux.lds.S b/arch/arm/kernel/vmlinux.lds.S
index 5ff5406..538fcb5 100644
--- a/arch/arm/kernel/vmlinux.lds.S
+++ b/arch/arm/kernel/vmlinux.lds.S
@@ -94,6 +94,7 @@ SECTIONS
                         TEXT_TEXT
                         SCHED_TEXT
                         LOCK_TEXT
+                       *(.note.*)
  #ifdef CONFIG_MMU
                         *(.fixup)
  #endif

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2008-01-13 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 15:18 large uImage size Risto Pajula
2008-01-13 15:33 ` Philip Balister [this message]
2008-03-14 22:12   ` Tom Rini
2008-01-13 15:35 ` Koen Kooi

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=478A2F3A.4090402@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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.