From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC/PATCH] Makefile: allow boards to check file size limits
Date: Wed, 20 Oct 2010 01:16:46 -0400 [thread overview]
Message-ID: <201010200116.47740.vapier@gentoo.org> (raw)
In-Reply-To: <AANLkTimcki1vN0Hy5tXixytNaWYQkrgKfO=i9wM4GTch@mail.gmail.com>
On Wednesday, October 20, 2010 00:38:08 Vaibhav Bedia wrote:
please do not top post
> The size of other sections like the bss section also need to be accounted
> for when doing a size check.
that really cannot be checked at compile time. it certainly cannot be done
easily or with a few lines of shell code.
> Insufficient space for bss when doing something like a MMC read which
> requires large buffers causes system hangs for no apparent reason.
that doesnt make much sense. bss is statically allocated. either it exists,
or it doesnt. if bss doesnt work, your system/build is fundamentally screwed.
either way, none of this is related to my patch.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20101020/19afb5c9/attachment.pgp
next prev parent reply other threads:[~2010-10-20 5:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 2:58 [U-Boot] [RFC/PATCH] Makefile: allow boards to check file size limits Mike Frysinger
2010-10-18 20:43 ` Wolfgang Denk
2010-10-19 4:17 ` Mike Frysinger
2010-10-19 5:24 ` Wolfgang Denk
2010-10-19 5:38 ` Mike Frysinger
2010-10-19 21:29 ` Wolfgang Denk
2010-10-20 4:38 ` Vaibhav Bedia
2010-10-20 5:16 ` Mike Frysinger [this message]
2010-10-20 6:56 ` Vaibhav Bedia
2010-10-20 7:19 ` Wolfgang Denk
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=201010200116.47740.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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