unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Guix on the MNT Reform
Date: Fri, 08 May 2020 18:30:05 +0000	[thread overview]
Message-ID: <ofIg9YWrGNHxeJhNAbyvWzMxf_wSzNjI1XtKGcVIW3NqtWbXw4EsewsA4gCN7PK4LCaT49Y533gFfBWr8WdG6-Rwn-gkxcBBn5cPUhet1Eo=@elenq.tech> (raw)
In-Reply-To: <87ftcaqxer.fsf@dustycloud.org>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, May 8, 2020 5:06 PM, Christopher Lemmer Webber <cwebber@dustycloud.org> wrote:

> I'm very excited to see the MNT Reform launch:
>
> https://www.crowdsupply.com/mnt/reform
> https://www.crowdsupply.com/mnt/reform/updates/the-campaign-is-live
>
> Completely hackable laptop; all the designs (that are possible) are
> libre, and you can even 3d print to replace many of the parts.
>
> However my impression is that running Guix on ARM is not necessarily
> straightforward. I haven't tried it yet.
>
> Most important specs:
>
> CPU: NXP/Freescale i.MX8MQ with 4x ARM Cortex-A53 cores (1.5 GHz),
> 1x Cortex-M4F core. CPU and RAM are on exchangeable SO-DIMM sized
> module.
> RAM: 4GB LPDDR4 memory
> GPU: Vivante GC7000Lite GPU with mainline Linux drivers and OpenGL
> 2.1, ES 2.0
>
> (My other main worry is: that's pretty light on RAM these days...!
> But hey, maybe incentive for me to cut the fat in the programs I use a
> bit more...)
>
> I am thinking of getting one and running Guix on it. It would be nice
> to know that I wouldn't be alone. :) Anyone else planning to get one
> and joing me on the journey on maybe the most hacker-oriented laptop
> ever?
>
> -   Chris

Hey Chris,

It's a great project, I've been checking the schematics and stuff myself and I liked it a lot. It's a great reference design to build on top of.
I can't afford one atm but I can do my best to help you play with it.
I'm really interested on if it's able to run Guix and I'd like to know about your experience with it.

Please keep me posted on your journey!

Best,
Ekaitz


  parent reply	other threads:[~2020-05-08 18:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 15:06 Guix on the MNT Reform Christopher Lemmer Webber
2020-05-08 18:19 ` Simon Josefsson
2020-05-09 13:03   ` Christopher Lemmer Webber
2020-05-08 18:30 ` Ekaitz Zarraga [this message]
2020-05-08 18:52 ` Vagrant Cascadian
2020-05-08 19:16   ` Leo Famulari
2020-05-08 20:44 ` John Soo
2020-09-02 22:22 ` Andreas Enge
2020-09-13 14:10   ` Andreas Enge
2020-09-15  3:23     ` Fredrik Salomonsson
2021-08-17 17:24 ` Christine Lemmer-Webber
2021-08-17 23:49   ` Fredrik Salomonsson
2021-09-05  1:31     ` Christine Lemmer-Webber
2021-09-06 17:07       ` Christine Lemmer-Webber
2021-09-06 19:37         ` Fredrik Salomonsson
2021-09-06 20:50           ` Christine Lemmer-Webber
2021-09-06 23:59             ` Fredrik Salomonsson
2021-09-07  1:13               ` Fredrik Salomonsson
2021-09-07  4:36       ` Denis 'GNUtoo' Carikli
2021-09-07 18:18         ` Christine Lemmer-Webber
2021-09-07 20:07           ` Denis 'GNUtoo' Carikli
2021-09-08 10:32             ` Christine Lemmer-Webber
2021-09-08 16:47               ` Vagrant Cascadian
2021-09-08 18:10                 ` Christine Lemmer-Webber
2021-09-09 14:10                 ` Denis 'GNUtoo' Carikli
2021-09-08 18:08               ` Christine Lemmer-Webber
2021-08-18  0:36 ` Jonathan McHugh
2021-08-29 19:10   ` Joshua Branson
2021-08-29 21:38   ` Jonathan McHugh
2021-08-29 23:27     ` Joshua Branson
2021-08-30  9:02     ` Jonathan McHugh

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='ofIg9YWrGNHxeJhNAbyvWzMxf_wSzNjI1XtKGcVIW3NqtWbXw4EsewsA4gCN7PK4LCaT49Y533gFfBWr8WdG6-Rwn-gkxcBBn5cPUhet1Eo=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=cwebber@dustycloud.org \
    --cc=help-guix@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.
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).