We're excited to share a preview of a Framework Laptop with a new CPU architecture today, and it's not the one you probably think it is. DeepComputing is creating the first partner-developed Mainboard, and it's powered by a RISC-V processor!
You can see the full announcement in our blog post at:
https://frame.work/blog/introducing-a-new-risc-v-mainboard-from-deepcomputing
Introducing a new RISC-V Mainboard from DeepComputing

We’re excited to share a preview of a Framework Laptop 13 Mainboard with a new CPU architecture.

Framework
DeepComputing is showing an early demo of the new RISC-V Mainboard at the RISC-V Summit in Munich next week. This board uses a StarFiveTech JH7110 with SiFive RISC-V CPU cores. DeepComputing is also working closely with the teams at Ubuntu and Fedora on Linux support.
This Mainboard drops directly into any existing Framework Laptop 13, and is aimed at enabling developers, tinkerers, and hobbyists to start testing and creating on RISC-V. In this generation, it isn't directly optimized for end-consumer usage.

@frameworkcomputer This is exciting!

I'm trying to figure out if there is a GPU or GPU equivalent on this. It looks like the JH7110 serves at least some of the purposes of a GPU?

EDIT: I am having a little trouble navigating the vendor site but a third party says the GPU is an Imagination BXE-4-32? Is this correct?

@mcc @frameworkcomputer it's the same SoC as the VisionFive 2, I think. So anything you can find about that is probably approximately correct.

The soc definitely has a GPU, but it's nothing amazing. Neither are the cpu cores for that matter.

@megmac Honestly not even interested in whether it's good, just is it there and does it conform to any particular standard
@mcc yeah there should be binary blob kms/dri drivers for Linux at the very least for it I'm pretty sure. The chipset's been out for a while and there's a bunch of more or less sketchy products built around it now.

@megmac @mcc

Binary blob as in "kernel driver is upstream in Linux, but needs to load a firmware" or "binary-only kernel module"?

The former isn't really a win for open/free software, but avoids _so many_ practical problems with the latter....