large uImage size

large uImage size

[Risto Pajula]

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.

This has however changed in some point of OE development. If I use an old OE 
snapshot and build the crosscompiler with it the resulting kernel image even 
when building outside OE environment is normal. (Both however use gcc 4.1.2).

I have tried to figure what is different in the environment when building the 
kernel within OE and outside it but any of the environment variables and etc. 
have not solved the problem.

Does anybody know any changes in the OE which could cause this different 
behaviour in the gcc cross-compiler built with it?

Machine: at91sam9263-ek.
The kernel compilation ouside OE: 
make ARCH=arm 
CROSS_COMPILE=/PATH_TO_OE_BUILD_DIR/tmp/cross/bin/arm-angstrom-linux-gnueabi- 
uImage

I want to build the development kernel outside of openembedded framewok for 
various reasons but use OE crosscompiler. So any help or suggestions for 
figuring out why this happens would be appreciated.

BR.
Risto

Re: large uImage size

[Philip Balister]

[-- 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 --]

Re: large uImage size

[Tom Rini]

On Sun, Jan 13, 2008 at 10:33:14AM -0500, Philip Balister wrote:
> 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 ...

Old message, I know.  But, the upstream answer is a little different and
is:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1e621a8e3752367d4aae78a8ab00a18fb2793f34

-- 
Tom Rini

Re: large uImage size

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Risto Pajula schreef:
| 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.
|
| This has however changed in some point of OE development. If I use an
old OE
| snapshot and build the crosscompiler with it the resulting kernel
image even
| when building outside OE environment is normal. (Both however use gcc
4.1.2).
|
| I have tried to figure what is different in the environment when
building the
| kernel within OE and outside it but any of the environment variables
and etc.
| have not solved the problem.
|
| Does anybody know any changes in the OE which could cause this different
| behaviour in the gcc cross-compiler built with it?

http://www.openembedded.org/repo/org.openembedded.dev/packages/linux/linux-2.6.23/binutils-buildid-arm.patch

|
| Machine: at91sam9263-ek.
| The kernel compilation ouside OE:
| make ARCH=arm
|
CROSS_COMPILE=/PATH_TO_OE_BUILD_DIR/tmp/cross/bin/arm-angstrom-linux-gnueabi-

| uImage
|
| I want to build the development kernel outside of openembedded
framewok for
| various reasons

any valid reasons?


- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHii/YMkyGM64RGpERAnUCAJ9SiBslj6zIdKOC1v8FapxmyPNi+gCgqJDP
zLSyPC/dzhhoh3KULKcA/Hw=
=V0yR
-----END PGP SIGNATURE-----