unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: MIPS support
Date: Wed, 6 May 2020 13:35:36 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.20.2005061302170.5735@marsh.hcoop.net> (raw)
In-Reply-To: <CAEwRq=pF=NieQUxzx0XA1NaqEEVF_VuUtvyMsBRzXrF89EvZvQ@mail.gmail.com>

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

On Wed, 6 May 2020, Vincent Legoll wrote:

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

I also have a gnubee, and would love to be able to put Guix on it. 
However, so far I haven't put much time into getting it working. It would 
certainly be more fun to work on it with others :)

My impression is that the the gnubee is a different class of MIPS than the 
current port. I think that the gnubee is a SoC that is is targeted at home 
routers and is 32-bit, while the current port is 64-bit and targeted at 
chips like the longsoon. Is that correct?

There seems to be a a fair amount of the router-class hardware available 
that works with Free Software, but not much, if any, of the latter, more 
powerful hardware. Unfortunately, I think having the more powerful 
hardware available would make it much easier to work on the port.

[…]

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

I feel similarly. It's always sad to see things go (I used to have a 
collection of SPARC hardware, but let it go when I moved a few years ago), 
but no need to keep it just for me.

Vincent, it sounds like there are at least two of us. Maybe we can work 
together.

Best,
Jack

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

  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=alpine.DEB.2.20.2005061302170.5735@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --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).