unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
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, 14 May 2018 10:34:20 +0200	[thread overview]
Message-ID: <87in7qbppv.fsf@gnu.org> (raw)
In-Reply-To: <20180513125925.66a91367@scratchpost.org> (Danny Milosavljevic's message of "Sun, 13 May 2018 13:03:43 +0200")

Hello Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

>>   (define-record-type <board>
>>     (board name triplet installer)
>>     …)
>> 
>> Thoughts?
>
> The idea of make-u-boot-bootloader (and os-with-u-boot) was that it would free
> us from having to play whack-a-mole regarding u-boot (except for the
> installation methods of which there are much fewer than boards or chip models)
> and also free the user from having to know anything but the board name.
>
> With your idea it would mean that we'd have to carry a huge list of <board>s,
> defining the board and architecture and installer, right? (or I guess the
> user would have to create it on-the-fly)
>
> That's exactly what I was trying to avoid :)

Oh I see, especially the 1.2K boards vs. 86 SoCs!

Then perhaps “board” is not the right abstraction; maybe <soc> would
make more sense?

Either way, my point was that it would be nice to have some abstraction
to clearly specify things, and then use that as an input to construct
both the U-Boot package and its configuration.

Or do you think enumerating the SoCs would still be too painful?  In
that case, some auto-guessing might be the right choice, but in general,
I think it should be a last resort.  :-)

Thanks,
Ludo’.

  parent reply	other threads:[~2018-05-14  8:35 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 [this message]
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
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=87in7qbppv.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).