Been learning RISC-V Assembly lang the past two weeks. It's been equally the most enlightening and frustrating learning so far on this journey. I love that it's forcing me to check my understanding of so many concepts! But dang... it's really tricky making sure you didn't forget something!

Still not quite sure about how to actually use the Stack, but working through this little calculator program should help.

I get it now why some people say C is a high level language.

#assembly #riscv

Linus Torvalds says RISC-V will make the same mistakes as Arm and x86 | Tom's Hardware https://www.tomshardware.com/tech-industry/linus-torvalds-says-risc-v-will-make-the-same-mistakes-as-arm-and-x86

#linux #riscv

Check out the latest Trip Report from the recent BSDCan 2024, contributed by Mitchell Horne, covering the dev summit, his experience presenting an update on FreeBSD’s support for the RISC-V CPU architecture, and the conference itself.
#riscv #softwaredevelopment #FreeBSD
https://freebsdfoundation.org/blog/bsdcan-2024-trip-report-mitchell-horne/

Hooray! I was gifted a SiFive Unleashed for my research lab, and wasted no time porting #dlang to OpenBSD/riscv64 by way of GDC:

/home/brian $ uname -a
OpenBSD riscv64.cs.rpi.edu 7.5 GENERIC.MP#26 riscv64
/home/brian $ egdc --version
egdc (GCC) 11.2.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

#OpenBSD #riscv #riscv64 #unix #gcc #compiler #compilers #d #linux #bsd #freebsd #netbsd #dragonflybsd

👋 I’m looking to sponsor work via RISE (https://riseproject.dev) to improve the software ecosystem on #riscv . Sponsoring can come as the usual machines resources and knowledge, but also paying for contributions to relevant projects! If you know anyone or have ideas of you own, please reach out! Some efforts we’re already contributing to: https://wiki.riseproject.dev/display/HOME/RISE+RFP

@MHS_Jenkins
Main laptop: #LinuxMint
Old T430: #NetBSD
#VisionFive2 : irradium (a CRUX Linux derivative for #riscv )
#raspberrypi3 runs openSUSE Tumbleweed
#raspberrypi5 runs Raspberry Pi OS (debian)
Pine A64 also runs #NetBSD like my T430

"All RISC-V does is specify what software should expect of a RISC-V processor – it is up to processor designers to decide how exactly they implement that specification. RISC-V is open and royalty free to use, but the chips themselves can be either open source designs or closed and proprietary. The RISC-V world fears it will be broadly hit with sanctions if it can't get officials to see that distinction"

https://www.theregister.com/2024/05/29/riscv_messsaging_struggle/

#RISCV #Sanctions #OpenStandard #Opensource #China #Geopolitics

The recording of the June 13th, 2024 #bhyve Production User Call is up:

https://www.youtube.com/watch?v=-DgUGMEUW74

We discussed TPM pass-through, bhyve / #RISCV, a follow-up to read-only storage for UEFI VMs, AND HANDS-ON PACKAGED BASE BUILDING AND INSTALLATION, and more!

It was slow going but all steps to build a "packaged base" #FreeBSD system are included and are in the Agenda/Minutes doc.

"Don't forget to slam those Like and Subscribe buttons."

👩‍🏭 Meet RVPC the world lowest cost Open Source Hardware All-in-one educational RISC-V computer with VGA and PS2 keyboard which will be available for DIY soldering workshop on Open Fest in Sofia this year! - Olimex

https://olimex.wordpress.com/2024/05/15/meet-rvpc-the-world-lowest-cost-open-source-hardware-all-in-one-educational-risc-v-computer-with-vga-and-ps2-keyboard-which-will-be-available-for-diy-soldering-workshop-on-open-fest-in-sofia-this-year/

#RISCV #Opensource #OpenHardware

I created some ready-to-use container images for #RV64:
* #Debian Trixie
* #Ubuntu Jammy (22.04)
* Ubuntu Mantic (23.10)
* Ubuntu Noble (24.04)
* #Fedora 39

https://gyptazy.ch/misc/riscv-container-images-for-podman-docker/

#riscv64 #rv #risc #docker #podman #images #containerreg #registry #userland

Ooh, #FreeBSD #riscv #bhyve support is starting to take shape
https://reviews.freebsd.org/D45553

I already provide ready to use binaries for some systems:

#FreeBSD 14: https://cdn.gyptazy.ch/files/riscv64/freebsd/snac/
#Debian 12: https://cdn.gyptazy.ch/files/riscv64/debian/snac/
#Ubuntu 23.10: https://cdn.gyptazy.ch/files/riscv64/ubuntu/snac/

(Also works on Ubuntu 24.04).

@BrideOfLinux I am a big fan of the #RISCV movement. However it is worth asking whether one would go and contribute if this were in Russia or North Korea. The PRC is an active ally of these states and their actions, supporting them in word and deed, and could be treated the same way. It is staggering to me that we do this now.

Red Hat is hiring a kernel engineer for RISC-V enablement and support. This will be highly Fedora-focused work.

https://redhat.wd5.myworkdayjobs.com/en-US/jobs/job/Software-Engineer---RISC-V-Hardware-Enablement_R-038565

Note that the job is out of the Waterford, Ireland office.

PS: if seriously interested, and if we're at least acquainted, contact me _before_ applying and I'll send you a referral link!

#fedora #risc_v #riscv #job #redhat #ireland

Ruslan is working on #FreeBSD #bhyve for #RISCV

#Pixilica company now wants to develop a graphics unit for #SoCs whose instruction set is called RISC-V - RV64X and uses the vector instruction set already specified in RISC-V. RV64X is intended to support graphics and 3D calculations as well as compute and media processing.

A frame buffer, a texture unit and much more that we know from other GPU designs are planned. A built-in µCode SRAM in the design developed by Pixilica is 8K. There is also a 32 kB L1 cache. The Quad Vector ALUs can handle 32 bits per ALU in the form of FP32 and INT8 data.
RV64X RISC-V GPU design
RV64X RISC-V GPU design

The design is chosen so that custom pipeline stages, custom geometry, pixel and frame buffer stages as well as custom tessellators and custom instancing operations can be implemented. First you just want to address the Vulkan API. DirectX and OpenGL will follow later.

Not only do you want to be particularly flexible within the architecture, several RISC-V CPUs and RISC-V GPUs can also be operated together - either as a graphics microcontroller to enable a RISC-V SoC to provide simple graphical output, for example, or in multiple execution as a kind of shader design. In terms of performance, it is currently difficult to estimate where we will be with the first implementation of an RV64X design. But we are certainly talking about purely rudimentary output options as a first step.

The development is still at a fairly early stage. While RISC-V cores are increasingly being used, mostly hidden, in everyday IT, it will still be some time before more end customers come into direct contact with them. The same probably applies to the GPUs. However, an open source GPU is the logical step towards more independence in this area.
#riscv
https://www-hardwareluxx-de.translate.goog/index.php/news/hardware/grafikkarten/55310-rv64x-risc-v-gpu-befindet-sich-in-der-entwicklung.html?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en

@itsfoss see toot above for #riscv #linux distro

Se non fosse sold-out...

Milk-V Mars | The First high-performance RISC-V Single Board Computer (SBC) the size of a credit card

https://milkv.io/mars

#riscv #sbccomputing #openhardware

#BoxyBSD is testing the the public #UNIX shell service where you can get your own unix user login on different systems w/o further limitations.

Closed beta currently: boxybsd.com/shell/

This could also lead into solutions for #RISCV but still not sure how useful it might be nowadays in general.

#freebsd #openbsd #netbsd #hosting #SelfHosting #homelab

@gyptazy maybe this could be a solution for providing #RISCV on #BoxyBSD since we do not have any H-supported systems right now. But I’m not sure if there’s a huge benefit of other hw architectures when only providing jails

@ringzer0 #riscv #assembly see post above

#riscv #ubuntu #ubuntu24 for #visionfive2 is available here apparently
https://cdimage.ubuntu.com/releases/24.04/release/

@bsletten well you don't and the Chinese have been pushing the #RISCV architecture quite tremendously recently.
Why Infineon and other companies alike don't is beyond me though

Need to update Gunther at some point.
#VisionFive2 #RISCV #riscv64 #riscvsbc #raspberrypi #raspberrypi3 #raspberrypi5 #opensourcehardware #sbc #singleboardcomputer

#QEMU 9.0 Released with #RaspberryPi 4 Support, LoongArch #KVM Acceleration Support, and New #RISCV Features https://9to5linux.com/qemu-9-0-released-with-raspberry-pi-4-support-loongarch-kvm-acceleration

#Linux #OpenSource

Never worked with #ansible before and I need it for an upcoming project... so I'm using my #VisionFive2 to manage all other #SBC in my home. Even reinstalled my old #raspberrypi 3 with #openSUSE to have a different OS and system in the network xD
The way things look right now I'll have a lot of time on my hands to figure this out...
#RISCV #riscv64 #riscvsbc #ARM #Linux

FreeBSD OpenJDK Contract

Various contracts, full- and part-time:

— bhyve hypervisor kernel improvements
— desktop usability
— developer tools such as LLD
— hardware support on new ARM and RISC-V devices
— installer
— jails – usability/orchestration/OCI-compatibility
— networking
— packaging – including package base (pkgbase)
— …

<https://freebsdfoundation.org/open-positions/>

@FreeBSDFoundation

#FreeBSD #OCI #JDK #OpenJDK #ARM #RISCV #bhyve #LLD #pkgbase #orchestration #Java

@bugaevc I'll mention, but not advocate, CheriBSD <https://www.cheribsd.org/> …

#FreeBSD # Arm #Morello #CHERI #RISCV

@geerlingguy Snappy review of #sipeed #cyberd #riscv #RaspberryPi #liliputing

#amd64 offers the best support and is fast.
#arm64 is very efficient and also very fast.
#riscv is amazing & exciting (but slow with my current hw, but I can deal with it)

While amd64 & ARM64 work perfectly fine with #FreeBSD, the #RISCV hardware support (beside #qemu stuff) is still very limited. Currently, #Ubuntu and #OpenBSD work very well there.

#amd64 offers the best support and is fast.
#arm64 is very efficient and also very fast.
#riscv is amazing & exciting (but slow with my current hw, but I can deal with it)

While amd64 & ARM64 work perfectly fine with #FreeBSD, the #RISCV hardware support (beside #qemu stuff) is still very limited. Currently, #Ubuntu and #OpenBSD work very well there.

Just to give you a sense of scale, that's this board next to a fully equipped #esp32 D1 Mini, an #esp32s2 dev board and the #VisionFive2 🥹
#esp32c3 #RISCV #riscv32 #microcontroller

CC: @ex3mpted@mastodon.social @nixCraft@mastodon.social

Happy serving on #OpenBSD & #Ubuntu. Hopefully soon again back on #FreeBSD. #rv64 #risc #risc64 #riscv64

#risc #risc64 #riscv #rv64

https://gyptazy.ch/misc/starfive-visionfive2-riscv64-board-perfect-ubuntu-support-review/

https://gyptazy.ch/misc/riscv-container-images-for-podman-docker/

#docker #podman #skopeo #risc #risc64 #riscv64

- Primary Auth NS & NTP
- Secondary NS & NTP
- Webserver (#manpageblog)
- #snac (#Fediverse server) & #synapse (#Matrix chat server)
- #Tor relay node

#risc #riscv64 #risc64

gcc: internal compiler error: Segmentation fault signal terminated program cc1

Do I have encountered a hardware issue?

mmdebstrap --architectures=riscv64 --aptopt='Acquire::Check-Valid-Until "false"' --include="debian-ports-archive-keyring" sid /srv/riscv64-chroot "deb [trusted=yes] https://snapshot.debian.org/archive/debian-ports/20220616T194833Z unstable main"

cp /usr/bin/qemu-riscv64-static /srv/riscv64-chroot/usr/bin/

chroot /srv/riscv64-chroot/ qemu-riscv64-static /bin/bash

Tags:
#risc #riscv #risc64 #riscv64 #starfive #vision #packages #crosscompile #foss

mmdebstrap --architectures=riscv64 --aptopt='Acquire::Check-Valid-Until "false"' --include="debian-ports-archive-keyring" sid /srv/riscv64-chroot "deb [trusted=yes] https://snapshot.debian.org/archive/debian-ports/20220616T194833Z unstable main"

cp /usr/bin/qemu-riscv64-static /srv/riscv64-chroot/usr/bin/

chroot /srv/riscv64-chroot/ qemu-riscv64-static /bin/bash

Tags:
#risc #riscv #risc64 #riscv64 #starfive #vision #packages #crosscompile #foss

I recompiled #Debian #Bookworm (non snapshot) packages for #RISCV. Currently, there're running 7 nodes with QEMU RISC-V images and one native board. Maybe I should simply switch to experimental but I guess in the current situation many new RISCV users will stay on the bookworm snapshot's which has been used as a default by #StarFive for the #VF2 board.

#risc #riscv #riscv64 #risc64 #risc-v #visionfive #visionfive2 #hardware

I recompiled #Debian #Bookworm (non snapshot) packages for #RISCV. Currently, there're running 7 nodes with QEMU RISC-V images and one native board. Maybe I should simply switch to experimental but I guess in the current situation many new RISCV users will stay on the bookworm snapshot's which has been used as a default by #StarFive for the #VF2 board.

#risc #riscv #riscv64 #risc64 #risc-v #visionfive #visionfive2 #hardware

#onionrouting #privacy #relay #relaynode #network

So, when it comes to the #StarFive VF2 board I tried to collect some information in general as well as VF2 specific ones. We also have a #RISCV (#risc #risc64 #riscv64) Matrix chat in the #BSDCafe which you can find here:
#RISCV64:bsd.cafe

You can find more to regarding my initial ideas, reasons and information here: https://gyptazy.ch/misc/switching-from-arm64-to-open-riscv-hardware-architecture/

Some #VisionFive (#VisionFive2) specific things like benchmarks, images (collection) or precompiled software like #snac2 (Fediverse instance server), matrix-synapse (Matrix server), #unixbench etc can be found here:
https://gyptazy.ch/misc/collection-of-images-and-information-for-risc64-board-visionfive2/

Keep in mind that not all OS images may work fully and may lack drivers. For my #FreeBSD one for example you can just boot into memory. Debian runs quite well but still needs a custom kernel (do not upgrade the kernel unless you know what you’re doing). Even RISCV is tier 2 level in FreeBSD many things are missing. Pkg completely, ports is a mess. However, you may find QEMU RISCV images to cross-build stuff from your amd64 or ARM64 machine right here: https://gyptazy.ch/misc/freebsd-14-riscv64-build-box-image-for-qemu/

Here you can find a real life test where the board served for a day my whole website (based on #manpageblog) and some other ones:
https://gyptazy.ch/snac/gyptazy/p/1706078460.746773

Btw, here’s a #neofetch output:
https://gyptazy.ch/snac/gyptazy/p/1707391057.757603

Here's the #neofetch output on the #StarFive #VisionFive2 board based on #RISCV running #Debian #Linux. If you have any question, feel free to ask.

#risc #riscv64 #openhardware #opensource

Because I can! For real, it’s an awesome new platform, almost no one is using it for production (because of the limited support (especially currently from an OS perspective), knowledge and performance). However, I’m already running some boards in production, some tests I already shared with you (see also summary) and we saw that it’s easily running my workloads - so why not?

So when speaking about „why not“ my first issue is that it would force me to #Linux #Debian instead of #FreeBSD. It would be the first time since 2008 running personal Linux server instead of BSD based ones. It’s not a knowledge problem, I heavily even contribute to a Debian based distribution as a developer, it’s more an aspect of philosophy.

If you’re interested in #riscv (especially the #starfive #visionfive2 board), see also:

* Fediverse with snac: https://gyptazy.ch/snac/gyptazy/p/1706017043.921341
* Weberserver (testrun for a day): https://gyptazy.ch/snac/gyptazy/p/1706078460.746773
* More details: https://gyptazy.ch/misc/collection-of-images-and-information-for-risc64-board-visionfive2/
* Benchmarks: https://browser.geekbench.com/v6/cpu/4566123
* Docs: https://wiki.bsd.cafe/docs:riscv64
* Chat: We also have a chat for RISC related topics in the BSD cafe. Feel free to join us at: #riscv64:bsd.cafe

#risc #risc64 #riscv #riscv64 #bsdcafe

Because I can! For real, it’s an awesome new platform, almost no one is using it for production (because of the limited support (especially currently from an OS perspective), knowledge and performance). However, I’m already running some boards in production, some tests I already shared with you (see also summary) and we saw that it’s easily running my workloads - so why not?

So when speaking about „why not“ my first issue is that it would force me to #Linux #Debian instead of #FreeBSD. It would be the first time since 2008 running personal Linux server instead of BSD based ones. It’s not a knowledge problem, I heavily even contribute to a Debian based distribution as a developer, it’s more an aspect of philosophy.

If you’re interested in #riscv (especially the #starfive #visionfive2 board), see also:

* Fediverse with snac: https://gyptazy.ch/snac/gyptazy/p/1706017043.921341
* Weberserver (testrun for a day): https://gyptazy.ch/snac/gyptazy/p/1706078460.746773
* More details: https://gyptazy.ch/misc/collection-of-images-and-information-for-risc64-board-visionfive2/
* Benchmarks: https://browser.geekbench.com/v6/cpu/4566123
* Docs: https://wiki.bsd.cafe/docs:riscv64
* Chat: We also have a chat for RISC related topics in the BSD cafe. Feel free to join us at: #riscv64:bsd.cafe

#risc #risc64 #riscv #riscv64 #bsdcafe

Notes: Only ethernet and SD plugged in, Full test is running all cores on 100%. Running on latest #Linux #Debian image. Measured with Refoss Smart Plug (accuracy unknown) #risc #risc64 #riscv

Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:14:riscv64/quarterly, please wait...

pkg: Error fetching http://pkg.FreeBSD.org/FreeBSD:14:riscv64/quarterly/Latest/pkg.txz: Not Found

A pre-built version of pkg could not be found for your system.

#risc #riscv #risc64 #ports #pkg #nichearchitectures

https://gyptazy.ch/misc/collection-of-images-and-information-for-risc64-board-visionfive2/

#risc #riscv #risc64

#riscv64 #risc #riscv

Attached you can find the #Grafana metrics and the system wasn't bothered in any way... But I also need to say, that everything is running in a very optimized way with a really low footprint in all ways. Thank you all (it were more than 20 people over the whole day) for testing, stress testing and your feedback I got during the day. The next steps will result in replacing ns[01,02] and ntp[01,02] (low performance) with #RISCV (#RISC #RISC64) boards. ns[03,04] and ntp[03,04] will remain on ARM architecture until everything is running stable. Guess, you will see some more RISC64 related content soon - stay tuned!

#riscv #risc #risc-v #opensource #hardware

Board: #StarFive #VisionFive2 with 8GB RAM

My last two orders never arrived, so maybe someone can recommend something? Thanks!