mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
	barebox@lists.infradead.org,
	Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 6/8] ARM: Add generic device tree 2nd stage support
Date: Tue, 19 Nov 2019 10:41:55 +0100	[thread overview]
Message-ID: <98fca2ef-9c7b-0570-ef4d-11ff92b33fa4@rempel-privat.de> (raw)
In-Reply-To: <27e33ef9-bb89-dcd0-9829-6dd3036eeae9@pengutronix.de>


[-- Attachment #1.1.1: Type: text/plain, Size: 1286 bytes --]

Am 19.11.19 um 09:26 schrieb Ahmad Fatoum:
> Hello Sascha,
> 
> On 8/19/19 3:38 PM, Sascha Hauer wrote:
>> +void dt_2nd_aarch64(void *fdt)
>> +{
>> +	unsigned long image_start = (unsigned long)_text + global_variable_offset();
>> +
>> +	arm_setup_stack(image_start);
> 
> Shouldn't we rather place the stack somewhere beyond the end of the barebox image
> instead of assuming that we can access the memory before the start? 
> 
> I am asking because I am testing use of the generic ARM board as default
> second stage image for the multi-image AT91s. The board specific entry point
> generates only the PBL, which runs in SRAM to do DRAM setup and chainloads
> the generic dt barebox from MMC to start of SDRAM and then calls it along
> with the dtb.

Hm.. Is it possible that you can get an exception vector in the star of SDRAM?

> It works so far and I like that I now can have the same second stage barebox
> for all multi-image targets. (And one could even "falcon"-boot that way).
> What do you think?>
>> +ENTRY_FUNCTION(start_dt_2nd, r0, r1, r2)
>> +{
>> +	unsigned long image_start = (unsigned long)_text + global_variable_offset();
>> +
>> +	arm_setup_stack(image_start);
> 
> 
> Ditto.
> 
> Cheers
> Ahmad
> 


-- 
Regards,
Oleksij


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2019-11-19  9:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 13:38 [PATCH 0/8] Add support for a generic DT based 2nd stage ARM image Sascha Hauer
2019-08-19 13:38 ` [PATCH 1/8] dtc: Update update-dtc-source.sh from Linux Sascha Hauer
2019-08-19 13:48   ` Roland Hieber
2019-08-19 13:38 ` [PATCH 2/8] scripts/dtc: Update to upstream version v1.5.0 Sascha Hauer
2019-08-19 13:52   ` Roland Hieber
2019-08-19 13:56     ` Sascha Hauer
2019-08-19 14:09       ` Roland Hieber
2019-09-23 13:39         ` Ahmad Fatoum
2019-08-19 13:38 ` [PATCH 3/8] pbl: Implement strrchr Sascha Hauer
2019-08-19 13:38 ` [PATCH 4/8] Compile libfdt for barebox Sascha Hauer
2019-08-19 13:38 ` [PATCH 5/8] common: return "none" when board unset Sascha Hauer
2019-08-19 13:38 ` [PATCH 6/8] ARM: Add generic device tree 2nd stage support Sascha Hauer
2019-11-19  8:26   ` Ahmad Fatoum
2019-11-19  9:41     ` Oleksij Rempel [this message]
2019-11-19 10:21       ` Ahmad Fatoum
2019-11-25  7:47     ` Sascha Hauer
2019-08-19 13:38 ` [PATCH 7/8] ARM: i.MX: Do not hang() on unknown SoCs Sascha Hauer
2019-08-19 13:38 ` [PATCH 8/8] ARM: i.MX: When generic DT image is enabled do not hardcode SoC 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=98fca2ef-9c7b-0570-ef4d-11ff92b33fa4@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --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