From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/5] riscv: sifive/fu540: Booting from SPI
Date: Mon, 20 Apr 2020 19:35:09 +0530 [thread overview]
Message-ID: <20200420140514.25847-1-jagan@amarulasolutions.com> (raw)
This series support Boot from SPI on SiFive FU540
HiFive Unleashed board.
SPI uses a separate defconfig and it is possible to reuse
existing one, but it requires runtime detection of boot
mode via MSEL.
Any help? let me know.
Series depends on [1] and [2].
[1] https://patchwork.ozlabs.org/cover/1263480/
[2] https://patchwork.ozlabs.org/project/uboot/list/?series=169649
Any inputs?
Jagan.
Jagan Teki (5):
sifive: fu540: Add Booting from SPI
env: Enable SPI flash env for SiFive FU540
sifive: fu540: Mark the default env as SPI flash
sifive: fu540: Add boot flash script offset, size
sifive: fu540: Enable SF distro bootcmd
.../dts/hifive-unleashed-a00-u-boot.dtsi | 12 ++++++
board/sifive/fu540/Kconfig | 1 +
board/sifive/fu540/fu540.c | 3 ++
configs/sifive_fu540_spi_defconfig | 26 +++++++++++
doc/board/sifive/fu540.rst | 43 +++++++++++++++++++
env/Kconfig | 3 ++
include/configs/sifive-fu540.h | 7 ++-
7 files changed, 94 insertions(+), 1 deletion(-)
create mode 100644 configs/sifive_fu540_spi_defconfig
--
2.17.1
next reply other threads:[~2020-04-20 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 14:05 Jagan Teki [this message]
2020-04-20 14:05 ` [PATCH 1/5] sifive: fu540: Add Booting from SPI Jagan Teki
2020-04-20 14:24 ` Bin Meng
2020-04-20 14:28 ` Jagan Teki
2020-04-20 14:05 ` [PATCH 2/5] env: Enable SPI flash env for SiFive FU540 Jagan Teki
2020-04-20 14:35 ` Bin Meng
2020-04-20 14:05 ` [PATCH 3/5] sifive: fu540: Mark the default env as SPI flash Jagan Teki
2020-04-20 14:36 ` Bin Meng
2020-04-20 14:05 ` [PATCH 4/5] sifive: fu540: Add boot flash script offset, size Jagan Teki
2020-04-20 14:05 ` [PATCH 5/5] sifive: fu540: Enable SF distro bootcmd Jagan Teki
2020-04-20 14:46 ` [PATCH 0/5] riscv: sifive/fu540: Booting from SPI Bin Meng
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=20200420140514.25847-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.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