From: Eugen.Hristev at microchip.com <Eugen.Hristev@microchip.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] ARM: at91: Enable SPL_SEPARATE_BSS by default
Date: Fri, 5 Jun 2020 08:35:04 +0000 [thread overview]
Message-ID: <54139d6f-e1c4-cc2e-20fd-c4bb18cba151@microchip.com> (raw)
In-Reply-To: <877dwm9ckt.fsf@FE-laptop>
On 05.06.2020 10:49, Gregory CLEMENT wrote:
> Hi Eugen,
>
>> On 10.01.2020 08:32, Stefan Roese wrote:
>>
>>> On 09.01.20 17:30, Gregory CLEMENT wrote:
>>>> According to the linker script for both armv7 and arm926ejs based SoC,
>>>> BSS section was all the time separated for SPL but this symbol was
>>>> only enabled on some boards. However, it is necessary to have it
>>>> enabled for OF_SEPARATE configuration where DTB is appended to u-boot
>>>> with DTB.
>>>>
>>>> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
>>>> ---
>>>> arch/arm/Kconfig | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
>>>> index f9dab073ea..e558024652 100644
>>>> --- a/arch/arm/Kconfig
>>>> +++ b/arch/arm/Kconfig
>>>> @@ -492,6 +492,7 @@ choice
>>>> config ARCH_AT91
>>>> bool "Atmel AT91"
>>>> select SPL_BOARD_INIT if SPL && !TARGET_SMARTWEB
>>>> + select SPL_SEPARATE_BSS if SPL
>>>>
>>>> config TARGET_EDB93XX
>>>> bool "Support edb93xx"
>>>>
>>>
>>> Reviewed-by: Stefan Roese <sr@denx.de>
>>>
>>> Thanks,
>>> Stefan
>>>
>>
>> Hi,
>>
>> With these changes, for all the A5 boards , SEPARATE_BSS was already
>> enabled, but for the rest of the platforms, it was not.
>> As I see from the linker script, the BSS area is configured into DRAM area.
>> Is there any chance that we have accesses to this section before the
>> DRAM is initialized on these platforms ? Could cause the boards to
>> hang.
>
> It is explicitly stated that it BSS is not available before setting up
> the DRAM: it is forbidden to use global/static variables. So it should
> be OK.
>
Thanks for the clarification. Will queue the patches for next merge window.
Eugen
> Gregory
>
>>
>> Eugen
>
> --
> Gregory Clement, Bootlin
> Embedded Linux and Kernel engineering
> http://bootlin.com
>
next prev parent reply other threads:[~2020-06-05 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 16:30 [PATCH 1/2] ARM: at91: Enable SPL_SEPARATE_BSS by default Gregory CLEMENT
2020-01-09 16:30 ` [PATCH 2/2] configs: atmel: cleanup CONFIG_SPL_SEPARATE_BSS Gregory CLEMENT
2020-01-10 6:32 ` Stefan Roese
2020-01-10 6:32 ` [PATCH 1/2] ARM: at91: Enable SPL_SEPARATE_BSS by default Stefan Roese
2020-01-23 8:12 ` Eugen.Hristev at microchip.com
2020-06-05 7:49 ` Gregory CLEMENT
2020-06-05 8:35 ` Eugen.Hristev at microchip.com [this message]
2020-06-05 8:45 ` Gregory CLEMENT
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=54139d6f-e1c4-cc2e-20fd-c4bb18cba151@microchip.com \
--to=eugen.hristev@microchip.com \
--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