From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] size of mips U-boot image
Date: Wed, 29 Sep 2004 21:42:28 +0200 [thread overview]
Message-ID: <20040929194233.2FAA3C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 29 Sep 2004 11:50:16 PDT." <200409291150.16422.msundius@sundius.com>
In message <200409291150.16422.msundius@sundius.com> you wrote:
> Could anyone give me an approximate size of the U-boot
> image for a mips system when configured with a reasonable configuration:
> i.e. with jffs2 support and support for bootp/tftp?
purple:
text data bss dec hex filename
154984 6016 16828 177828 2b6a4 u-boot
incaip:
text data bss dec hex filename
161288 6312 18256 185856 2d600 u-boot
[both with full networking, but without JFFS2 support]
> I realize the size can vary depending upon what stuff you pack in there,
> but I'm just looking for a general size.. since if its in the ball park I can
> do the tailoring to make it fit in our FLASH... If not, I'll have to do more
> thinking :]
So far, all images I've seen fit easily in 256 kB. You will have to
omit a lot of "nice to have" stuff to squeeze U-Boot into 128 kB.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
In C we had to code our own bugs, in C++ we can inherit them.
next prev parent reply other threads:[~2004-09-29 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CBqxq-0002xy-46@sc8-sf-list1.sourceforge.net>
2004-09-29 18:50 ` [U-Boot-Users] size of mips U-boot image C Michael Sundius
2004-09-29 19:42 ` Wolfgang Denk [this message]
2004-10-08 18:26 ` [U-Boot-Users] linking u-boot for mips little endian w/ hardhat tools C Michael Sundius
2004-10-08 18:54 ` Charles Eidsness
2004-10-08 20:28 ` Wolfgang Denk
2004-10-09 1:07 ` Masami Komiya
2004-10-11 22:53 ` Wolfgang Denk
2004-10-12 0:06 ` Masami Komiya
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=20040929194233.2FAA3C1430@atlas.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox