[RFC PATCH 0/3] Minimal platform configuration

Simon Glass sjg at google.com
Wed Jul 12 16:00:29 CEST 2023

Hi Jason,

On Tue, 11 Jul 2023 at 16:28, Jason Kacines <j-kacines at ti.com> wrote:
> When someone attempts to bring up a custom board using TI SoCs (am62x in
> this case), it often takes several days for someone to reduce the
> current configuration from the TI EVM/SK boards to a configuration that
> works for their board.
> The goal of these changes is to allow for a minimal boot configuration
> to exist within UBoot that someone can access directly in order to
> test their boards for a sign of life before beginning development. This
> is all done with the hope to increase ease of use and reduce the
> upbringing process from several days to a few hours.
> With the use of fragments, the base defconfigs reside in configs/ and
> the config fragments reside in board/../
> There is still quite a lot of board specific code inside board_init_f()
> that will need attention later, however this series begins the process
> of splitting the am62x's configs into a separate generic defconfig
> everyone can use for new board wakeups with individual board/ti/*.config
> fragments for each board varient.

How about setting up some common defaults for your arch using Kconfig,
so that the board defconfigs are much smaller?

In general, boards in U-Boot have far too many individual settings.
Most of them should use a sensible default.

Going in the direction you have here just continues that tradition,
inventing what I feel is an unnecessary solution.


More information about the U-Boot mailing list