From: Urja Rannikko <urjaman@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/4] Making veyrons boot, 2020 edition
Date: Wed, 13 May 2020 19:15:19 +0000 [thread overview]
Message-ID: <20200513191523.3141-1-urjaman@gmail.com> (raw)
Hi,
This is a series to make veyrons (tested on a veyron speedy),
boot atleast to the u-boot prompt, the first 3 patches are necessary
and the 4th one kinda just managed to catch this patch train ;)
PS. Thanks to swiftgeek on IRC for some bisecting & testing,
thus getting me curious enough to investigate these myself.
Urja Rannikko (4):
rockchip: spl: veyron speedy boots from SPI
rockchip: veyron: move board_early_init_f to _r (after reloc)
rockchip: spl-boot-order: do not attempt to access fdt if OF_PLATDATA
defconfig: veyron: no need for CONFIG_SPL_PINCTRL_FULL
arch/arm/mach-rockchip/spl-boot-order.c | 6 ++++++
arch/arm/mach-rockchip/spl.c | 3 ++-
board/google/veyron/veyron.c | 2 +-
configs/chromebit_mickey_defconfig | 4 ++--
configs/chromebook_jerry_defconfig | 5 ++---
configs/chromebook_minnie_defconfig | 4 ++--
configs/chromebook_speedy_defconfig | 3 ++-
7 files changed, 17 insertions(+), 10 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-13 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 19:15 Urja Rannikko [this message]
2020-05-13 19:15 ` [PATCH 1/4] rockchip: spl: veyron speedy boots from SPI Urja Rannikko
2020-05-15 1:57 ` Kever Yang
2020-05-13 19:15 ` [PATCH 2/4] rockchip: veyron: move board_early_init_f to _r (after reloc) Urja Rannikko
2020-05-15 1:57 ` Kever Yang
2020-05-13 19:15 ` [PATCH 3/4] rockchip: spl-boot-order: do not attempt to access fdt if OF_PLATDATA Urja Rannikko
2020-05-15 1:57 ` Kever Yang
2020-05-13 19:15 ` [PATCH 4/4] defconfig: veyron: no need for CONFIG_SPL_PINCTRL_FULL Urja Rannikko
2020-05-15 1:58 ` Kever Yang
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=20200513191523.3141-1-urjaman@gmail.com \
--to=urjaman@gmail.com \
--cc=u-boot@lists.denx.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