[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#31416] [PATCH 3/4] bootloader: Add make-u-boot-bootloader.

From: Ludovic Courtès
Subject: [bug#31416] [PATCH 3/4] bootloader: Add make-u-boot-bootloader.
Date: Mon, 18 Jun 2018 10:25:00 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Hi Danny,

Danny Milosavljevic <address@hidden> skribis:

> On Sun, 17 Jun 2018 22:33:05 +0200
> address@hidden (Ludovic Courtès) wrote:


>> IOW, we could definitely take Buildroot as an inspiration (it’s probably
>> one of the best tools in this area), but maybe not reuse the actual
>> files.
> The advantage if we reused the actual files is that we'd not have to maintain
> it so much ourselves.


> Next would be to find those in buildroot, extract the relevant information 
> from their genimage.cfg and unify them.
> But that's a little involved.  A path would be:
> (1) Extract possible SYS_SOC and SYS_VENDOR from all u-boot Kconfigs
> (2) Find out which u-boot defconfigs would lead to those u-boot Kconfigs
> (3) Find out which buildroot defconfigs would lead to those u-boot defconfigs
> (4) Find out which buildroot board directory is used by each buildroot 
> defconfig
> (5) Extract the genimage.cfg from each such buildroot board directory
> (6) Extract the u-boot installation specific parts from the genimage.cfg
> (7) Unify the set of "genimage.cfg" parts for this SOC and make sure they are 
> always the same

Sounds like a plan.

Though honestly, I think it’s fine if we have fewer configs available as
long as they’re known good.  It’s not a goal IMO to have as many
supported boards as Buildroot.

So I’d suggest defining the <soc> API and using it, taking inspiration
from those genimage.cfg files as needed.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]