From: ludo@gnu.org (Ludovic Courtès)
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: GuixSD on AArch64
Date: Wed, 24 Oct 2018 15:01:48 +0200 [thread overview]
Message-ID: <87mur34hxf.fsf@gnu.org> (raw)
In-Reply-To: <87sh0x3i55.fsf@aikidev.net> (Vagrant Cascadian's message of "Mon, 22 Oct 2018 12:17:58 -0700")
Vagrant Cascadian <vagrant@debian.org> skribis:
> On 2018-10-22, Ludovic Courtès wrote:
>> On IRC earlier today Vagrant mentioned that the Pinebook AArch64 laptop
>> (see <https://www.pine64.org/?page_id=3707>) should be able to run
>> GuixSD when Linux-libre 4.19 and U-Boot 2018.11 are out, with 100% free
>> software. That may give another incentive to work on AArch64.
>
> Looking like u-boot 2019.01 might be more likely, but modest patches
> work with 2018.11-rc2. I'll probably bring the pinebook with me to the
> Paris meetup in December... though with only 2GB of ram it might not
> make the most exciting GuixSD system... :)
Well, I know there’s still some way to go (in particular wrt. the Guile
compiler memory consumption), but we should aim to make Guix usable on
such systems.
> Very similar is the free open-source hardware Teres-I from olimex:
>
> https://www.olimex.com/Products/DIY-Laptop/
>
> ... Which is just a kit with all the parts you assemble yourself!
Looks like a lot of fun!
Ludo’.
next prev parent reply other threads:[~2018-10-24 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 13:20 GuixSD on the SoftIron OverDrive 1000 (AArch64) Ludovic Courtès
2018-10-20 16:40 ` Jan Nieuwenhuizen
2018-10-22 12:29 ` Ludovic Courtès
2018-10-22 19:17 ` GuixSD on AArch64 Vagrant Cascadian
2018-10-24 13:01 ` Ludovic Courtès [this message]
2018-12-12 10:36 ` Andreas Enge
2018-12-12 14:26 ` Vagrant Cascadian
2018-10-20 18:29 ` GuixSD on the SoftIron OverDrive 1000 (AArch64) Efraim Flashner
2018-10-22 12:31 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mur34hxf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.