mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: ore@pengutronix.de
Subject: [PATCH 0/4] ARM: rpi: enable single entry point for all
Date: Mon, 25 Apr 2022 08:28:45 +0200	[thread overview]
Message-ID: <20220425062849.17954-1-a.fatoum@pengutronix.de> (raw)

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.

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


             reply	other threads:[~2022-04-25  6:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25  6:28 Ahmad Fatoum [this message]
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 ` [PATCH 0/4] ARM: rpi: enable single entry point for all 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=20220425062849.17954-1-a.fatoum@pengutronix.de \
    --to=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