Hi Jesse,
On Mon, 02 Sep 2019 20:07:53 -0600
Jesse Gibbons wrote:
> On Mon, 2019-09-02 at 22:49 +0200, Danny Milosavljevic wrote:
> > Hi,
> >
> > On Mon, 02 Sep 2019 12:52:49 -0600
> > Jesse Gibbons wrote:
> >
> If the bootloader build fails, which appears necessary to generate the
> list,
> Where does guix get this list? Is it configured or automatically
> generated?
It's all the filenames suffixed with "_defconfig" in the "configs"
subdirectory of the u-boot source, minus the suffix.
- reepca
On Mon, 2019-09-02 at 22:49 +0200, Danny Milosavljevic wrote:
> Hi,
>
> On Mon, 02 Sep 2019 12:52:49 -0600
> Jesse Gibbons wrote:
>
> > 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
> > ho
Hi,
On Mon, 02 Sep 2019 12:52:49 -0600
Jesse Gibbons wrote:
> 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
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 bo