From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Oleksij Rempel <linux@rempel-privat.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 11:21:56 +0100 [thread overview]
Message-ID: <bdfb5299-841a-1637-0226-f8bdfd994d76@pengutronix.de> (raw)
In-Reply-To: <98fca2ef-9c7b-0570-ef4d-11ff92b33fa4@rempel-privat.de>
Hello Oleksij,
On 11/19/19 10:41 AM, Oleksij Rempel wrote:
> Am 19.11.19 um 09:26 schrieb Ahmad Fatoum:
>> 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?
Not when I chainload a barebox PBL. In that case, __barebox_arm_head is the
start of SDRAM and when barebox reconfigures the vector table, it will be
some bytes after that.
The exceptions vectors before barebox configures them are probably
0x0 because the ROM code didn't change it.
Why are you asking?
Cheers
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-11-19 10:22 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
2019-11-19 10:21 ` Ahmad Fatoum [this message]
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=bdfb5299-841a-1637-0226-f8bdfd994d76@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=linux@rempel-privat.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