unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Christine Lemmer-Webber <cwebber@dustycloud.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: help-guix@gnu.org
Subject: Re: Guix on the MNT Reform
Date: Wed, 08 Sep 2021 14:10:32 -0400	[thread overview]
Message-ID: <87a6kn9bt4.fsf@dustycloud.org> (raw)
In-Reply-To: <87czpjqak9.fsf@yucca>

Vagrant Cascadian <vagrant@debian.org> writes:

> [[PGP Signed Part:Undecided]]
> On 2021-09-08, Christine Lemmer-Webber wrote:
>> Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> writes:
>>> Here this I'MX8 issue also affect the Librem5 for instance, and
>>> probably several other devices as well. And the neat thing about the
>>> Librem 5 is that as I understand is that the modem and the WiFi cards
>>> are removable.
>>
>> I am guessing the Pinephone has a similar issue (or more) though I'm not
>> sure.
>
> The Pinephone doesn't have that specific issue, as it's a different CPU
> (Allwinner A64), the same used on the pine64+ and pinebook, which are
> supported in Guix's u-boot. I vaguely recall those boards having similar
> types of issues early on requiring some binary blobs, but it was fixed
> in u-boot upstream with a free implementation!

Oh good news!  It's nice to hear of success stories like this.

Speaking of, the other "guix system image" thing on my queue was to work
on getting Guix running (if not usable as a phone) on my pinephone.

I tried:

  guix system image --image-type=pine64-raw pine64-barebones.scm

and flashing the output to an SD card, but that didn't boot (or if it
did, it didn't display anything on the screen).  So I assume some extra
work is necessary.

 - Christine


  reply	other threads:[~2021-09-08 18:12 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
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 [this message]
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=87a6kn9bt4.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=help-guix@gnu.org \
    --cc=vagrant@debian.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).