unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: MIPS support
Date: Wed, 6 May 2020 14:28:27 -0400	[thread overview]
Message-ID: <20200506182827.GB27121@jasmine.lan> (raw)
In-Reply-To: <CAEwRq=pF=NieQUxzx0XA1NaqEEVF_VuUtvyMsBRzXrF89EvZvQ@mail.gmail.com>

On Wed, May 06, 2020 at 06:27:31PM +0200, Vincent Legoll wrote:
> I grabbed a gnubee during the crowdfunding campaign, but the CPU
> is too low spec to do a lot of compilation on it.

I'm not an expert on MIPS but I *think* the GnuBee uses a different
architecture than what Guix was ported to.

So, whether or not to officially retire the Guix MIPS port would not be
related to supporting Guix on the GnuBee, which would be cool!
Declarative NAS configuration would be nice :)

It would be helpful to get some clarification of the relationship
between these architectures before deciding what to do.


  parent reply	other threads:[~2020-05-06 18:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 19:32 MIPS support Christopher Baines
2020-04-08 22:07 ` Leo Famulari
2020-05-06 14:39   ` Ludovic Courtès
2020-05-06 16:27     ` Vincent Legoll
2020-05-06 17:35       ` Jack Hill
2020-05-06 17:45       ` Christopher Baines
2020-05-06 18:23       ` Leo Famulari
2020-05-17 22:12         ` Ludovic Courtès
2020-05-18  7:01           ` Efraim Flashner
2020-05-24 21:03             ` Ludovic Courtès
2020-05-25  9:44               ` Efraim Flashner
2020-05-25 21:20                 ` Ludovic Courtès
2020-05-26  6:15                   ` Efraim Flashner
2020-05-06 18:28       ` Leo Famulari [this message]
2020-05-06 22:16         ` Vincent Legoll
2020-05-08 10:55           ` Vincent Legoll
2020-05-26  9:28           ` Christopher Baines

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=20200506182827.GB27121@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=vincent.legoll@gmail.com \
    /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).