GNU bug report logs - #31416
[PATCH 0/4] Generalize bootloader installer selection.

Previous Next

Full log

View this message in rfc822 format

From: ludo <at> gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 31416 <at> debbugs.gnu.org
Subject: [bug#31416] [PATCH 3/4] bootloader: Add make-u-boot-bootloader.
Date: Mon, 18 Jun 2018 10:25:00 +0200

Hi Danny,

Danny Milosavljevic <dannym <at> scratchpost.org> skribis:

> On Sun, 17 Jun 2018 22:33:05 +0200
> ludo <at> gnu.org (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.

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.