From: Aleksandr Vityazev <avityazew@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: Efraim Flashner <efraim@flashner.co.il>,
guix-devel@gnu.org, guix-sysadmin <guix-sysadmin@gnu.org>
Subject: Re: RISC-V (riscv64-linux) substitutes are coming
Date: Tue, 09 May 2023 18:24:11 +0300 [thread overview]
Message-ID: <87a5ydedes.fsf@posteo.org> (raw)
In-Reply-To: <87r0rp37jo.fsf@cbaines.net> (Christopher Baines's message of "Tue, 09 May 2023 15:22:40 +0100")
Hi,
On 2023-05-09, 15:22 +0100, Christopher Baines <mail@cbaines.net> wrote:
> Efraim Flashner <efraim@flashner.co.il> writes:
>
>> [[PGP Signed Part:Undecided]]
>> On Tue, May 09, 2023 at 02:40:21PM +0100, Christopher Baines wrote:
>>> Hey!
>>>
>>> Almost a year ago now [1] I mentioned that I had received a HiFive
>>> Unmatched board, but I hadn't got it doing anything yet.
>>>
>>> 1: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00104.html
>>
>> Some would say that's almost two years ago!
>
> Indeed, I got my maths wrong! Time is really getting on :/
>
>>> In the last few days I've made some time to take a look at it again and
>>> try to get it connected up to the bordeaux build farm.
>>>
>>> This has been somewhat successful, you should be able to see the machine
>>> (named rochor) on the prototype activity viewer [2].
>>>
>>> 2: https://bordeaux.guix.gnu.org/activity
>>>
>>> Unfortunately it seems a bit stuck trying to upload the build results
>>> back to the coordinator due to the suspendable ports issues in
>>> guile-gnutls, but that should be fixed in the latest release so
>>> hopefully I'll be able to deploy that fix soon.
>>>
>>> It's also just currently a bare board hooked up to a spare power supply
>>> I have. I'll try and cost up a dedicated power supply plus case for it,
>>> and if anyone has suggestions for minimal mini-itx compatible cases,
>>> please let me know!
>>>
>>> This is a start, but more hardware will be needed to keep up with the
>>> master branch, plus testing patches and other branches, so if you have
>>> hardware to hand, or know of hardware available for purchase that might
>>> be suitable, that would be really useful to know about.
>>
>> That's really exciting!
>>
>> I've been having good luck with the visionfive1 as a build machine. My
>> visionfive2 gets a little hot and I'm looking at getting a desk fan to
>> blow at it and some of the other boards that get a bit hot while
>> building.
I also use visionfive2 as my build machine. Quite happy with it. I have
a fairly large heatsink installed without a fan, the temperature does
not exceed 60 degrees at full load.
> Cool, well let me know if any of those can be hooked up to the build
> farm. It's quite easy and obviously you can still use them (and just
> stop the build coordinator agent) if you need to.
>
I'd give it a try. Although now there is only a 256GB ssd plugged in and
no dedicated ip address. I don't know how the coordinator works, maybe
it doesn't matter, I need to see how it all works.
--
Best regards,
Aleksandr Vityazev
next prev parent reply other threads:[~2023-05-09 19:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 13:40 RISC-V (riscv64-linux) substitutes are coming Christopher Baines
2023-05-09 14:09 ` Efraim Flashner
2023-05-09 14:22 ` Christopher Baines
2023-05-09 15:24 ` Aleksandr Vityazev [this message]
2023-05-09 15:41 ` Christopher Baines
2023-05-09 18:33 ` Aleksandr Vityazev
2023-05-09 15:57 ` Efraim Flashner
2023-05-09 16:26 ` Aleksandr Vityazev
2023-05-09 14:19 ` 宋文武
2023-05-09 14:27 ` Christopher Baines
2023-05-10 12:44 ` 宋文武
2023-05-13 3:34 ` 宋文武
2023-05-13 3:49 ` 宋文武
2023-05-13 10:15 ` 宋文武
2023-05-09 14:29 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-09 14:33 ` Christopher Baines
2023-05-09 15:20 ` Janneke Nieuwenhuizen
2023-05-10 9:05 ` Andreas Enge
2023-05-10 9:24 ` Christopher Baines
2023-05-11 11:15 ` 郑俊杰
[not found] ` <87mt298pm9.fsf@qq.com>
2023-05-12 16:35 ` Z572
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=87a5ydedes.fsf@posteo.org \
--to=avityazew@gmail.com \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=guix-sysadmin@gnu.org \
--cc=mail@cbaines.net \
/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).