From: Peter Rosin <peda@axentia.se>
To: Sascha Hauer <s.hauer@pengutronix.de>, Ahmad Fatoum <ahmad@a3f.at>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: at91 sama5d3 "regressions"
Date: Sun, 19 Sep 2021 08:32:14 +0200 [thread overview]
Message-ID: <237cc091-69e4-c49a-9c7b-eb195515da63@axentia.se> (raw)
In-Reply-To: <bf4bc5ce-8206-ee40-f36c-1e5dff759b6e@axentia.se>
On 2021-09-18 01:57, Peter Rosin wrote:
> On 2021-09-18 00:37, Peter Rosin wrote:
>> Hi!
>>
>> I have old boards that I'm trying to get up to current
>> revisions of various pieces of software, and I'm running
>> into a couple of problems with barebox. After bisecting
>> and sorting though git history for a couple of days,
>> these are my findings...
>
> I meant to mention that I'm using this extra patch for my board.
>
> As you can see, it's been a couple of years, and it is not at
> all unlikely that the root cause is in these files, and that
> there has been changes in the other parts of the sama5d3 code
> that I need to pick up.
>
> I will dig into updating these files, and check if that help.
Ok, it turns out I don't need to do that update, because the
only thing that's actually used from the extra patch are the
tse850_defconfig file and the environment. But since the
tse850_defconfig file fails to set CONFIG_MACH_TSE850, the
actual code in the extra patch is not used (not even compiled).
Instead, the board code for sama5d3x is what I have been using
all along. Big blush about that, and sorry for the confusion!
However, the above also means that the quotes around the
"regressions" word in the subject can be removed. The problems
are squarely in the upstream code base, and I do need fixes
for region overlap, eXecute Never and RO_DATA_SECTION.
I have this hunch that the region overlap is what triggers
the other problems, but that's a pretty wild guess...
Cheers,
Peter
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-09-19 6:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 22:37 Peter Rosin
2021-09-17 22:39 ` [PATCH 1/4] common.h: reintroduce region_overlap() as, old_region_overlap() Peter Rosin
2021-09-17 22:39 ` [PATCH 2/4] ARM: copy data if there is a region overlap Peter Rosin
2021-09-17 22:40 ` [PATCH 3/4] Revert "ARM: mmu: use client domain permissions to support ARMv7 eXecute Never" Peter Rosin
2021-09-19 7:06 ` Rouven Czerwinski
2021-09-19 7:50 ` Peter Rosin
2021-09-19 20:33 ` Peter Rosin
2021-09-20 9:14 ` Ahmad Fatoum
2021-09-20 10:22 ` Peter Rosin
2021-09-17 22:41 ` [PATCH 4/4] lds: the RO_DATA_SECTION macro does not work on my SAMA5D3 board Peter Rosin
2021-09-17 23:57 ` at91 sama5d3 "regressions" Peter Rosin
2021-09-19 6:32 ` Peter Rosin [this message]
2021-09-22 7:06 ` Ahmad Fatoum
2021-09-22 7:41 ` Peter Rosin
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=237cc091-69e4-c49a-9c7b-eb195515da63@axentia.se \
--to=peda@axentia.se \
--cc=ahmad@a3f.at \
--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