all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: Application for aarch64 computing resources
Date: Fri, 02 Apr 2021 11:56:03 -0700	[thread overview]
Message-ID: <87mtug7by4.fsf@yucca> (raw)
In-Reply-To: <YGdlyMtpgYYJrj3X@jasmine.lan>

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

On 2021-04-02, Leo Famulari wrote:
> Those of us who watch the Guix build farm [0] closely have identified
> the lack of capacity for building ARM binaries as a serious limitation.
>
> As part of our efforts to improve the situation, I've applied for
> donation of aarch64 (64-bit ARM) computing resources for the Guix build
> farm:
>
> https://github.com/WorksOnArm/cluster/issues/254
>
> This is the official program for getting donations of this type; it's a
> partnership between Equinix and ARM.
>
> Let me know if you see any room for improvement; the application can be
> edited.

You might want to also ask for hardware that has the extensions for
32-bit arm, if we also want to improve substitute availability for armhf
too. The 32-bit extensions are optional for aarch64, and thus not all
hardware supports it.


live well,
  vagrant

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

  reply	other threads:[~2021-04-02 18:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02 18:43 Application for aarch64 computing resources Leo Famulari
2021-04-02 18:56 ` Vagrant Cascadian [this message]
2021-04-02 20:25   ` Leo Famulari
2021-04-02 21:01     ` Léo Le Bouter
2021-04-02 18:57 ` Nicolò Balzarotti
2021-04-02 20:20   ` Leo Famulari
2021-04-03 21:28 ` Katherine Cox-Buday
2021-04-03 23:14   ` Leo Famulari
2021-05-05  0:42 ` Leo Famulari
2021-05-06 16:32   ` 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=87mtug7by4.fsf@yucca \
    --to=vagrant@debian.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.