all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Andreas Enge <andreas@enge.fr>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: GuixSD on AArch64
Date: Wed, 12 Dec 2018 15:26:42 +0100	[thread overview]
Message-ID: <87a7lag6sd.fsf@ponder.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20181212103650.GD3740@jurong>

On 2018-12-12, Andreas Enge wrote:
> On Mon, Oct 22, 2018 at 12:17:58PM -0700, Vagrant Cascadian wrote:
>> Looking like u-boot 2019.01 might be more likely, but modest patches
>> work with 2018.11-rc2. I'll probably bring the pinebook with me to the
>> Paris meetup in December... though with only 2GB of ram it might not
>> make the most exciting GuixSD system... :)
>
> did you come to the meeting,

Yes! it was good fun.

> and did you manage to install GuixSD on your Pinebook?

Not yet... The substitutes were below 1% for aarch64 the last few weeks,
and only recently have started catching up. And building natively
was... astoundingly slow.

I did get the patched u-boot pinebook into Guix, and tested it
manually. I haven't yet checked current status of linux-libre on
aarch64, which might need some additional kernel configuration features
enabled compared to recent Debian kernel versions.


live well,
  vagrant

  reply	other threads:[~2018-12-12 14:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-20 13:20 GuixSD on the SoftIron OverDrive 1000 (AArch64) Ludovic Courtès
2018-10-20 16:40 ` Jan Nieuwenhuizen
2018-10-22 12:29   ` Ludovic Courtès
2018-10-22 19:17     ` GuixSD on AArch64 Vagrant Cascadian
2018-10-24 13:01       ` Ludovic Courtès
2018-12-12 10:36       ` Andreas Enge
2018-12-12 14:26         ` Vagrant Cascadian [this message]
2018-10-20 18:29 ` GuixSD on the SoftIron OverDrive 1000 (AArch64) Efraim Flashner
2018-10-22 12:31   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7lag6sd.fsf@ponder.i-did-not-set--mail-host-address--so-tickle-me \
    --to=vagrant@debian.org \
    --cc=andreas@enge.fr \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.