all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: MIPS support
Date: Wed, 6 May 2020 18:27:31 +0200	[thread overview]
Message-ID: <CAEwRq=pF=NieQUxzx0XA1NaqEEVF_VuUtvyMsBRzXrF89EvZvQ@mail.gmail.com> (raw)
In-Reply-To: <87sggdf7qm.fsf@gnu.org>

Hello,

> In the intervening years, interest faded away as free software friendly
> MIPS hardware became more rare.

I grabbed a gnubee during the crowdfunding campaign, but the CPU
is too low spec to do a lot of compilation on it.

> Perhaps it would be more honest to officially remove the MIPS port now?
>
> Technically that would involve removing it from the manual, from
> configure.ac, and little more.

From the manual or from the CI, to let the build farm do more useful things
I'm not against, but is it really making maintenance difficult by still being in
the codebase ?

> If there’s a need for it in the future, and developments happening for
> MIPS in general (for the GNU tool chain, the kernel, etc.), then we can
> always start a new MIPS port.

The kernel side looks good enough to me, there's a lot of openwrt
running on mips and it looks well maintained.

> Until then, POWER9 and perhaps RISC-V seem to have more
> appeal to free software hackers.

I have grabbed an old power8, that I also intend to put guix on.

> What do people think?

I may not be able to put huge time in it so won't ask you to keep it
just for me.

I'll restart working / trying things in the foreign archs area after my
list of pending things is drained a bit (guix-install.sh & tarball CI,
native-inputs lint warning chasing) but that's only wishful thinking
for now.

-- 
Vincent Legoll


  reply	other threads:[~2020-05-06 16:27 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 [this message]
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
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

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

  git send-email \
    --in-reply-to='CAEwRq=pF=NieQUxzx0XA1NaqEEVF_VuUtvyMsBRzXrF89EvZvQ@mail.gmail.com' \
    --to=vincent.legoll@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.