From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org, ore@pengutronix.de
Subject: Re: [PATCH 0/4] ARM: rpi: enable single entry point for all
Date: Mon, 25 Apr 2022 12:43:41 +0200 [thread overview]
Message-ID: <20220425104341.GK4012@pengutronix.de> (raw)
In-Reply-To: <20220425062849.17954-1-a.fatoum@pengutronix.de>
On Mon, Apr 25, 2022 at 08:28:45AM +0200, Ahmad Fatoum wrote:
> VideoCore can boot kernel directly and will pass appropriate DT
> according to kernel boot convention. If we do arm_cpu_lowlevel_init() in
> the ARM board-dt-2nd, we can have this generic image act as second stage
> on all Raspberry Pi variants.
I just chatted with Ahmad and we both agreed that we'll go into the
direction that we'll remove the individual images after a few releases
and fully go to using the board-dt-2nd image for rpi. We'll leave the
individual images here for now until we are sure the generic image
works.
Applied, thanks
Sascha
>
> Ahmad Fatoum (4):
> ARM: cpu: board-dt-2nd: call arm_cpu_lowlevel_init
> ARM: rpi: don't warn about lack of videocore fdt
> ARM: rpi: remove outdated comment after stack setup rework
> ARM: configs: rpi: add and document single barebox-dt-2nd bootloader
>
> Documentation/boards/bcm2835.rst | 6 ++++++
> arch/arm/boards/raspberry-pi/lowlevel.c | 1 -
> arch/arm/boards/raspberry-pi/rpi-common.c | 4 +---
> arch/arm/configs/rpi_defconfig | 1 +
> arch/arm/cpu/board-dt-2nd.c | 4 ++++
> 5 files changed, 12 insertions(+), 4 deletions(-)
>
> --
> 2.30.2
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
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
prev parent reply other threads:[~2022-04-25 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 6:28 Ahmad Fatoum
2022-04-25 6:28 ` [PATCH 1/4] ARM: cpu: board-dt-2nd: call arm_cpu_lowlevel_init Ahmad Fatoum
2022-04-25 6:28 ` [PATCH 2/4] ARM: rpi: don't warn about lack of videocore fdt Ahmad Fatoum
2022-04-25 6:28 ` [PATCH 3/4] ARM: rpi: remove outdated comment after stack setup rework Ahmad Fatoum
2022-04-25 6:28 ` [PATCH 4/4] ARM: configs: rpi: add and document single barebox-dt-2nd bootloader Ahmad Fatoum
2022-04-25 10:43 ` Sascha Hauer [this message]
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=20220425104341.GK4012@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ore@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