From: dgilmore at redhat.com <dgilmore@redhat.com>
To: u-boot@lists.denx.de
Subject: [PATCH 3/4] ARM: mvebu: ClearFog make sure that SATA and UART images are buildable
Date: Sun, 6 Dec 2020 19:36:02 -0600 [thread overview]
Message-ID: <20201207013603.330578-3-dgilmore@redhat.com> (raw)
In-Reply-To: <20201207013603.330578-1-dgilmore@redhat.com>
From: Dennis Gilmore <dennis@ausil.us>
SATA and UART ClearFog imaages are not buildable as ENV_SECT_SIZE is not defined
set values for both possible targets
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
---
board/solidrun/clearfog/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/board/solidrun/clearfog/Kconfig b/board/solidrun/clearfog/Kconfig
index e8c3f53d84..cf95258090 100644
--- a/board/solidrun/clearfog/Kconfig
+++ b/board/solidrun/clearfog/Kconfig
@@ -50,9 +50,9 @@ config ENV_OFFSET
config ENV_SECT_SIZE
hex "Environment Sector-Size"
# Use SPI flash erase block size of 4 KiB
- default 0x1000 if MVEBU_SPL_BOOT_DEVICE_SPI
+ default 0x1000 if MVEBU_SPL_BOOT_DEVICE_SPI || MVEBU_SPL_BOOT_DEVICE_SATA
# Use optimistic 64 KiB erase block, will vary between actual media
- default 0x10000 if MVEBU_SPL_BOOT_DEVICE_MMC
+ default 0x10000 if MVEBU_SPL_BOOT_DEVICE_MMC || MVEBU_SPL_BOOT_DEVICE_UART
config SYS_SPI_U_BOOT_OFFS
hex "address of u-boot payload in SPI flash"
--
2.28.0
next prev parent reply other threads:[~2020-12-07 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 1:36 [PATCH 1/4] ARM: mvebu: helios4 adjust env sizes to enable SPI to work dgilmore at redhat.com
2020-12-07 1:36 ` [PATCH 2/4] ARM: mvebu: helios4 dts changes to enable SPI dgilmore at redhat.com
2020-12-07 5:36 ` Baruch Siach
2020-12-07 1:36 ` dgilmore at redhat.com [this message]
2020-12-07 1:36 ` [PATCH 4/4] ARM: mvebu: fixup building a SPI image for db-mv784mp-gp dgilmore at redhat.com
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=20201207013603.330578-3-dgilmore@redhat.com \
--to=dgilmore@redhat.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