unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: phodina <phodina@protonmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: U-Boot for Raspberry Pi
Date: Sat, 30 Oct 2021 15:05:32 -0700	[thread overview]
Message-ID: <87h7cygocz.fsf@yucca> (raw)
In-Reply-To: <QxiawUX4Q1CKPU8Wk8t8CvzTPxrXfSaKx4w4PbDbbG1dZuZIWwfnIAxs4vzrfWo7beK05xg8La-pd-WDw47ZOpKYvDIsDEQwhH9jXLNIyxs=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]

On 2021-10-30, phodina via wrote:
> 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.

Well, you still need to load u-boot from the broadcom
firmware/bootloader...


> 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?

There are install targets defined in gnu/bootloader/u-boot.scm, though
most (all?) of those targets install to a raw device offset, whereas
u-boot for the rpi needs u-boot.bin to be copied to your firmware
partition and needs to be specified as a "kernel" in config.txt, if I
recall correctly.


> (define-public u-boot-raspberry-pi-4
> (make-u-boot-package "rpi_4" "aarch64-linux-gnu"))

I would also try to keep the u-boot-BOARD matching the defconfig,
e.g. u-boot-rpi-4 instead of u-boot-raspberry-pi-4. Not for any
technical reason, per se, just keeping the u-boot target naming
consistent.

You might want to just build the u-boot package, and then manually copy
it to your firmware partition and configure that appropriately once, and
then just use guix to generate and update the extlinux.conf... I forget
the exact syntax to generate extlinux.conf without actually installing
u-boot, but I've done it in the past.

Another option would be to build the raspberry pi UEFI (not 100% sure of
the licensing, but reasonably free) instead of u-boot, and then use
guix's standard UEFI configuration with grub-efi and such.


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2021-10-30 22:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-30 21:39 U-Boot for Raspberry Pi phodina via
2021-10-30 22:05 ` Vagrant Cascadian [this message]
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=87h7cygocz.fsf@yucca \
    --to=vagrant@debian.org \
    --cc=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).