From: phodina via <help-guix@gnu.org>
To: help-guix <help-guix@gnu.org>
Subject: U-Boot for Raspberry Pi
Date: Sat, 30 Oct 2021 21:39:48 +0000 [thread overview]
Message-ID: <QxiawUX4Q1CKPU8Wk8t8CvzTPxrXfSaKx4w4PbDbbG1dZuZIWwfnIAxs4vzrfWo7beK05xg8La-pd-WDw47ZOpKYvDIsDEQwhH9jXLNIyxs=@protonmail.com> (raw)
Hi,
I'm trying to run Guix System on Raspberry Pi. In order to do that we need a way to boot it up.
There is the nonfree Broadcom bootloader, which does the job and it's used by many distributions.
However, there is also an open source alternative as U-Boot supports the BCM SoCs.
I had look at different u-boot definitions under gnu/packages/bootloaders.scm and gnu/bootloader.scm.
From my understanding the way how to define a new board is find the defconfig name in the configs directory in U-Boot.
Then use the make-u-boot-package with the config name and target triplet to define the package.
Unfortunately, the definitions below are not found by Guix if I run guix search -L. raspberry
If I inherit from the u-boot itself and specify the name, it's then in the list and I can build it.
But the I can't use the package for the bootloader record.
There must be something trivial I had overlooked.
Could you please guide me on the procedure for porting the u-boot to new board as a new Guix package?
--8<---------------cut here---------------start------------->8---
(define-module (raspberry-pi)
#:use-module (guix packages)
#:use-module (gnu packages bootloaders)
#:use-module (guix download)
#:use-module (guix git-download)
#:use-module (guix build-system gnu)
#:use-module ((guix licenses) #:prefix license:))
(define-public u-boot-raspberry-pi-2
(make-u-boot-package "rpi_2" "arm-linux-gnueabihf"))
(define-public u-boot-raspberry-pi-3
(make-u-boot-package "rpi_3" "aarch64-linux-gnu"))
(define-public u-boot-raspberry-pi-4
(make-u-boot-package "rpi_4" "aarch64-linux-gnu"))
next reply other threads:[~2021-10-30 21:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 21:39 phodina via [this message]
2021-10-30 22:05 ` U-Boot for Raspberry Pi Vagrant Cascadian
2021-10-31 6:47 ` phodina
-- strict thread matches above, loose matches on Subject: below --
2021-10-31 23:09 Stefan
2021-11-02 11:00 ` phodina
2021-11-02 13:24 ` Stefan
2022-02-16 15:55 ` Reza Alizadeh Majd
2022-02-18 23:12 ` Ricardo Wurmus
2022-02-21 11:08 ` Reza Alizadeh Majd
2022-02-21 11:14 ` Ricardo Wurmus
2022-02-22 7:36 ` Reza Alizadeh Majd
2022-02-22 8:30 ` Ricardo Wurmus
2022-02-22 9:05 ` Vincent Legoll
2022-02-22 9:07 ` Vincent Legoll
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='QxiawUX4Q1CKPU8Wk8t8CvzTPxrXfSaKx4w4PbDbbG1dZuZIWwfnIAxs4vzrfWo7beK05xg8La-pd-WDw47ZOpKYvDIsDEQwhH9jXLNIyxs=@protonmail.com' \
--to=help-guix@gnu.org \
--cc=phodina@protonmail.com \
/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.
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).