RiscV

Crossposted from https://lemmy.ml/post/21673583

RISC-V International, the global standards organization, today announced that the RVA23 Profile is now ratified. RVA Profiles align implementations of RISC-V 64-bit application processors that will run rich operating systems (OS) stacks from standard binary OS distributions. RVA Profiles are essential to software portability across many hardware implementations and help to avoid vendor lock-in. The newly ratified RVA23 Profile is a major release for the RISC-V software ecosystem and will help accelerate widespread implementation among toolchains and operating systems.

Each Profile specifies which ISA features are mandatory or optional, providing a common target for software developers. Mandatory extensions can be assumed to be present, and optional extensions can be discovered at runtime and leveraged by optimized middleware, libraries, and applications.

Key Components of RVA23 Include:

• Vector Extension: The Vector extension accelerates math-intensive workloads, including AI/ML, cryptography, and compression / decompression. Vector extensions yield better performance in mobile and computing applications with RVA23 as the baseline requirement for the Android RISC-V ABI.
• Hypervisor Extension: The Hypervisor extension will enable virtualization for enterprise workloads in both on-premises server and cloud computing applications. This will accelerate the development of RISC-V-based enterprise hardware, operating systems, and software workloads. The Hypervisor extension will also provide better security for mobile applications by separating secure and non-secure components.

cross-posted from: https://lemmy.world/post/20499594

cross-posted from: https://lemmy.world/post/20236242

cross-posted from: https://lemm.ee/post/36499892

cross-posted from: https://lemm.ee/post/36499694

Hope everyone is having a relaxing Sunday morning/evening.

I wanted to follow up from my previous post, as some of you have indicated interest.

About logistic considerations, I believe 8 weeks is a good time commitment for a hardware project. The goal is to learn more about silicon manufacturing, lower-level computer hardware details such as architecture, circuit design, fundamental condensed matter physics, and digital logic design. Other goals involve understanding firmware systems such as BIOS and the cascade of events that occur from power-on to user operation as well as conceptualizing the small timescales that these events occur on. My intention is not to dictate the philosophy of learning, but bring awareness to details that otherwise would have never been known or to draw a larger picture using the constellation of components that is a modern computing device. We then will delve into HDLs (Hardware description languages) and look specifically at the VHDL (Verilog HDL) for how to design a chip. This is where my understanding of what is out there becomes fuzzy.

We will need a repository to store documents. It is not my intention to use Google Drive. Is there a trusted platform that offers this functionality? I am also curious as to learning a VCS (Version Control System). Git seems to be the choice for this. Maintaining our codebase, resources/references, questions/comments, presentations, notes, and miscellaneous documents in some platform that does not infringe on user privacy. Any ideas in this domain?

Individual development environments are also crucial to a productive hobby/working session. I think it'd be fun to discuss IDEs, TUI environments, barebones software to accomplish simple tasks, CLI navigation, file system implementation, and drive partitioning. Some of you are adept TUI text editor users, which your expertise would be greatly appreciated.

Because this is Lemmy, I assume most of us are interested in FOSS software/hardware. Perhaps there are open source architectures for GPUs, RAM devices, and other fundamental computing units.

Is there a such thing as open source RAM architectures? Is that even the correct question to pose? I see that "OpenRAM" exists for ASIC design. Maybe we can have an ultra-specific computing task that we could optimize all the constituent hardware pieces to perform. Maybe a game engine for a programming project, but where we patchwork the pieces, or at least examine the guts of Godot together. I've found that discussing how one actually READS documentation, can be helpful in becoming more independent during information searching.

Apologies if some parts are still unclear. I'm just happy to see some of you are interested! As per the survey and what you'd like to get out of something like this, or if the idea needs other parts glued together, feel free to suggest them here. Looking forward to your feedback.

cross-posted from: https://feddit.cl/post/3171211

cross-posted from: https://feddit.cl/post/3120695

My unfunded speculation is that this will quite expensive and a bit hard to boot other thing different that Ubuntu.

Title. Just curious since apparently risc-v is mentioned as a "ultra low power draw" CPU... so I'd like to know if that is true. Thanks in advance.

RISC-V intl. announces plans to add matrix multiplication to the ISA, in an attempt to turn the architecture into a general-purpose solution for all processor derivatives eg. GPUs, TPUs, DSPs, Security Processors, Power management processors.

This isn't a rip on RISC-V but it's something I notice a lot with ARM and RISC SBCs compared to x86, which seems to support Linux, Windows, MacOS regardless of the device specs.

On other platforms, the developers have to build special iso images for each device, even though the underlying OS supports the whole architecture.

If I wanted to move to a new device (say, upgrade my Raspberry pi 4B to an Orange Pi, or other RISC-V alternatives) I'd have to ensure the new device had support from my OS choice, download a new image for it, and manually port stuff across. (as far as I can tell).

What's the technical reason that x86 can configure the OS on the fly but ARM/RISC can't?

Abstract. Formal languages are commonly used to model the seman- tics of instruction set architectures (e.g. ARM). The majority of prior work on these formal languages focuses on concrete instruction execu- tion and validation tasks. We present a novel Haskell-based modelling approach which allows the creation of flexible and versatile architecture models based on free monads and a custom expression language. Con- trary to existing work, our approach does not make any assumptions regarding the representation of memory and register values. This way, we can implement non-concrete software analysis techniques (e.g. sym- bolic execution where values are SMT expressions) on top of our model as interpreters for this model. In contrast to prior work, our modelling approach is therefore explicitly focused on the creation of custom ISA in- terpreters. We employ our outlined approach to create an abstract model and a concrete interpreter for the RISC-V base instruction set. Based on this model, we demonstrate that custom interpreters can be implemented with minimal effort using dynamic information flow tracking as a case study.