From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 31416@debbugs.gnu.org
Subject: [bug#31416] [PATCH 3/4] bootloader: Add make-u-boot-bootloader.
Date: Mon, 18 Jun 2018 10:25:00 +0200 [thread overview]
Message-ID: <874li0y00z.fsf@gnu.org> (raw)
In-Reply-To: <20180617234138.725002ef@scratchpost.org> (Danny Milosavljevic's message of "Sun, 17 Jun 2018 23:41:38 +0200")
Hi Danny,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Sun, 17 Jun 2018 22:33:05 +0200
> ludo@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’.
next prev parent reply other threads:[~2018-06-18 8:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 14:35 [bug#31416] [PATCH 0/4] Generalize bootloader installer selection Danny Milosavljevic
2018-05-11 14:36 ` [bug#31416] [PATCH 1/4] system: Add os-with-u-boot Danny Milosavljevic
2018-05-11 14:36 ` [bug#31416] [PATCH 2/4] bootloader: install-u-boot: Automatically select the correct installer Danny Milosavljevic
2018-05-13 9:31 ` Ludovic Courtès
2018-05-13 10:43 ` Danny Milosavljevic
2018-05-11 14:36 ` [bug#31416] [PATCH 3/4] bootloader: Add make-u-boot-bootloader Danny Milosavljevic
2018-05-13 9:36 ` Ludovic Courtès
2018-05-13 11:03 ` Danny Milosavljevic
2018-05-13 11:15 ` Danny Milosavljevic
2018-05-14 8:31 ` Ludovic Courtès
2018-05-13 13:46 ` Danny Milosavljevic
2018-05-14 8:34 ` Ludovic Courtès
2018-05-14 16:29 ` Danny Milosavljevic
2018-06-15 7:12 ` Ludovic Courtès
2018-06-17 0:28 ` Danny Milosavljevic
2018-06-17 12:35 ` Danny Milosavljevic
2018-06-17 20:33 ` Ludovic Courtès
2018-06-17 21:41 ` Danny Milosavljevic
2018-06-18 8:25 ` Ludovic Courtès [this message]
2018-05-11 14:36 ` [bug#31416] [PATCH 4/4] bootloader: Simplify bootloader installer selection Danny Milosavljevic
2018-05-13 9:24 ` [bug#31416] [PATCH 1/4] system: Add os-with-u-boot Ludovic Courtès
2018-05-13 12:09 ` Jelle Licht
2023-07-21 16:53 ` [bug#31416] [PATCH 0/4] Generalize bootloader installer selection Maxim Cournoyer
2023-09-01 18:47 ` bug#31416: " Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874li0y00z.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31416@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).