From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel@gnu.org
Subject: Re: RISCV porting effort
Date: Sat, 12 Jun 2021 00:07:42 +0200 [thread overview]
Message-ID: <87o8cc3vip.fsf@gnu.org> (raw)
In-Reply-To: <YMIRqvNSP/NzehWs@3900XT> (Efraim Flashner's message of "Thu, 10 Jun 2021 16:20:42 +0300")
Hello!
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Tue, Jun 08, 2021 at 03:43:44PM +0200, Ludovic Courtès wrote:
[...]
>> If the HiFive works fine, let me remind you that we have budget to buy
>> hardware, so we could just as well order a couple of these right away
>> (maybe you’ll have Guix System running by the time we receive them ;-)).
>
> On one hand they seem similar to some of our aarch64 boards (but with
> 16GB of RAM), on the other hand it'd be a coup to announce serious
> support for the platform so quickly.
I’m not saying we should announce anything, but rather that we get ready
for when the port is functional (especially if there’s typically 6
months between ordering and shipping).
> I had to pay import tax when I received mine, and I assume those in
> Europe did too, so I'd recommend they be hosted in the US since IIRC
> they're shipping from Texas. It might be nice to wait until we have it
> working for sure, but the lead time is still expected to be 6 months
> between ordering and shipping dates.
OK. I don’t doubt “working for sure” will eventually happen; I wouldn’t
be surprised if it takes less than 6 months even. :-)
(I’m not talking about the reduced bootstrap seeds, just the gross
bootstrap as currently done on ARM.)
> I suppose if something else comes along that's faster we could always
> cancel an order and switch to that.
>
> I have mine sitting in a mini-ITX case, using a libre-respecting NVIDIA
> card. Definitely a more serious board than the aarch64 boards I've
> bought in the past.
Good!
Ludo’.
next prev parent reply other threads:[~2021-06-11 22:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 7:09 RISCV porting effort Efraim Flashner
2021-06-07 15:37 ` Christopher Lemmer Webber
2021-06-08 13:43 ` Ludovic Courtès
2021-06-08 22:28 ` Gabriel Wicki
2021-06-10 13:22 ` Efraim Flashner
2021-06-11 21:07 ` Ludovic Courtès
2021-06-10 13:20 ` Efraim Flashner
2021-06-11 22:07 ` Ludovic Courtès [this message]
2021-06-18 13:05 ` RISCV porting effort (now in stock @mouser) Gabriel Wicki
2021-06-11 11:16 ` RISCV porting effort Efraim Flashner
2021-06-13 17:24 ` Vagrant Cascadian
2021-06-14 7:27 ` Efraim Flashner
2021-06-15 1:00 ` Vagrant Cascadian
2021-06-15 12:37 ` Efraim Flashner
2021-06-13 21:21 ` Christopher Baines
2021-06-20 15:37 ` Ludovic Courtès
2022-06-16 1:46 ` Pjotr Prins
2022-06-16 18:12 ` Maxim Cournoyer
2022-06-17 16:08 ` Ludovic Courtès
2022-06-17 22:52 ` Pjotr Prins
2022-06-20 7:45 ` Pjotr Prins
2022-06-22 13:37 ` Ludovic Courtès
2022-06-22 15:19 ` Ekaitz Zarraga
2022-06-28 8:54 ` Efraim Flashner
2022-06-30 12:01 ` Ludovic Courtès
2022-07-03 9:07 ` Efraim Flashner
2022-06-24 6:37 ` Pjotr Prins
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=87o8cc3vip.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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.
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).