unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: ARMHF flash image - Put on website under GuixSD
Date: Mon, 10 Sep 2018 14:28:52 +0200	[thread overview]
Message-ID: <877ejth6yj.fsf@gnu.org> (raw)
In-Reply-To: <20180907222110.50e6bac2@scratchpost.org> (Danny Milosavljevic's message of "Fri, 7 Sep 2018 22:21:10 +0200")

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> finally, https://hydra.gnu.org/build/3044681 (flash-image armhf) built.
>
> Can we put it on the website at https://www.gnu.org/software/guix/download/
> inside the GuixSD part?
>
> I think it would be nice to have something ready-to-go for ARM systems as well,
> and this would be a good start.  Apart from the bootloader, everything should
> work as-is in there.  And the user can either keep the original bootloader
> on the board or flash a new one after booting GuixSD - either in qemu or
> on a real machine.

I agree that it would be nice, but to what extent is this image generic
to all ARM boards?  My understanding is that images are necessarily
bound to a specific board.

Other considerations include the fact that it’s yet another image to
build when we make a release, but perhaps the solution is simply to
improve our automation and build farm availability.

Thanks,
Ludo’.

  reply	other threads:[~2018-09-10 12:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07 20:21 ARMHF flash image - Put on website under GuixSD Danny Milosavljevic
2018-09-10 12:28 ` Ludovic Courtès [this message]
2018-09-10 13:47   ` pelzflorian (Florian Pelz)
2018-09-10 15:12   ` Danny Milosavljevic
2018-09-10 15:45   ` Vagrant Cascadian
2018-09-10 20:54     ` Ludovic Courtès

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=877ejth6yj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).