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

Christine Lemmer-Webber <cwebber@dustycloud.org> writes:

> Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> writes:
>
>> Christine Lemmer-Webber <cwebber@dustycloud.org> wrote:
>>
>>> I had thought looking at the manual of the MNT Reform that only the
>>> HDMI port required a blob.  This will be disappoiting if we can't get
>>> the Reform into Guix proper soon.  There are of course channels, and
>>> maybe the work here might have to move to one of those locations
>>> rather than getting committed to the main guix repo, but I hope not.
>>
>> In their "Re-Introducing Reform" blog post[3], MNT Research states the
>> following:
>>
>>> Unfortunately, during the boot process, i.MX8M requires a
>>> closed-source firmware for an embedded ARCompact processor in the
>>> Synopsys DDR4 PHY. This firmware, which is only a few kilobytes in
>>> size, is responsible for regulating the physical connection to the
>>> DDR chips in the face of changing temperatures. We are in contact
>>> with reverse engineers with the goal of analyzing what the
>>> capabilities of this so called PHY Utility Block (PUB) are, and to
>>> find out if we have a chance to replace this firmware at some point
>>> in the future.
>
> So, that is disappointing, but also a space for optimism I guess?  I
> would be curious to know more about this reverse engineering effort.
>
>> So it would also be a good idea to remind them about that and
>> potentially look for other declarations from MNT Research about the
>> DDR4 firmware.
>
> Yeah.

I talked with them a bit today btw.  There hasn't been progress, and the
conversation might have reignited some interest, but it was made clear
that this was not a current focus at the moment.


  parent reply	other threads:[~2021-09-08 18:10 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
2021-09-09 14:10                 ` Denis 'GNUtoo' Carikli
2021-09-08 18:08               ` Christine Lemmer-Webber [this message]
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=87czpj9bvw.fsf@dustycloud.org \
    --to=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).