From: "Ludovic Courtès" <ludo@gnu.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix on the ASUS C201PA
Date: Fri, 15 Mar 2019 12:23:22 +0100 [thread overview]
Message-ID: <87ef78755h.fsf@gnu.org> (raw)
In-Reply-To: <875zswjwoc.fsf@ngyro.com> (Timothy Sample's message of "Wed, 06 Mar 2019 02:20:51 -0500")
Hello!
Timothy Sample <samplet@ngyro.com> skribis:
> I was able to get Guix to boot on an ASUS Chromebook C201PA. This model
> of computer is pretty neat. It’s an ARMv7 (32-bit) machine that can be
> run with entirely free software. There is even a free graphics driver
> in the works [1].
>
> I’ve attached a (messy) patch that adds a (hacky) bootloader definition
> for Depthcharge and a Linux-Libre package that works on the machine
> (using an unsupported version of Linux-Libre). All those parenthetical
> comments are supposed to suggest that this work is not really finished.
> Now that the computer runs Guix, it should be straight-forward (if time
> consuming) to fix some of these problems and arrive at something nice.
Impressive work!
The patch is really not what I expected given the qualifiers you gave
above. :-) It could use more comments to explain what’s going on but
apart from that it looks rather clean to my eyes.
What do you think would be the best course of action to integrate it?
Wait for Vagrant to test it and fix a couple of things? ;-) Or…?
Thank you,
Ludo’.
next prev parent reply other threads:[~2019-03-15 13:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 7:20 Guix on the ASUS C201PA Timothy Sample
2019-03-06 8:59 ` Vagrant Cascadian
2019-03-06 14:33 ` Timothy Sample
2019-03-10 2:42 ` Vagrant Cascadian
2019-03-17 6:47 ` Vagrant Cascadian
2019-03-17 15:20 ` Timothy Sample
2019-03-18 5:38 ` Vagrant Cascadian
2019-03-19 7:22 ` Danny Milosavljevic
2019-03-23 16:33 ` Ludovic Courtès
2019-03-23 19:10 ` Mark H Weaver
2019-03-23 21:04 ` Vagrant Cascadian
2019-03-24 18:19 ` Vagrant Cascadian
2019-03-06 12:02 ` swedebugia
2019-03-06 15:46 ` mikadoZero
2019-03-15 11:23 ` Ludovic Courtès [this message]
2019-03-15 17:39 ` Timothy Sample
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=87ef78755h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=samplet@ngyro.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).