From: Peter Rosin <peda@axentia.se>
To: Rouven Czerwinski <r.czerwinski@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Ahmad Fatoum <ahmad@a3f.at>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 3/4] Revert "ARM: mmu: use client domain permissions to support ARMv7 eXecute Never"
Date: Sun, 19 Sep 2021 22:33:07 +0200 [thread overview]
Message-ID: <148368af-c744-3cde-1a5e-f895c6e57784@axentia.se> (raw)
In-Reply-To: <02b09328-e300-f36e-4cc4-daa7afb47ad5@axentia.se>
On 2021-09-19 09:50, Peter Rosin wrote:
> On 2021-09-19 09:06, Rouven Czerwinski wrote:
>> processors. Are you calling into SAMA5D3 ROM code somewhere? If so an
>
> *I* am not calling anything. Maybe the board code for sama5d3xek is,
> but I have no idea as it's not "my" code. How can I figure out if it
> does?
I did some digging and I think calling into any ROM can be ruled out
in this case. The only ROM that I can find in the sama5d3x datasheet
is this one:
- One 160 Kbyte Internal ROM Single-cycle Access at System Speed,
Embedded Boot Loader: Boot on 8-bit NAND Flash, SDCard, eMMC,
serial DataFlash, selectable Order
AFAICT, the internal ROM only contains the first level boot loader,
so the ROM is presumably never used after that stage. That said,
I'm by no means an expert on the internal details of the sama5d3x...
That, and there's no external ROM on the address bus.
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 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 22:37 at91 sama5d3 "regressions" 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 [this message]
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
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=148368af-c744-3cde-1a5e-f895c6e57784@axentia.se \
--to=peda@axentia.se \
--cc=ahmad@a3f.at \
--cc=barebox@lists.infradead.org \
--cc=r.czerwinski@pengutronix.de \
--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