mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: David Picard <david.picard@clermont.in2p3.fr>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [PATCH v2 2/2] ARM: setup_c: avoid clearing BSS twice
Date: Wed, 18 Mar 2026 15:12:23 +0100	[thread overview]
Message-ID: <121dc773-a7f4-4d8d-851f-0ff10dc3c8c8@clermont.in2p3.fr> (raw)
In-Reply-To: <2b87f519-866d-4db2-925f-8a828a4f450b@clermont.in2p3.fr>

Did it help? I can make more tests.

David

Le 18/03/2026 à 11:06, David Picard a écrit :
> https://paste.debian.net/hidden/5de2d5d1
>
> Le 18/03/2026 à 09:00, Sascha Hauer a écrit :
>> Hi David,
>>
>> On Wed, Mar 18, 2026 at 08:49:02AM +0100, David Picard wrote:
>>> Hi,
>>>
>>> The boot log with CONFIG_DEBUG_LL enabled for 1st and 2nd stage:
>>> https://paste.debian.net/hidden/d82f6a59
>> This starts with:
>>
>>> lowlevel init done
>>> SDRAM setup...
>>> SDRAM calibration...
>>> done
>>> Switch to console [cs0]
>>>
>>>
>>> barebox 2026.03.0 #1 Tue Mar 17 14:17:44 CET 2026
>> The binary has the same timestamp as the one you posted yesterday and it
>> doesn't have my patch applied, otherwise it should print the 8 hex
>> numbers followed by ABC, just like the 2nd stage shows.
>>
>> Sascha
>>
>
>




  reply	other threads:[~2026-03-18 14:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  7:53 [PATCH v2 0/2] ARM: Avoid to clear bss multiple times Sascha Hauer
2026-03-04  7:53 ` [PATCH v2 1/2] ARM: setupc_32: remove relocation code from setup_c Sascha Hauer
2026-03-04  9:02   ` Ahmad Fatoum
2026-03-11 14:41   ` Ahmad Fatoum
2026-03-11 19:08     ` Sascha Hauer
2026-03-04  7:53 ` [PATCH v2 2/2] ARM: setup_c: avoid clearing BSS twice Sascha Hauer
2026-03-04  9:05   ` Ahmad Fatoum
2026-03-10 10:44     ` Sascha Hauer
2026-03-16 13:21       ` David Picard
2026-03-17  9:06         ` Sascha Hauer
2026-03-17  9:50           ` David Picard
2026-03-17 12:43           ` David Picard
2026-03-17 15:56             ` Ahmad Fatoum
2026-03-17 16:03               ` David Picard
2026-03-17 16:11                 ` Ahmad Fatoum
2026-03-18  7:49                   ` David Picard
2026-03-18  8:00                     ` Sascha Hauer
2026-03-18 10:06                       ` David Picard
2026-03-18 14:12                         ` David Picard [this message]
2026-03-18 14:55                           ` Sascha Hauer
2026-03-18 15:43                             ` David Picard
2026-03-23 13:22                             ` David Picard
2026-03-10 10:42 ` [PATCH v2 0/2] ARM: Avoid to clear bss multiple times Sascha Hauer
2026-03-17 10:21 ` Sascha Hauer

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=121dc773-a7f4-4d8d-851f-0ff10dc3c8c8@clermont.in2p3.fr \
    --to=david.picard@clermont.in2p3.fr \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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