From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] BSS footprint of FAT very high - SPL issues
Date: Fri, 11 Feb 2011 09:15:59 +0100 [thread overview]
Message-ID: <4D54F03F.6070308@free.fr> (raw)
In-Reply-To: <4D54DDD7.7080507@ti.com>
Le 11/02/2011 07:57, Aneesh V a ?crit :
>> As you point out, using __u_boot_cmd would cause as much of a concern as
>> the current use of __bss_start, so I see no improvement there.
>>
>> Please define a label in the linker file. If you haven't got time to
>> port the change to other linkers, don't ; the BSS issue is, for now,
>> specific to your case.
>
> I thought it rather unlikely that the position of __u_boot_cmd will
> change in future. But I agree with you. Better do it cleanly once and
> for all. Changing the linker scripts for all cpus should not be a big
> deal. But I will not be able to test any of them except armv7/omap4
>
> One patch will do, right?
Yes.
> Also, any thoughts on the name for the new label.
> _end_of_relocated_image is all I can think of?
Current practice has "_end" appended to whatever the labels delimit --
same as for "_start".
Besides, the "relocated" part would be inexact; what matters here is the
loading, or copying, of the image, not its relocation (and actually BSS
is kind-of-relocated, as references to BSS from text or data may be the
target of a relocation record).
So I would suggest "__image_load_end" or "__image_copy_end".
>>> Best regards,
>>> Aneesh
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-02-11 8:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 5:23 [U-Boot] BSS footprint of FAT very high - SPL issues Aneesh V
2011-02-01 6:52 ` Bedia, Vaibhav
2011-02-01 7:58 ` Wolfgang Denk
2011-02-01 8:26 ` Aneesh V
2011-02-01 8:35 ` Bedia, Vaibhav
2011-02-01 10:05 ` Wolfgang Denk
2011-02-01 10:18 ` Bedia, Vaibhav
2011-02-01 10:48 ` Albert ARIBAUD
2011-02-01 12:43 ` Bedia, Vaibhav
2011-02-01 13:27 ` Wolfgang Denk
2011-02-01 10:53 ` Albert ARIBAUD
2011-02-11 21:16 ` Ulf Samuelsson
2011-02-11 22:15 ` Wolfgang Denk
2011-09-13 21:40 ` Ulf Samuelsson
2011-09-28 20:28 ` Wolfgang Denk
2011-02-12 6:13 ` Aneesh V
2011-02-01 7:04 ` Albert ARIBAUD
2011-02-01 7:11 ` Albert ARIBAUD
2011-02-01 8:00 ` Wolfgang Denk
2011-02-01 8:27 ` Aneesh V
2011-02-01 7:55 ` Wolfgang Denk
2011-02-01 8:18 ` Aneesh V
2011-02-01 8:48 ` Bedia, Vaibhav
2011-02-01 10:03 ` Wolfgang Denk
2011-02-02 13:17 ` Aneesh V
2011-02-02 13:37 ` Albert ARIBAUD
2011-02-02 14:01 ` Aneesh V
2011-02-02 15:14 ` Albert ARIBAUD
2011-02-03 10:38 ` Aneesh V
2011-02-05 6:58 ` Albert ARIBAUD
2011-02-11 6:28 ` Aneesh V
2011-02-11 6:39 ` Albert ARIBAUD
2011-02-11 6:57 ` Aneesh V
2011-02-11 8:15 ` Albert ARIBAUD [this message]
2011-02-11 8:27 ` Aneesh V
2011-02-02 21:01 ` Graeme Russ
2011-02-03 7:01 ` Aneesh V
2011-02-03 10:05 ` Graeme Russ
2011-02-03 6:49 ` sughosh ganu
2011-02-03 7:22 ` Aneesh V
2011-02-15 8:44 ` Mike Frysinger
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=4D54F03F.6070308@free.fr \
--to=albert.aribaud@free.fr \
--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