From: Jesse Gibbons <jgibbons2357@gmail.com>
To: 37286@debbugs.gnu.org
Subject: bug#37286: Make a faster method to list supported boards.
Date: Mon, 02 Sep 2019 12:52:49 -0600 [thread overview]
Message-ID: <5f87e4c297b8e4fca0f9ceb0729f2176dec947bb.camel@gmail.com> (raw)
There should be a faster way to list the supported boards with custom
versions of U-Boot.
From manual:
Many ARM boards require a specific variant of the U-Boot
(https://www.denx.de/wiki/U-Boot/) bootloader.
If you build a disk image and the bootloader is not available
otherwise (on another boot drive etc), it’s advisable to build an image
that includes the bootloader, specifically:
guix system disk-image --system=armhf-linux -e '((@ (gnu system
install) os-with-u-boot) (@ (gnu system install) installation-os) "A20-
OLinuXino-Lime2")'
‘A20-OLinuXino-Lime2’ is the name of the board. If you specify an
invalid board, a list of possible boards will be printed.
I think an example of an invalid board is "dne-board", which (last I
checked) does not exist and probably never will exist. If I run the
following command:
guix system disk-image --system=armhf-linux -e '((@ (gnu system
install) os-with-u-boot) (@ (gnu system install) installation-os) "dne-
board")'
guix tries to build an entire system. It doesn't look like it checks if
"dne-board" is a valid board until it is building the image. It takes
hours to cross-compile the kernel, and even longer if the kernel needs
to be deblobbed. I have not yet been able to cross-compile any system
using this method.
next reply other threads:[~2019-09-02 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 18:52 Jesse Gibbons [this message]
2019-09-02 20:49 ` bug#37286: Make a faster method to list supported boards Danny Milosavljevic
2019-09-03 2:07 ` Jesse Gibbons
2019-09-03 3:28 ` Caleb Ristvedt
2019-09-03 8:57 ` Danny Milosavljevic
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=5f87e4c297b8e4fca0f9ceb0729f2176dec947bb.camel@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=37286@debbugs.gnu.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).