From: Stefan <Stefan_Kuhr@arcor.de>
To: help-guix@gnu.org
Subject: Aw: Another Raspberry Pi data point
Date: Sat, 13 Feb 2021 15:38:26 +0100 [thread overview]
Message-ID: <952BB538-8B2E-4708-AE78-D8308355DB78@arcor.de> (raw)
Hi!
The change in <https://issues.guix.gnu.org/44543> is waiting to be committed by someone. And I will send more changes to progress with the Raspberry support.
Currently I have a booting setup over NFS with the firmware blob, a customized U-Boot, Grub and kernel. There is no possibility yet to create an image, but I have changes ongoing with a different Grub package to make that possible.
I’m progessing slowly, I don’t have much spare time. And it seems that my personal interrests regarding Guix have only small intersections with other people’s interrests (who have commit rights), so it takes time for my patches to be applied. But I’m patient. :-)
My first contributions were to make NFS booting possible in general. This required changes in Guix and Grub. Then I focused on chainloading firmware and bootloaders. Now I’m about to provide Raspberry specific U-Boot packages (actually ready, but I’d first like to improve the defconfig handling, which may later also ease kernel modifications, see <https://issues.guix.gnu.org/45046>, which is also waiting to be committed). In the meantime I think I found a way to create an image with a chainloading Grub.
However, I currently hit a blocking issue with qemu, which is not buinding anymore on aarch64 – it is failing in the virtio-net-test. It is needed to build the Grub package. I found no reason why this started to fail, at least the same qemu sources were building with an older Guix version.
Any solution to get qemu building on aarch64 again wound be very welcome. :-)
When all this is done, a future step will be to find out if or how the linux-libre kernel is usable for the Raspberry and if the rpi-open-firmware (already packaged by Danny) can replace the firmware blob.
Bye
Stefan
reply other threads:[~2021-02-13 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=952BB538-8B2E-4708-AE78-D8308355DB78@arcor.de \
--to=stefan_kuhr@arcor.de \
--cc=help-guix@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.
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).