From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@openembedded.org>,
angstrom-distro-devel@linuxtogo.org
Subject: Re: [Angstrom-devel] Tosa kernel bloat
Date: Fri, 28 Dec 2007 11:02:18 +0100 [thread overview]
Message-ID: <4774C9AA.8050705@student.utwente.nl> (raw)
In-Reply-To: <4774C182.20501@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Junqian Gordon Xu schreef:
> Tosa kernel is bloated with the recent patch and change to defconfig-tosa
>
> |`/home/gordon/oe/build/tmp/work/tosa-angstrom-linux-gnueabi/linux-rp-2.6.23-r14/linux-2.6.23'
> | Size is 1296464
> | FATAL: This kernel is too big for your PXA Zaurus and will destroy
> data if you flash it. Please reduce the size of the kernel by making
> more of it modular.
>
> Anybody else experience this? I guess kernel size below 1280000 is ok?
> I'm not sure where I should look to trim it down?
Is that also the case in the angstrom stable branch?
regards,
Koen
- --
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)
iD8DBQFHdMmqMkyGM64RGpERApOTAJwJS0aNs5EWEAfAzZDg/ysIcmbrjACfXYAg
twGk159NAGv4UuScqp1pid0=
=e/cH
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-12-28 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 9:27 Tosa kernel bloat Junqian Gordon Xu
2007-12-28 10:02 ` Koen Kooi [this message]
2007-12-28 13:04 ` [Angstrom-devel] " cyril Romain
2007-12-28 13:32 ` Marcin Juszkiewicz
2008-01-01 13:34 ` Junqian Gordon Xu
2007-12-28 11:08 ` Marcin Juszkiewicz
2007-12-31 20:10 ` Michael 'Mickey' Lauer
2007-12-31 23:18 ` Richard Purdie
2008-01-01 16:41 ` 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=4774C9AA.8050705@student.utwente.nl \
--to=k.kooi@student.utwente.nl \
--cc=angstrom-distro-devel@linuxtogo.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.