Closed Popolon closed 2 years ago
Yes, this is expected.
Currently, cpufetch does not run on RISC-V, and I do not have the intention to add support to it shortly (see #101). Maybe next summer, maybe next year... If I can get access to real hardware I will probably change my mind and add support much sooner, so if you can offer anything, I will listen :thinking:.
Closing.
OK, as it was closed I didn't found anything when searching for RISC-V, sorry.
Hi, @Dr-Noob I have the riscv64 machine by hand, please how to help here?
Sorry, I'm already busy on porting packages and systems since few month on RISC-V, which board do you use. I use mainly Sipeed Lichee-RV for these ports.
Thank your work:) Once done, I will forward this to maintainer of cpufetch Debian packages. Background: I am fixing some debian packages on riscv64 that have ftbfs: https://buildd.debian.org/status/package.php?p=cpufetch&suite=sid.
I pushed a patch for openmsx on Debian lists but don't know if it had worked?
For information, /proc/cpuinfo on LicheeRV (archlinux for RISC-V, linux-5.18rc4 with Smaeul patchs) :
processor : 0
hart : 0
isa : rv64imafdc
mmu : sv39
uarch : thead,c906
This is a Allwinner D1 (based on opensource T-Head C906 implementation) RISC-V. There is the 0.7 version specifications of the vector extension (v) on this processor, detected in /proc/cpuinfo on Debian, with kernel 5.14 including several blobby drivers patchs. This cheap SoC use 22nm technology after what I read (need to found again the source).
Great! The link has more riscv cpu info: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012077
When I try to compile on RISC-V (64 bit version) of Debian.
For information on my qemu installation of Debian, I have the following /proc/cpuinfo
rv32 means RISC-V 32 bits rv64, 64 bits and rv128 128 bits (still in draft). the letter that follow are the names of the extensions: