From: Josua Mayer <josua@solid-run.com>
To: Dennis Gilmore <dgilmore@redhat.com>, Tom Rini <trini@konsulko.com>
Cc: Stefan Roese <sr@denx.de>,
u-boot@lists.denx.de, Josua Mayer <josua@solid-run.com>
Subject: [PATCH v2 3/3] board: helios-4: add config fragment for spi booting
Date: Fri, 02 Feb 2024 16:13:34 +0100 [thread overview]
Message-ID: <20240202-helios4-spi-v2-3-df085461d894@solid-run.com> (raw)
In-Reply-To: <20240202-helios4-spi-v2-0-df085461d894@solid-run.com>
Add a config fragment with required differences for booting from spi
flash instead of sd-card (default).
Settings for environment location are based on vendor u-boot:
https://github.com/kobol-io/u-boot/blob/helios4/include/configs/helios4.h#L59
The fragment can be applied on top of helios4_defconfig by make:
make helios4_defconfig spiboot.config
Signed-off-by: Josua Mayer <josua@solid-run.com>
---
board/kobol/helios4/spiboot.config | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/board/kobol/helios4/spiboot.config b/board/kobol/helios4/spiboot.config
new file mode 100644
index 0000000000..5ffb7d2e3b
--- /dev/null
+++ b/board/kobol/helios4/spiboot.config
@@ -0,0 +1,4 @@
+CONFIG_MVEBU_SPL_BOOT_DEVICE_SPI=y
+# CONFIG_MVEBU_SPL_BOOT_DEVICE_MMC is not set
+CONFIG_ENV_OFFSET=0x100000
+CONFIG_ENV_SECT_SIZE=0x10000
--
2.35.3
next prev parent reply other threads:[~2024-02-02 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 15:13 [PATCH v2 0/3] arm: mvebu: helios-4: add config fragment for spi booting et al Josua Mayer
2024-02-02 15:13 ` [PATCH v2 1/3] arm: dts: armada-38x-solidrun-microsom: configure i2c0 bus Josua Mayer
2024-03-05 10:32 ` Stefan Roese
2024-02-02 15:13 ` [PATCH v2 2/3] arm: mvebu: helios4_defconfig: enable setexpr command Josua Mayer
2024-02-12 20:40 ` Dennis Gilmore
2024-02-13 13:07 ` Josua Mayer
2024-03-05 10:32 ` Stefan Roese
2024-02-02 15:13 ` Josua Mayer [this message]
2024-02-02 16:06 ` [PATCH v2 3/3] board: helios-4: add config fragment for spi booting Tom Rini
2024-03-05 10:32 ` Stefan Roese
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=20240202-helios4-spi-v2-3-df085461d894@solid-run.com \
--to=josua@solid-run.com \
--cc=dgilmore@redhat.com \
--cc=sr@denx.de \
--cc=trini@konsulko.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