From: Vagrant Cascadian <vagrant@debian.org>
To: Farshid Karimi <farshidk49@gmail.com>, help-guix@gnu.org
Subject: Re: Run GuixSD on Raspberry pi
Date: Wed, 23 Oct 2019 11:54:09 -0700 [thread overview]
Message-ID: <875zkf1eem.fsf@yucca> (raw)
In-Reply-To: <CAL0x6=KU+Ss3jgGHBB=veePVdTGjwkYr7Z9AjdFdv2TJCRsxcg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On 2019-10-23, Farshid Karimi wrote:
> I know that could install guix as a package manager on armhf
> architecture.Including raspberry pi board.
> But is there any way to install guixsd image on raspberry pi?
> I saw the gnu/system/install.scm and there is some little board that
> supported by it.
If you treat the non-free boot firmware like people treat BIOS/EFI on
x86 systems, and leave it up to the end-user to set that up, it's
probably technically possible.
There may be some drivers that require non-free firmware (e.g. wireless)
that will not work with Guix's linux-libre kernel.
The two options I see would be to add support for the boot configuration
used by the raspberry pi firmware, or for a little more flexible option,
configure the raspberry pi firmware to load u-boot and then use the
existing infrastructure to generate u-boot configuration files.
Since there's at least one major non-free component involved, I'm not
quite sure how it all sits with following the FSDG:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
Though, one could treat that like BIOS/EFI on x86...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2019-10-23 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 13:32 Run GuixSD on Raspberry pi Farshid Karimi
2019-10-23 18:54 ` Vagrant Cascadian [this message]
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=875zkf1eem.fsf@yucca \
--to=vagrant@debian.org \
--cc=farshidk49@gmail.com \
--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).