public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Josua Mayer <josua@solid-run.com>
Cc: Dennis Gilmore <dgilmore@redhat.com>, u-boot@lists.denx.de
Subject: Re: [PATCH 3/3] arm: mvebu: helios-4: add defconfig for spi booting
Date: Sat, 13 Jan 2024 12:22:36 -0500	[thread overview]
Message-ID: <20240113172236.GI1610741@bill-the-cat> (raw)
In-Reply-To: <20240113-helios4-spi-v1-3-2a5663a10e6a@solid-run.com>

[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]

On Sat, Jan 13, 2024 at 05:36:57PM +0100, Josua Mayer wrote:

> Add a new defconfig based on existing helios4_config file to support
> booting from spi flash.
> 
> Settings for environment location are based on vendor u-boot:
> https://github.com/kobol-io/u-boot/blob/helios4/include/configs/helios4.h#L59
> 
> A separate defconfig is required because the options are not
> intuitive from menuconfig, numeric values in particular.
> 
> Signed-off-by: Josua Mayer <josua@solid-run.com>
> ---
>  configs/helios4_spi_defconfig | 81 +++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 81 insertions(+)

So, a super new thing that might be of interest, but please try this
since I'd like to prove/disprove the use-case.  This could instead be:
configs/helios4_spi_defconfig:
#include "configs/helios4_defconfig"
... enable/disable options specific to the SPI boot use case ...

And so now both boards will otherwise be kept in-sync for general config
changes.  It could further be done as:
configs/helios4_spi_defconfig:
#include "configs/helios4_defconfig"
#include "board/kobol/helios4/spiboot.config"

And have board/kobol/helios4/spiboot.config contain the SPI-boot
specific options.  This path would allow for:
make helios4_defconfig spiboot.config
to be a valid alternative way of configuring a build for spiboot.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2024-01-13 17:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13 16:36 [PATCH 0/3] arm: mvebu: helios-4: add defconfig forspi booting et al Josua Mayer
2024-01-13 16:36 ` [PATCH 1/3] arm: dts: armada-38x-solidrun-microsom: configure i2c0 bus Josua Mayer
2024-01-13 16:36 ` [PATCH 2/3] arm: mvebu: helios4_defconfig: enable setexpr command Josua Mayer
2024-01-13 16:36 ` [PATCH 3/3] arm: mvebu: helios-4: add defconfig for spi booting Josua Mayer
2024-01-13 17:22   ` Tom Rini [this message]
2024-01-14  9:47     ` Josua Mayer
2024-01-14 14:37       ` Tom Rini
2024-02-02 15:08         ` Josua Mayer
2024-01-22 11:45     ` 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=20240113172236.GI1610741@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=dgilmore@redhat.com \
    --cc=josua@solid-run.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