From nobody Tue Nov 12 21:50:26 2024 X-Original-To: freebsd-riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Xp0TN3qYfz5cfY2 for ; Tue, 12 Nov 2024 21:50:32 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mail.oetec.com", Issuer "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xp0TM3mSFz4Q75 for ; Tue, 12 Nov 2024 21:50:31 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=GEP4LoDR; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org; dmarc=pass (policy=quarantine) header.from=blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 4ACLoR7d039025 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Tue, 12 Nov 2024 16:50:28 -0500 (EST) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1731448228; bh=dinfqeu5mT14y1UbctjWBtZlwd1P8VI7USVG6NZEkdk=; h=Date:From:Subject:To; b=GEP4LoDRYmoWsUWSoDXqcQzbt4g20Na0SJEKFHHs11NTlahIaRbcHkyeew5f9/n1u Sh04npzaW0qxYGbEIA89FUVO9C2f2N7jvzsp1ZH+N8jEVZc9ba49tTmVEJq4zDpyHn daP38dHv05zo2KD1yMFzE7wnkzYKZaDpRToYhUgh1OnxbaM8R8E1HG0SneTKD1HX/9 2z2+zv2uyuotR77zFrloG5gKBJLhwqTYcjtHiS1PpABK4E8A8kl9mbHJpZmPy8e5Y7 U/Vlz3FyeAlPdn3m7Ipf/wOgiLwd2sOKxS5g3yRM2r2067jKtKMNva/LARB6o4I5yL lep6E8e1kbcHw== Message-ID: <62b7409c-899a-4888-96bf-07af49c1a791@blastwave.org> Date: Tue, 12 Nov 2024 16:50:26 -0500 List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Dennis Clarke Subject: And now the dumb question du jour To: freebsd-riscv@FreeBSD.org Content-Language: en-CA Organization: GENUNIX Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 4ACLoR7d039025 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Spamd-Result: default: False [-4.69 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-riscv@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+]; MLMMJ_DEST(0.00)[freebsd-riscv@FreeBSD.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4Xp0TM3mSFz4Q75 X-Spamd-Bar: ---- Dear RISC-V folks : Given the recent big LLVM/Clang update into the src tree[1] it seemed reasonable to do a full buildworld/kernel and that worked out very well. No LLVM hack patch required ! enceladus# uname -apKU FreeBSD enceladus 15.0-CURRENT FreeBSD 15.0-CURRENT #1 main-n273541-cdd3234186b1: Tue Nov 12 08:49:15 GMT 2024 root@enceladus:/usr/obj/usr/src/riscv.riscv64/sys/SIFIVE-COMPAT11 riscv riscv64 1500026 1500026 enceladus# cc --version FreeBSD clang version 19.1.3 (https://github.com/llvm/llvm-project.git llvmorg-19.1.3-0-gab51eccf88f5) Target: riscv64-unknown-freebsd15.0 Thread model: posix InstalledDir: /usr/bin Build config: +assertions enceladus# At this point I want to rebuild the few packages that I have. Here is where I get a bit confused about poudriere. enceladus# enceladus# poudriere ports -l PORTSTREE METHOD TIMESTAMP PATH latest git+https 2024-11-08 17:21:03 /poudriere/ports/latest enceladus# enceladus# poudriere jails -l JAILNAME VERSION ARCH METHOD TIMESTAMP PATH enceladus# enceladus# zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT rv64 912G 27.6G 884G - - 11% 3% 1.00x ONLINE - enceladus# enceladus# poudriere jail -c -j 150rv64 -a riscv64 -b -m src=/usr/src -f rv64/poudriere/jails/150rv64 -v main [00:00:00] Creating 150rv64 fs at /poudriere/jails/150rv64... done [00:00:00] Copying /usr/src to /poudriere/jails/150rv64/usr/src... done [00:04:04] Starting make buildworld with 4 jobs --- buildworld --- make[1]: "/poudriere/jails/150rv64/usr/src/Makefile.inc1" line 164: Unknown target riscv64:riscv64. in .for loop from /poudriere/jails/150rv64/usr/src/Makefile.inc1:162 with _t = riscv64 in directory /poudriere/jails/150rv64/usr/src make[1]: stopped making "buildworld" in /poudriere/jails/150rv64/usr/src make: stopped making "buildworld" in /poudriere/jails/150rv64/usr/src [00:04:06] Error: Failed to 'make buildworld' [00:04:06] Error while creating jail, cleaning up. [00:04:06] Removing 150rv64 jail... done [00:04:13] Cleaning 150rv64 data... done enceladus# Unknown target ? Excuse me ? enceladus# sysctl hw.fdt.model hw.fdt.model: SiFive HiFive Unmatched A00 enceladus# Am I missing something blunt force trauma obvious here? -- Dennis Clarke [1] https://cgit.freebsd.org/src/commit/?id=d686ce931cab72612a9e1ada9fe99d65e11a32a3 From nobody Tue Nov 12 21:56:11 2024 X-Original-To: freebsd-riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Xp0c91BmPz5cgMq for ; Tue, 12 Nov 2024 21:56:25 +0000 (UTC) (envelope-from jrtc27@jrtc27.com) Received: from mail-wm1-f45.google.com (mail-wm1-f45.google.com [209.85.128.45]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xp0c86Fs9z4Qgr for ; Tue, 12 Nov 2024 21:56:24 +0000 (UTC) (envelope-from jrtc27@jrtc27.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-f45.google.com with SMTP id 5b1f17b1804b1-43152b79d25so51995265e9.1 for ; Tue, 12 Nov 2024 13:56:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731448583; x=1732053383; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=6Q766b0RqAhrkHyha6GcFxV4I2MziNdWrKA1ZN/N5bQ=; b=GE2T6XgtLbl1uVh8zPV1KeOYxRexB+fpjLETJAUNgQGkARQ8786kFdOtU3KG3jgt7O jzc/qWOaV6s6XFrPjVW6EIXPdVZiPg9kqbb0I1hyubAkYOME32eiQH2bR0DXi6+BBAPE 55OPH4wotwXYiTLmltHcix8q3u35jPcqcoONj/DWrTb+hLTZ5DtZ0RYNsbvl+nzI+Pql xhgG3jSwSeqoKOrBTUsfuNxYrHuLfzEaRBm5gJIegt2WOGw4Z1Dnmg0vTHtJD1u0SvQ2 yH8q6EutssMvZ4VSi8wQ+/+Hrw2wfFzDjsI+5KJg4K7LVrXZZgK8vqEsLhIqhXhr/z24 vu6A== X-Gm-Message-State: AOJu0YzzXlHbVnFsLU0xi7YAViH+sYzAJ/qyxA72BzDZ79b8GxhoVoYD x4WlOls4I9M0mDZ2iqrZvEY8hE26i3gzxYNpiRG7ZFArErlJ5Iln9YqWme5Ei1hyTXie6DWYFZG i X-Google-Smtp-Source: AGHT+IFHgXIRfJPdGpf0yhWbCh8JfQdMTBpzEXzkocuT1Nm/CV/5NLiQbZkbX5zz4zELh4uUwyk6IQ== X-Received: by 2002:a05:6000:400e:b0:382:531:536f with SMTP id ffacd0b85a97d-3820df67247mr457549f8f.30.1731448583247; Tue, 12 Nov 2024 13:56:23 -0800 (PST) Received: from smtpclient.apple ([131.111.5.201]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-381ed9707d3sm16245449f8f.19.2024.11.12.13.56.21 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Nov 2024 13:56:22 -0800 (PST) Content-Type: text/plain; charset=us-ascii List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\)) Subject: Re: And now the dumb question du jour From: Jessica Clarke In-Reply-To: <62b7409c-899a-4888-96bf-07af49c1a791@blastwave.org> Date: Tue, 12 Nov 2024 21:56:11 +0000 Cc: "freebsd-riscv@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <62b7409c-899a-4888-96bf-07af49c1a791@blastwave.org> To: Dennis Clarke X-Mailer: Apple Mail (2.3826.200.121) X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4Xp0c86Fs9z4Qgr X-Spamd-Bar: ---- On 12 Nov 2024, at 21:50, Dennis Clarke wrote: >=20 >=20 > Dear RISC-V folks : >=20 > Given the recent big LLVM/Clang update into the src tree[1] it > seemed reasonable to do a full buildworld/kernel and that worked out > very well. No LLVM hack patch required ! >=20 > enceladus# uname -apKU > FreeBSD enceladus 15.0-CURRENT FreeBSD 15.0-CURRENT #1 = main-n273541-cdd3234186b1: Tue Nov 12 08:49:15 GMT 2024 = root@enceladus:/usr/obj/usr/src/riscv.riscv64/sys/SIFIVE-COMPAT11 riscv = riscv64 1500026 1500026 >=20 > enceladus# cc --version > FreeBSD clang version 19.1.3 (https://github.com/llvm/llvm-project.git = llvmorg-19.1.3-0-gab51eccf88f5) > Target: riscv64-unknown-freebsd15.0 > Thread model: posix > InstalledDir: /usr/bin > Build config: +assertions > enceladus# >=20 > At this point I want to rebuild the few packages that I have. Here is > where I get a bit confused about poudriere. >=20 > enceladus# > enceladus# poudriere ports -l > PORTSTREE METHOD TIMESTAMP PATH > latest git+https 2024-11-08 17:21:03 /poudriere/ports/latest > enceladus# > enceladus# poudriere jails -l > JAILNAME VERSION ARCH METHOD TIMESTAMP PATH > enceladus# > enceladus# zpool list > NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP = HEALTH ALTROOT > rv64 912G 27.6G 884G - - 11% 3% 1.00x = ONLINE - > enceladus# > enceladus# poudriere jail -c -j 150rv64 -a riscv64 -b -m src=3D/usr/src = -f rv64/poudriere/jails/150rv64 -v main > [00:00:00] Creating 150rv64 fs at /poudriere/jails/150rv64... done > [00:00:00] Copying /usr/src to /poudriere/jails/150rv64/usr/src... = done > [00:04:04] Starting make buildworld with 4 jobs > --- buildworld --- > make[1]: "/poudriere/jails/150rv64/usr/src/Makefile.inc1" line 164: = Unknown target riscv64:riscv64. > in .for loop from = /poudriere/jails/150rv64/usr/src/Makefile.inc1:162 with _t =3D riscv64 > in directory /poudriere/jails/150rv64/usr/src >=20 > make[1]: stopped making "buildworld" in = /poudriere/jails/150rv64/usr/src >=20 > make: stopped making "buildworld" in /poudriere/jails/150rv64/usr/src > [00:04:06] Error: Failed to 'make buildworld' > [00:04:06] Error while creating jail, cleaning up. > [00:04:06] Removing 150rv64 jail... done > [00:04:13] Cleaning 150rv64 data... done > enceladus# >=20 >=20 > Unknown target ? >=20 > Excuse me ? >=20 > enceladus# sysctl hw.fdt.model > hw.fdt.model: SiFive HiFive Unmatched A00 > enceladus# >=20 > Am I missing something blunt force trauma obvious here? The RISC-V port is MACHINE=3Driscv MACHINE_ARCH=3Driscv64 (c.f. MACHINE=3Darm64 MACHINE_ARCH=3Daarch64 or MACHINE=3Dpowerpc MACHINE_ARCH=3Dpowerpc64), so you need to give -a riscv.riscv64 to poudriere rather than -a riscv64 (which is shorthand for -a riscv64.riscv64), unlike amd64 where MACHINE=3DMACHINE_ARCH=3Damd64 so = the shorthand works. Building src is smarter about inferring one from the other rather than defaulting to them being the same, but poudriere is not. Jess From nobody Tue Nov 12 22:35:36 2024 X-Original-To: riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Xp1TV0MgYz5ck18 for ; Tue, 12 Nov 2024 22:35:42 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mail.oetec.com", Issuer "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xp1TT0rcLz4VSm for ; Tue, 12 Nov 2024 22:35:41 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=FvfI6IQ9; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org; dmarc=pass (policy=quarantine) header.from=blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 4ACMZaSg040700 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Tue, 12 Nov 2024 17:35:38 -0500 (EST) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1731450938; bh=iVPfdbIsaqKCxFIwnLaUOhLWvDdb+JtyU1lkPLGw9bc=; h=Date:Subject:To:References:From:In-Reply-To; b=FvfI6IQ9ZYZ43OR9qjEZz8aPAxwTEPgvyN4M6Y2LxatI87NF/kZi2aPqPF5SjHvuk 0dQVpsB1JmHE+QtaB/u0wzXrv8pXh1IvG2bosrCphjs2zmZCf3XLlehMyv8sVM8ajt 1rjrDWpuqQV4wWK1TW5AXTe5xRRmwgxcAH5dPs0PFMYlEllHgIXkAUzu2kxERw/L03 NVBszAqC+7+q3E2UY+XhFTfONwcy8sGV9pYcs8ya6sjxxz0h+QmaKJqfhDjFt4klOh KVgW5sotnh56TcC7xYwgHxJNKSXdzdTWRY6dlcVLgKjDixdXcRgFzHrl1oWNwlTWav 1tdDFahSUYjmQ== Message-ID: Date: Tue, 12 Nov 2024 17:35:36 -0500 List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: And now the dumb question du jour Content-Language: en-CA To: riscv@freebsd.org References: <62b7409c-899a-4888-96bf-07af49c1a791@blastwave.org> From: Dennis Clarke Organization: GENUNIX In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 4ACMZaSg040700 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Spamd-Result: default: False [-4.69 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_SPF_ALLOW(-0.20)[+mx:c]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[riscv@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+]; MLMMJ_DEST(0.00)[riscv@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4Xp1TT0rcLz4VSm X-Spamd-Bar: ---- On 11/12/24 16:56, Jessica Clarke wrote: > On 12 Nov 2024, at 21:50, Dennis Clarke wrote: >> >> >> Dear RISC-V folks : >> >> Given the recent big LLVM/Clang update into the src tree[1] it >> seemed reasonable to do a full buildworld/kernel and that worked out >> very well. No LLVM hack patch required ! >> >> enceladus# uname -apKU >> FreeBSD enceladus 15.0-CURRENT FreeBSD 15.0-CURRENT #1 main-n273541-cdd3234186b1: Tue Nov 12 08:49:15 GMT 2024 root@enceladus:/usr/obj/usr/src/riscv.riscv64/sys/SIFIVE-COMPAT11 riscv riscv64 1500026 1500026 >> >> enceladus# cc --version >> FreeBSD clang version 19.1.3 (https://github.com/llvm/llvm-project.git llvmorg-19.1.3-0-gab51eccf88f5) >> Target: riscv64-unknown-freebsd15.0 >> Thread model: posix >> InstalledDir: /usr/bin >> Build config: +assertions >> enceladus# >> ... >> >> Am I missing something blunt force trauma obvious here? > > The RISC-V port is MACHINE=riscv MACHINE_ARCH=riscv64 (c.f. > MACHINE=arm64 MACHINE_ARCH=aarch64 or MACHINE=powerpc > MACHINE_ARCH=powerpc64), so you need to give -a riscv.riscv64 to > poudriere rather than -a riscv64 (which is shorthand for -a > riscv64.riscv64), unlike amd64 where MACHINE=MACHINE_ARCH=amd64 so the > shorthand works. Building src is smarter about inferring one from the > other rather than defaulting to them being the same, but poudriere is > not. > > Jess Ah ha ! Once again you save me from head scratching and confusion. Looking at : # grep -i 'riscv' /usr/src/Makefile.inc1 riscv64/riscv .if ${TARGET} == "riscv" That did not help me very much with the syntax that poudriere wants. # idprio 0 poudriere jail -c -j 150rv64 -a riscv.riscv64 -b -m src=/usr/src -f rv64/poudriere/jails/150rv6 4 -v main 2>&1 | tee /root/log/`dn`_create_150rv64_jail.log [00:00:00] Creating 150rv64 fs at /poudriere/jails/150rv64... done [00:00:00] Copying /usr/src to /poudriere/jails/150rv64/usr/src... done [00:04:27] Starting make buildworld with 4 jobs --- buildworld --- make[1]: "/poudriere/jails/150rv64/usr/src/Makefile.inc1" line 362: SYSTEM_COMPILER: Determined that CC=/usr/local/bin/ccache cc matches the source tree. Not bootstrapping a cross-compiler. make[1]: "/poudriere/jails/150rv64/usr/src/Makefile.inc1" line 367: SYSTEM_LINKER: Determined that LD=ld matches the source tree. Not bootstrapping a cross-linker. --- buildworld_prologue --- -------------------------------------------------------------- >>> World build started on Tue Nov 12 22:30:27 UTC 2024 -------------------------------------------------------------- --- _cleanworldtmp --- >>> Deleting stale files in build tree... . . . . and away it goes ... Thank you very much once again :) In unrelated areas I have been giving a considerable stare at the P550 but figure it is best to await folks with far more skills than I to attack that unit. https://www.sifive.com/cores/performance-p550 My guess is that it would do everything the Unmatched Rev B can do with the added SATA port there for serious convenience. The absent M2 SSD slot is a bit strange but who knows. It does have some sort of onboard managment port as well as dual ethernet and that is a real bonus. -- Dennis Clarke From nobody Fri Nov 15 23:47:21 2024 X-Original-To: freebsd-riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Xqtx50Mnhz5djqf for ; Fri, 15 Nov 2024 23:47:37 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xqtx41lZDz42B2 for ; Fri, 15 Nov 2024 23:47:36 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.221.42 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-wr1-f42.google.com with SMTP id ffacd0b85a97d-38232c6311fso234484f8f.3 for ; Fri, 15 Nov 2024 15:47:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731714453; x=1732319253; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=eIMoTUPhSlwMnDkTCKGESR0qYZXYePSbTVvgxqTGNc0=; b=RiF4tSklShIbkHGzRYzuwohEN7UAfduRs6F/jOyKUz+rJ993i0ub5zXeoTlvyyDpKj JLPSz0f8zwTnkoYhSqHt0qgvYK74tUzCh+7Xc+gDY9uMizMhXt3uhvoy8Sa/nhUrAud5 W5xLrVlxGeq225TLmXNQ28w5EnimgOqavUhxneMVl7e22iQoQhh4mGQzLSZODOHpD2VU G5K0SxBJw3qwiSHjWGO+DCY/xEmOR7IK62tyz2ms/Jv3cgOHZfhjenel1kPqjvwBjsuS Yjie8PqrzCw1OZ3u2U+eWtNCZ6S/CbYjaFQL+Ze9Lg306BGRocXhQaImvgqp0fSKgvG4 8DQA== X-Gm-Message-State: AOJu0YyN1vCsBJrzVv8iYI31Rkh4wj7M2lkALJUKwGtllOnH7/cERklj CCK0WFkmbk7USzt3BdRGRX09SdCPoIGLLLXhshGY/5V5AP5bVKhoBoSbF/xypIDD2IYi4nvX+12 rwKakVYXgH4E47k+dcISPwgE12GC20Hk0 X-Google-Smtp-Source: AGHT+IGbbmhAokwTMNfIMH1xCbxzo95kqPyitwe67RmFWlpOT2mFrKzPEWgYjRo6vzerNMuwvEvNiqn4XwZig3mWKZ0= X-Received: by 2002:a5d:47a1:0:b0:381:df72:52cd with SMTP id ffacd0b85a97d-38225a0c616mr3101031f8f.23.1731714452939; Fri, 15 Nov 2024 15:47:32 -0800 (PST) List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 From: Alan Somers Date: Fri, 15 Nov 2024 16:47:21 -0700 Message-ID: Subject: Help wanted improving Rust support for RISC-V To: freebsd-riscv@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-2.84 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.993]; NEURAL_HAM_SHORT(-0.99)[-0.986]; NEURAL_HAM_LONG(-0.96)[-0.958]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-riscv@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; FREEFALL_USER(0.00)[asomers]; MLMMJ_DEST(0.00)[freebsd-riscv@freebsd.org]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.221.42:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.221.42:from] X-Rspamd-Queue-Id: 4Xqtx41lZDz42B2 X-Spamd-Bar: -- I want to improve the state of Rust on FreeBSD in general, and RISC-V in particular. My plan is: * Assemble a corpus of crates heavy on OS stuff (like Nix and Tokio) and ensure that their tests pass on Riscv FreeBSD. * Update libc's ABI to FreeBSD 12, finally eliminating the need for COMPAT_11 on riscv to run Rust programs. * Ensure that the corpus of crates still passes their tests. * Convince the libc maintainers to use the FreeBSD 12 ABI, for riscv only. * After a full Rust release cycle (at least 6 weeks), and maybe two, if there are no reports of breakage, and if Poudriere looks good, use that as justification to raise libc's ABI for all architectures. But in order to do any of this, I need access to riscv hardware. A virtual instance at Scaleway[^1][^2] would be ideal, but I don't know if FreeBSD can run there. Has anybody tried it? Failing that, I would need to either acquire some hardware myself, or borrow access to somebody else's. Or, convince some other developer to do the work himself. But I won't be able to help very much if I don't have direct access. Can anybody on this list help me get some access? -Alan [^1]: https://labs.scaleway.com/en/em-rv1/ [^2]: https://www.phoronix.com/review/scaleway-risc-v-cloud From nobody Sat Nov 16 09:21:13 2024 X-Original-To: freebsd-riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Xr7gM4vLjz5d5GQ for ; Sat, 16 Nov 2024 09:21:35 +0000 (UTC) (envelope-from thj@freebsd.org) Received: from fout-b6-smtp.messagingengine.com (fout-b6-smtp.messagingengine.com [202.12.124.149]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xr7gM1RpLz4rGQ; Sat, 16 Nov 2024 09:21:35 +0000 (UTC) (envelope-from thj@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from phl-compute-02.internal (phl-compute-02.phl.internal [10.202.2.42]) by mailfout.stl.internal (Postfix) with ESMTP id BB71B114014D; Sat, 16 Nov 2024 04:21:33 -0500 (EST) Received: from phl-imap-07 ([10.202.2.97]) by phl-compute-02.internal (MEProxy); Sat, 16 Nov 2024 04:21:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1731748893; x=1731835293; bh=t 1x+bghOuhDWHHZT5KdM/xTxFH6nyyeEydMCtUo2u3Q=; b=VXXIhdLKb+GGYDcP6 PiJts1HAC/scgvfWEAooQI5NL7xga14TYP4CWbAU+if95eUhaKesP489LAzYM6nu 42YKZcK44DTptn4IpsgdtFd6kHn0q3DyKIitinDG9dKEiWDeIIL56NdrA/A/I8Os s3uav/xBQO/rxRaoe1/dadF3qEZ7k65dPoawafu0UARhm9Kg8W3Z2Ul9F4FHksts seJyt8UmW/n391aIkk41dI2oCg6RMM+U7Cm2EAuLn3oWUFy4313kOMBItg7BXME0 TkjQJ4uvcxwLcsJXl+nODCY3NccKBPTdcgaf13CxS9IQsCS4lRKE0b7fr4RTQ89t 93H6w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrvdeigddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenucfjughrpefoggffhffvkfgjfhfutgfgsehtqhertdertdejnecu hfhrohhmpedfvfhomhculfhonhgvshdfuceothhhjhesfhhrvggvsghsugdrohhrgheqne cuggftrfgrthhtvghrnhepveehjeffudehgeetkeeuteegtdetffffkedtveelheffledu veefieeutddutdejnecuffhomhgrihhnpegrughvvghnthhurhhishhtrdhmvgenucevlh hushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhjsehfrhgv vggsshgurdhorhhgpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprh gtphhtthhopegrshhomhgvrhhssehfrhgvvggsshgurdhorhhgpdhrtghpthhtohepfhhr vggvsghsugdqrhhishgtvhesfhhrvggvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: ib75146ab:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 61CF8BA006F; Sat, 16 Nov 2024 04:21:33 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 Date: Sat, 16 Nov 2024 09:21:13 +0000 From: "Tom Jones" To: "Alan Somers" , freebsd-riscv@freebsd.org Message-Id: In-Reply-To: References: Subject: Re: Help wanted improving Rust support for RISC-V Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:151847, ipnet:202.12.124.0/24, country:AU] X-Rspamd-Queue-Id: 4Xr7gM1RpLz4rGQ X-Spamd-Bar: ---- On Fri, Nov 15, 2024, at 23:47, Alan Somers wrote: > I want to improve the state of Rust on FreeBSD in general, and RISC-V > in particular. My plan is: > > * Assemble a corpus of crates heavy on OS stuff (like Nix and Tokio) > and ensure that their tests pass on Riscv FreeBSD. > * Update libc's ABI to FreeBSD 12, finally eliminating the need for > COMPAT_11 on riscv to run Rust programs. > * Ensure that the corpus of crates still passes their tests. > * Convince the libc maintainers to use the FreeBSD 12 ABI, for riscv o= nly. > * After a full Rust release cycle (at least 6 weeks), and maybe two, > if there are no reports of breakage, and if Poudriere looks good, use > that as justification to raise libc's ABI for all architectures. > > But in order to do any of this, I need access to riscv hardware. A > virtual instance at Scaleway[^1][^2] would be ideal, but I don't know > if FreeBSD can run there. Has anybody tried it? Failing that, I > would need to either acquire some hardware myself, or borrow access to > somebody else's. Or, convince some other developer to do the work > himself. But I won't be able to help very much if I don't have direct > access. > > Can anybody on this list help me get some access? I can=E2=80=99t help with scaleway, it sounds like an interesting choice= .=20 I have no idea of the current state of easily and affordable available h= ardware. The visonfive 2 might be a good choice, there has been a lot of= work in the year since I last tried it.=20 https://adventurist.me/posts/00315 It=E2=80=99s probably still the easiest to get hold of if a little under= whelming.=20 You don=E2=80=99t mention qemu, is there some reason you can=E2=80=99t s= tart there? - Tom From nobody Sat Nov 16 14:26:22 2024 X-Original-To: freebsd-riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XrGRJ5hbXz5dRCg for ; Sat, 16 Nov 2024 14:26:36 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f46.google.com (mail-ed1-f46.google.com [209.85.208.46]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XrGRJ3lqvz42h4; Sat, 16 Nov 2024 14:26:36 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-f46.google.com with SMTP id 4fb4d7f45d1cf-5cf92052dccso2130730a12.3; Sat, 16 Nov 2024 06:26:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731767194; x=1732371994; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=sCMJTl86PUBpsopw675SnoOeTAkKoowEzi/YR3V0tVM=; b=fpL76Mck1cNTRzX9uZop/ZWoFaz4UqfqtG33KALnbLxkIwWQoXh5usaX5wXolxu2ks TA10/f3lScSAjp7RRuuIMAsGRFJhBsoE6DvGqDniO3JXEO/SnHUlM/3NaTT6SoYuklhm cmen23K4gEbvUQZS+BenZ9Q5aPTZAgYwFtDBBFK02Et3qmsUmtY714qNwkDLP1o7EP0k 3OsyOPkTR0ZopEyMvlpromKJxLo9lP8wCstnYLivzxD5FHXSrqBBp0jtDVaUGssIDD2Z oMhz6ekiKD6lt2ei4cH1Ii4PlunuxZI6Q01jjBnIsRXjk+ri8nGXC9lnFUGk3z7R/U3S W7pQ== X-Forwarded-Encrypted: i=1; AJvYcCX6/kuqhWqzXC3s8fJYBEbi4a3JWIsETm2sGOGlR3Kpq55I8CnKNYGEURL9OlHgmlxH4YYo1qSHNMsw8qlL@freebsd.org X-Gm-Message-State: AOJu0Yw5J+VtwvQhlSFEKxBptIdjeGk12rj1pDQPriB1nM8D5or6DXnG B8mv1DtC2jpdwT+vvJCPI0yuxRBNkD7HSUNBT0i7EsWuqQn+BI5WcmXEjcR6pN8iSk280ncrjDu s/qy2bIFm/ZP5FC4sPmCLfM+6AAhj9Q== X-Google-Smtp-Source: AGHT+IE2HVGvueks5K9XCiFwNhgZBW588fVe7gF3H5njaElB5Zri8/ygtEaoUCB8lyHmpVqIeC9jl2kjhXUTEZzBgAw= X-Received: by 2002:a05:6402:5192:b0:5ce:dc8b:615c with SMTP id 4fb4d7f45d1cf-5cf8fc84c52mr5251124a12.8.1731767194014; Sat, 16 Nov 2024 06:26:34 -0800 (PST) List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Sat, 16 Nov 2024 07:26:22 -0700 Message-ID: Subject: Re: Help wanted improving Rust support for RISC-V To: Tom Jones Cc: Alan Somers , freebsd-riscv@freebsd.org Content-Type: multipart/alternative; boundary="0000000000006ee1c606270878d8" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4XrGRJ3lqvz42h4 X-Spamd-Bar: ---- --0000000000006ee1c606270878d8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Nov 16, 2024, 2:21=E2=80=AFAM Tom Jones wrote: > > > On Fri, Nov 15, 2024, at 23:47, Alan Somers wrote: > > I want to improve the state of Rust on FreeBSD in general, and RISC-V > > in particular. My plan is: > > > > * Assemble a corpus of crates heavy on OS stuff (like Nix and Tokio) > > and ensure that their tests pass on Riscv FreeBSD. > > * Update libc's ABI to FreeBSD 12, finally eliminating the need for > > COMPAT_11 on riscv to run Rust programs. > > * Ensure that the corpus of crates still passes their tests. > > * Convince the libc maintainers to use the FreeBSD 12 ABI, for riscv > only. > > * After a full Rust release cycle (at least 6 weeks), and maybe two, > > if there are no reports of breakage, and if Poudriere looks good, use > > that as justification to raise libc's ABI for all architectures. > > > > But in order to do any of this, I need access to riscv hardware. A > > virtual instance at Scaleway[^1][^2] would be ideal, but I don't know > > if FreeBSD can run there. Has anybody tried it? Failing that, I > > would need to either acquire some hardware myself, or borrow access to > > somebody else's. Or, convince some other developer to do the work > > himself. But I won't be able to help very much if I don't have direct > > access. > > > > Can anybody on this list help me get some access? > > I can=E2=80=99t help with scaleway, it sounds like an interesting choice. > > I have no idea of the current state of easily and affordable available > hardware. The visonfive 2 might be a good choice, there has been a lot of > work in the year since I last tried it. > > https://adventurist.me/posts/00315 > > It=E2=80=99s probably still the easiest to get hold of if a little underw= helming. > > You don=E2=80=99t mention qemu, is there some reason you can=E2=80=99t st= art there? > > - Tom > I haven't had good luck with using qemu-user-static to emulate armv7. > --0000000000006ee1c606270878d8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Nov 16, 2024, 2:21=E2=80=AFAM Tom Jones <thj@freebsd.org> wrote:


On Fri, Nov 15, 2024, at 23:47, Alan Somers wrote:
> I want to improve the state of Rust on FreeBSD in general, and RISC-V<= br> > in particular.=C2=A0 My plan is:
>
> * Assemble a corpus of crates heavy on OS stuff (like Nix and Tokio) > and ensure that their tests pass on Riscv FreeBSD.
> * Update libc's ABI to FreeBSD 12, finally eliminating the need fo= r
> COMPAT_11 on riscv to run Rust programs.
> * Ensure that the corpus of crates still passes their tests.
> * Convince the libc maintainers to use the FreeBSD 12 ABI, for riscv o= nly.
> * After a full Rust release cycle (at least 6 weeks), and maybe two, > if there are no reports of breakage, and if Poudriere looks good, use<= br> > that as justification to raise libc's ABI for all architectures. >
> But in order to do any of this, I need access to riscv hardware.=C2=A0= A
> virtual instance at Scaleway[^1][^2] would be ideal, but I don't k= now
> if FreeBSD can run there.=C2=A0 Has anybody tried it?=C2=A0 Failing th= at, I
> would need to either acquire some hardware myself, or borrow access to=
> somebody else's.=C2=A0 Or, convince some other developer to do the= work
> himself.=C2=A0 But I won't be able to help very much if I don'= t have direct
> access.
>
> Can anybody on this list help me get some access?

I can=E2=80=99t help with scaleway, it sounds like an interesting choice. <= br>
I have no idea of the current state of easily and affordable available hard= ware. The visonfive 2 might be a good choice, there has been a lot of work = in the year since I last tried it.

https://adventurist.me/posts/00315

It=E2=80=99s probably still the easiest to get hold of if a little underwhe= lming.

You don=E2=80=99t mention qemu, is there some reason you can=E2=80=99t star= t there?

- Tom

I haven't had good luck with using qemu-user-static to emulate arm= v7.
--0000000000006ee1c606270878d8-- From nobody Sat Nov 16 14:44:53 2024 X-Original-To: freebsd-riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XrGrX3rVXz5dRj0 for ; Sat, 16 Nov 2024 14:45:00 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "Certum Domain Validation CA SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XrGrX182cz43yp; Sat, 16 Nov 2024 14:45:00 +0000 (UTC) (envelope-from tuexen@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (unknown [IPv6:2a02:8109:1140:c3d:6da1:1cdc:926a:a22f]) (Authenticated sender: micmac) by drew.franken.de (Postfix) with ESMTPSA id 8A0E0721E281F; Sat, 16 Nov 2024 15:44:54 +0100 (CET) Content-Type: text/plain; charset=utf-8 List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\)) Subject: Re: Help wanted improving Rust support for RISC-V From: tuexen@freebsd.org In-Reply-To: Date: Sat, 16 Nov 2024 15:44:53 +0100 Cc: Tom Jones , freebsd-riscv@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0408D5F2-C44C-4000-941C-244B3BBC6C2A@freebsd.org> References: To: Alan Somers X-Mailer: Apple Mail (2.3826.200.121) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:680, ipnet:2001:638::/32, country:DE] X-Rspamd-Queue-Id: 4XrGrX182cz43yp X-Spamd-Bar: ---- > On 16. Nov 2024, at 15:26, Alan Somers wrote: >=20 >=20 >=20 > On Sat, Nov 16, 2024, 2:21=E2=80=AFAM Tom Jones = wrote: >=20 >=20 > On Fri, Nov 15, 2024, at 23:47, Alan Somers wrote: >> I want to improve the state of Rust on FreeBSD in general, and RISC-V >> in particular. My plan is: >>=20 >> * Assemble a corpus of crates heavy on OS stuff (like Nix and Tokio) >> and ensure that their tests pass on Riscv FreeBSD. >> * Update libc's ABI to FreeBSD 12, finally eliminating the need for >> COMPAT_11 on riscv to run Rust programs. >> * Ensure that the corpus of crates still passes their tests. >> * Convince the libc maintainers to use the FreeBSD 12 ABI, for riscv = only. >> * After a full Rust release cycle (at least 6 weeks), and maybe two, >> if there are no reports of breakage, and if Poudriere looks good, use >> that as justification to raise libc's ABI for all architectures. >>=20 >> But in order to do any of this, I need access to riscv hardware. A >> virtual instance at Scaleway[^1][^2] would be ideal, but I don't know >> if FreeBSD can run there. Has anybody tried it? Failing that, I >> would need to either acquire some hardware myself, or borrow access = to >> somebody else's. Or, convince some other developer to do the work >> himself. But I won't be able to help very much if I don't have = direct >> access. >>=20 >> Can anybody on this list help me get some access? >=20 > I can=E2=80=99t help with scaleway, it sounds like an interesting = choice. Hi Alan, neither can I... Depending on the resources you are willing to spend, = https://eu.mouser.com/ProductDetail/SiFive/HF105-001?qs=3DImq1NPwxi75JBw6u= lD0quQ%3D%3D might be an option. Best regards Michael >=20 > I have no idea of the current state of easily and affordable available = hardware. The visonfive 2 might be a good choice, there has been a lot = of work in the year since I last tried it.=20 >=20 > https://adventurist.me/posts/00315 >=20 > It=E2=80=99s probably still the easiest to get hold of if a little = underwhelming.=20 >=20 > You don=E2=80=99t mention qemu, is there some reason you can=E2=80=99t = start there? >=20 > - Tom >=20 > I haven't had good luck with using qemu-user-static to emulate armv7. From nobody Sat Nov 16 15:11:06 2024 X-Original-To: freebsd-riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XrHQl04qbz5dTTG for ; Sat, 16 Nov 2024 15:11:11 +0000 (UTC) (envelope-from nenos@protonmail.com) Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch [185.70.40.134]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XrHQk4xCQz47rf; Sat, 16 Nov 2024 15:11:10 +0000 (UTC) (envelope-from nenos@protonmail.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1731769868; x=1732029068; bh=t4ohlLwaL/gWkckn5CWJj6e7TpXqMj0RDBLbKY7sMtg=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=qybmQ5JhiMg83rvPRpvUhDK8iORGLmWYOoFpE3Qt97C7XGr57fWcr9UG8InrGALMb G34AdtAPp/YPcju5k79EkL38cUwkQXzQJQJgVtj5EIIiad7PS2ZeAfAyyS2jQeYN2w MLGnIBsVnwaI73r2yz0LG87fcDjfFEm/KnnY/2edL+Oyh2ICgD1qMHRhRTNd/DNxmF vF0qVO4aC5KdUGfgFwrOKS6vSs+NtgVy5DxBlP7tRCeUHLdmL8NeRc8FqoLq/ShFYi H5QdhOf2stWbLPjzja3IZJpCAOk4bx1YygfZFkTffBha1anmFkRvEpfzvwReKq2qKH lIVAh19RB7wQw== Date: Sat, 16 Nov 2024 15:11:06 +0000 To: "tuexen@freebsd.org" , "asomers@freebsd.org" From: nenos Cc: "thj@freebsd.org" , "freebsd-riscv@freebsd.org" Subject: Re: Help wanted improving Rust support for RISC-V Message-ID: In-Reply-To: <0408D5F2-C44C-4000-941C-244B3BBC6C2A@freebsd.org> References: <0408D5F2-C44C-4000-941C-244B3BBC6C2A@freebsd.org> Feedback-ID: 8468933:user:proton X-Pm-Message-ID: 217d84ed248281ef5624456666dd05c3185f28f3 List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH] X-Rspamd-Queue-Id: 4XrHQk4xCQz47rf X-Spamd-Bar: ---- I can loan you my VisionFive 2 SBC for an extended period if that would hel= p. Just send me a good mailing address, and I can ship it on Monday. -Nate -------- Original Message -------- On 11/16/24 9:44 AM, wrote: > > On 16. Nov 2024, at 15:26, Alan Somers wrote: > > > > > > > > On Sat, Nov 16, 2024, 2:21=E2=80=AFAM Tom Jones wrot= e: > > > > > > On Fri, Nov 15, 2024, at 23:47, Alan Somers wrote: > >> I want to improve the state of Rust on FreeBSD in general, and RISC-V > >> in particular. My plan is: > >> > >> * Assemble a corpus of crates heavy on OS stuff (like Nix and Tokio) > >> and ensure that their tests pass on Riscv FreeBSD. > >> * Update libc's ABI to FreeBSD 12, finally eliminating the need for > >> COMPAT_11 on riscv to run Rust programs. > >> * Ensure that the corpus of crates still passes their tests. > >> * Convince the libc maintainers to use the FreeBSD 12 ABI, for riscv = only. > >> * After a full Rust release cycle (at least 6 weeks), and maybe two, > >> if there are no reports of breakage, and if Poudriere looks good, use > >> that as justification to raise libc's ABI for all architectures. > >> > >> But in order to do any of this, I need access to riscv hardware. A > >> virtual instance at Scaleway[^1][^2] would be ideal, but I don't know > >> if FreeBSD can run there. Has anybody tried it? Failing that, I > >> would need to either acquire some hardware myself, or borrow access t= o > >> somebody else's. Or, convince some other developer to do the work > >> himself. But I won't be able to help very much if I don't have direc= t > >> access. > >> > >> Can anybody on this list help me get some access? > > > > I can=E2=80=99t help with scaleway, it sounds like an interesting choi= ce. > Hi Alan, > neither can I... Depending on the resources you are willing to spend, > https://eu.mouser.com/ProductDetail/SiFive/HF105-001?qs=3DImq1NPwxi75JBw= 6ulD0quQ%3D%3D > might be an option. > =20 > Best regards > Michael > > > > I have no idea of the current state of easily and affordable available= hardware. The visonfive 2 might be a good choice, there has been a lot of = work in the year since I last tried it. > > > > https://adventurist.me/posts/00315 > > > > It=E2=80=99s probably still the easiest to get hold of if a little und= erwhelming. > > > > You don=E2=80=99t mention qemu, is there some reason you can=E2=80= =99t start there? > > > > - Tom > > > > I haven't had good luck with using qemu-user-static to emulate armv7. > =20 > =20 > From nobody Sat Nov 16 18:49:37 2024 X-Original-To: freebsd-riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XrNH33ggDz5dgnS for ; Sat, 16 Nov 2024 18:49:51 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f52.google.com (mail-ed1-f52.google.com [209.85.208.52]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XrNH31cgqz4Y98; Sat, 16 Nov 2024 18:49:51 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-f52.google.com with SMTP id 4fb4d7f45d1cf-5cfbaf3d88dso56859a12.3; Sat, 16 Nov 2024 10:49:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731782989; x=1732387789; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=WV9IKvMxX+JOgfcQd92of50hUthXSuJyxOhqlbt89hA=; b=w5MfpNC9UaA62nv8Fw8hFmfsPiUMNg2WxPYqJaMDsLQe5crELv/G6Xoo+cLlJFNMOf YjIBD8nk4HUjhR6r8vZtxImQTORt+VPWydgQJKRpPbR6aUFDdviaEUPrS5rY26B/c/8I u6PdPEK6bVlX4XqnUub8lJPwX49ohjiPXFhC26XQo9vzRfHsFHw4paMxh5zNwrk7lByz D+Q42LMg/jQ40qpbzD+xE5Jfm6PaXw9QBKUHM3TsBitTeE/ucDgi8kGxBpnMBY87p0+I bR+QNESfMddIPd5tMms4HMW2/K9sFCh3K33ZIRELss3WCMo75m/8GaDhCeaQq6XaEwBE x0Jg== X-Forwarded-Encrypted: i=1; AJvYcCVSHgr0dGSKfP7QJflzFJwuVCysI6QN4RhiaRoq6k2DEoHnogol608CaWthVcfLHE2Fa40DMrqUf8+23Rd5@freebsd.org, AJvYcCXg3Frd8YpyQJwjnX831WzUx0aIqKvwkaO2k9z5kIaVw1iVKEWvFdm82N1mwGlf0q7skyjv@freebsd.org X-Gm-Message-State: AOJu0Yw1RfAiIoaf5xQb25cZ6n+zqTs0m/+QO9GX7DFXlb9LAOXHaY5M O5c1BSOGoSmHFfNw3mpuDm+D2APFnb/4M2zn7Si53FRMu4UypYKvsNX65KDMfVbBKdgRiMopGul ynaSnw5amVhUU+snNcROTazIRnMtdiw== X-Google-Smtp-Source: AGHT+IEim4mBsS4L7gf1kUKCPY0fCCcxC+f3tQBefO0E6693vQvDit0q7ynmu8M1OIUknVjXPxGftsuYx5+m2GV3ij8= X-Received: by 2002:a05:6402:13c4:b0:5cf:14fa:d24d with SMTP id 4fb4d7f45d1cf-5cf8fd2c8b2mr8753522a12.22.1731782989129; Sat, 16 Nov 2024 10:49:49 -0800 (PST) List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 References: <0408D5F2-C44C-4000-941C-244B3BBC6C2A@freebsd.org> In-Reply-To: From: Alan Somers Date: Sat, 16 Nov 2024 11:49:37 -0700 Message-ID: Subject: Re: Help wanted improving Rust support for RISC-V To: nenos Cc: "tuexen@freebsd.org" , "thj@freebsd.org" , "freebsd-riscv@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4XrNH31cgqz4Y98 X-Spamd-Bar: ---- That's a very generous offer, and I'll take you up on it if I can't find an option that doesn't involve moving actual stuff around the planet. I'm trying QEMU right now, but it's painfully slow. And I've inquired with Scaleway too. -Alan On Sat, Nov 16, 2024 at 8:11=E2=80=AFAM nenos wrote: > > I can loan you my VisionFive 2 SBC for an extended period if that would h= elp. Just send me a good mailing address, and I can ship it on Monday. > > -Nate > > > -------- Original Message -------- > On 11/16/24 9:44 AM, wrote: > > > > On 16. Nov 2024, at 15:26, Alan Somers wrote: > > > > > > > > > > > > On Sat, Nov 16, 2024, 2:21=E2=80=AFAM Tom Jones wr= ote: > > > > > > > > > On Fri, Nov 15, 2024, at 23:47, Alan Somers wrote: > > >> I want to improve the state of Rust on FreeBSD in general, and RISC= -V > > >> in particular. My plan is: > > >> > > >> * Assemble a corpus of crates heavy on OS stuff (like Nix and Tokio= ) > > >> and ensure that their tests pass on Riscv FreeBSD. > > >> * Update libc's ABI to FreeBSD 12, finally eliminating the need for > > >> COMPAT_11 on riscv to run Rust programs. > > >> * Ensure that the corpus of crates still passes their tests. > > >> * Convince the libc maintainers to use the FreeBSD 12 ABI, for risc= v only. > > >> * After a full Rust release cycle (at least 6 weeks), and maybe two= , > > >> if there are no reports of breakage, and if Poudriere looks good, u= se > > >> that as justification to raise libc's ABI for all architectures. > > >> > > >> But in order to do any of this, I need access to riscv hardware. A > > >> virtual instance at Scaleway[^1][^2] would be ideal, but I don't kn= ow > > >> if FreeBSD can run there. Has anybody tried it? Failing that, I > > >> would need to either acquire some hardware myself, or borrow access= to > > >> somebody else's. Or, convince some other developer to do the work > > >> himself. But I won't be able to help very much if I don't have dir= ect > > >> access. > > >> > > >> Can anybody on this list help me get some access? > > > > > > I can=E2=80=99t help with scaleway, it sounds like an interesting ch= oice. > > Hi Alan, > > neither can I... Depending on the resources you are willing to spend, > > https://eu.mouser.com/ProductDetail/SiFive/HF105-001?qs=3DImq1NPwxi75J= Bw6ulD0quQ%3D%3D > > might be an option. > > > > Best regards > > Michael > > > > > > I have no idea of the current state of easily and affordable availab= le hardware. The visonfive 2 might be a good choice, there has been a lot o= f work in the year since I last tried it. > > > > > > https://adventurist.me/posts/00315 > > > > > > It=E2=80=99s probably still the easiest to get hold of if a little u= nderwhelming. > > > > > > You don=E2=80=99t mention qemu, is there some reason you can=E2=80= =99t start there? > > > > > > - Tom > > > > > > I haven't had good luck with using qemu-user-static to emulate armv7= . > > > > > > From nobody Sun Nov 17 11:00:03 2024 X-Original-To: riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Xrnpf38D3z5djkd for ; Sun, 17 Nov 2024 11:00:10 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mail.oetec.com", Issuer "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xrnpd5lWLz47gr for ; Sun, 17 Nov 2024 11:00:09 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b="B76kVrG/"; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org; dmarc=pass (policy=quarantine) header.from=blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 4AHB03BE072658 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Sun, 17 Nov 2024 06:00:05 -0500 (EST) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1731841205; bh=7lIQ8dRYVUHZAImwmAnvKTGR69jBGPWi6vGg6JSgn2s=; h=Date:Subject:To:References:From:In-Reply-To; b=B76kVrG/ij6L1rjSVMz96CRt2rMq9ldEnVt0z8P9/r/jS3sisdynyAKH0kEpaJ0Uv NV+F2ldtnTgmNxFhR8XPwGa63ip0JgBMQzXDdHnSkinQh9XpSLgzondVBuM8oY0JZx oYDJ4DL8KAppWidLo0y9ojkTEP51IvnUvMqGTtQph3WqXirYVPovuszaEGoRUZpEE8 Z+iZA0umeChGZDxQDHbgbF+1L+bqFJOXD+X43SwvJVL4JFmM+8mD3oP2I9+9gBios2 P+JrFqMyCrlDao4hA/8rIuyGlkrhWw1UE6rA7t8iKmt0hfpZ26iud9xsGQKY6Lf6Tf BRXiTM+rEq/wA== Message-ID: Date: Sun, 17 Nov 2024 06:00:03 -0500 List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Help wanted improving Rust support for RISC-V Content-Language: en-CA To: riscv@freebsd.org References: <0408D5F2-C44C-4000-941C-244B3BBC6C2A@freebsd.org> From: Dennis Clarke Organization: GENUNIX In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 4AHB03BE072658 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Spamd-Result: default: False [-4.59 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.90)[-0.905]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[riscv@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+]; MLMMJ_DEST(0.00)[riscv@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4Xrnpd5lWLz47gr X-Spamd-Bar: ---- On 11/16/24 13:49, Alan Somers wrote: > That's a very generous offer, and I'll take you up on it if I can't > find an option that doesn't involve moving actual stuff around the > planet. I'm trying QEMU right now, but it's painfully slow. And I've > inquired with Scaleway too. Slow ? I emailed you off list to help here however this is reasonably safe to share on list : I have the SiFive UnMatched Rev B running and neatly nailed to a wall complete with a nice blue led to indicate disk/storage activity : SiFive UnMatched RevB can slowly flash a blue led. https://youtu.be/vdk-eBMw1uo Serial console access is via a neat little ASUS motherboard that does nothing much. https://www.genunix.com/dclarke/three_machines_m.png I am sure we can figure something out or await the SiFive P550 units. Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken