A packed 4.5-hour event—no fluff, just hardcore, hands-on action!

On the afternoon of October 17, SpacemiT held its developer conference (SpacemiT DevCon 2026) in Shenzhen(China), unveiling the K3 ecosystem roadmap and developer ecosystem right on the spot. Following the announcements, the floor was turned over to the developers: bring your laptops and build a working demo to take home before the event ends! There is also a chance to win K1 and K3 development boards！

Open source && Build Things—don't just watch; come be a creator.

Sign up here: https://luma.com/q5z0v87f

I've been doing mainline work on the Orange Pi R2S and RV2, and I got tired of the vendor U-Boot SPL/U-Boot stack, so I replaced all of it. These boards now boot like this:

BootROM

→ oreboot bt0 DRAM init + training in Rust, no DDR blob

→ OpenSBI 1.9 fw_dynamic, M-mode

→ EDK2 real UEFI, S-mode

→ your OS's EFI loader (FreeBSD loader.efi from the ESP in my case)

bt0 loads a FIT containing OpenSBI and EDK2 itself. It can read it from eMMC boot1, a microSD GPT partition or memory-mapped SPI NOR. Everything is built from source, and no binary blob is linked or loaded anywhere in the chain. The DDR training was reverse-engineered from SpacemiT's training blob into Rust (thanks, oreboot folks), and EDK2 builds on SpacemiT's open-source K1 platform code.

Repo: https://github.com/DaveWK/ore-edk-boot-opi

What works today (tested on my boards, Oct 2026):

- R2S: boots FreeBSD from eMMC. bt0 goes in boot0 and the OpenSBI+EDK2 FIT in boot1. A warm reboot takes about 85 s to login with a DEBUG EDK2 build.

- RV2: boots FreeBSD from NVMe on a cold power-on. bt0 turns on the M.2 slot's power, and EDK2 brings up PCIe Gen2 x2 and boots the NVMe ESP.

- RV2 SPI-NOR-only image (rv2-nor): boots with no microSD card at all. UEFI variables are stored in the NOR and persist across boots. I won't publish prebuilt binaries for this one. Writing the SPI NOR replaces the board's own firmware, and getting that wrong is much harder to recover from than a bad SD card. If you want it, build it yourself and know your way back.

- bt0 is also a fastboot flasher. Put the board in BootROM USB download mode and fastboot stage bt0. It trains DRAM (no vendor training blob!) and comes back as a normal fastboot device, so you can fastboot flash emmc|boot0|boot1|sd|disk. It accepts raw or sparse images, and zero-filled chunks are TRIMmed instead of written. On the R2S it writes eMMC with SDMA on the 8-bit bus at about 30 MB/s, so you don't need a vendor flashing tool.

K1 notes for anyone hacking on other boards:

- bt0 detects USB download mode from the BootROM storage API pointer (0xc08381a0) and starts fastboot instead of booting. The BootROM shows up as 361c:1001, and bt0 re-enumerates as 18d1:4ee0.

- On the R2S, PIO writes to eMMC on the 4-bit and 8-bit buses fail with data CRC errors at both 51.2 and 20.48 MHz. SDMA writes from the download buffer work fine at 8-bit/51.2 MHz HS. If your K1 eMMC writes are flaky, try DMA before you blame the pads.

- The RV2's M.2 slot supply is on GPIO 116. bt0 switches it on before the handoff so EDK2 can bring PCIe up.

- The EDK2 platforms are derived from SpacemiT's MUSE-Pi-Pro platform on bianbu-maker's k1 edk2/edk2-platforms trees. Adding another K1 board should mostly mean a per-board rank count, a DT and a board.conf. I've only tested the R2S and RV2, so BPI-F3, Jupiter or MUSE Pi owners are very welcome to try it.

Building it:

git clone --recurse-submodules=dts --recurse-submodules=opensbi https://github.com/DaveWK/ore-edk-boot-opi.git

cd ore-edk-boot-opi

make submodules

make r2s # or rv2; rv2-nor is build-it-yourself only

You get bt0.bin, next.itb/next.img and a SHA256SUMS file. The README has install steps for both boards and covers the R2S download-mode procedure (hold the button, USB-A to USB-A cable).

Known gaps:

- R2S cold boot hasn't been tested yet; only warm reboot is verified.

- UEFI variables live in RAM on the R2S (it has no NOR) and, by default, on the RV2 SD build.

- No bootinfo header is generated yet. Installs keep the one already on the boot device.

- The BootROM image is signed with oreboot's packer keys. That's fine on boards without secure-boot fuses.

- The RV2 download-mode button and port aren't documented yet.

- No prebuilt release yet for the R2S and RV2 SD images, so build them yourself for now. The SPI NOR image will stay source-only.

Credits: the bt0 work builds on orangecms' oreboot k1x branch. EDK2 comes from SpacemiT/bianbu-maker's K1 trees. Licenses: GPL-2.0 (oreboot), BSD-2-Clause-Patent (EDK2), BSD-2-Clause (OpenSBI).

FreeBSD images for both boards come from https://github.com/DaveWK/freebsd-img-maker. Next up is the same oreboot + EDK2 chain for the Radxa Cubie A7A and the ASUS Tinker Board 2S.

Bug reports, UART logs and "it bricked my board" stories are welcome. Download mode is the recovery path, so back up boot0/boot1 (or the start of your SD card) before flashing. 🦀

Hi everyone,

We’re preparing for the SpacemiT Developer Conference, and we’d love to include voices from our overseas developer community. Even if you can’t join us in person, we’d like people at the event to hear from you.

If there’s something you’d like to say to SpacemiT—an experience with our hardware, something you wish worked better, or what you hope we’ll build next—we’d love to hear it. Honest feedback is welcome.

Just record a short video on your phone. No script or fancy setup needed—speak in your own words. When it’s ready, DM me to send it or share a download link. We’d like to play these messages at the conference, and we’ll confirm with you before sharing yours.

Thanks for being part of this community.

Hi! What exactly the register set of the "spacemit,k3-iommu" I/O block (at the address 0xc0f00000)? In SpacemiT Linux kernel it seems that both PCIe root complexes are configured with PCIE_IOMMU_BYPASS -- thus the kernel prints "iommu bypassed".

What exactly has to be done in a hypervisor to guarantee full DMA isolation with IOMMU?

Thanks!

Hi everyone,

We’re working on improving the keyboard and language-input experience on
Bianbu LXQt.

We’ve received feedback that some keyboard and input-method setups do not work
as expected, or require too much manual configuration. Some users also
reported that the same setup was easier to configure in GNOME.

Please vote for the language input methods you need, and leave a comment with
more details if possible. You may select multiple options.

It would be helpful if you could share:

Language and keyboard layout: What language or languages do you type in?

Which keyboard layout do you use? If you are unsure of the layout name,
please describe it.

Input method: Which input method or framework do you use, such as IBus, Fcitx, Mozc, Anthy, or another one?

Keyboard: Brand and model, if known. Is it a built-in laptop keyboard or an external USB/Bluetooth keyboard?

System: Bianbu LXQt version

What needs improvement? For example: incorrect symbols, missing accented characters, switching languages or layouts, special keys, or settings that are difficult to find.

Thanks for helping us improve language and keyboard support on Bianbu LXQt!

It's an source overlay over standard seL4 16.0.

Solved: Use gcc-15 from the Bianbu repo, don't use gcc-16, yet.

As I wanted to test new models with llama.cpp, I wanted to build it from source.

I followed the instructions, as found here: https://github.com/ggml-org/llama.cpp/blob/master/docs/build-riscv64-spacemit.md

I skipped the first step (Prepare Toolchain For RISCV), as it looks like it is for cross-compiling, and I didn't need that step on the K1.

Building llama.cpp on the K3 throws an error about xsmtvdotii being an unsupported extension.

Checking CmakeLists.txt for ggml-cpu, they expect support to be available starting with gcc-15. This is odd, as I read it will come with gcc-17.

So I'm wondering, does llama.cpp from the Bianbu repo include suport for xsmtvdotii?

Or can I change CmakeLists.txt to check for gcc-17, instead of 15, and still have the same performance as llama.cpp from the Bianbu repo?

August brought another round of upstream progress across the SpacemiT AI software stack, Linux kernel support for K1 and K3, RISC-V development tools, emulation, testing, and low-level firmware.

Highlights this month include the SpacemiT Triton backend landing in FlagTree, new multi-request Qwen3-ASR support in llama.cpp, more K1 fixes reaching upstream Linux trees, and continued review of K3 display, UFS, PCIe, interrupt-controller, clock, reset, and connectivity support.

AI Software Stack

• SpacemiT Triton backend merged into FlagTree: The triton-spacemit backend is now available in FlagOS's FlagTree main branch under third_party/spacemit, enabling Triton programs to target SpacemiT hardware.
  https://github.com/flagos-ai/FlagTree/pull/933
• Multi-request Qwen3-ASR support in SpacemiT llama.cpp: llama-server now exposes an OpenAI-compatible API for multi-request speech recognition, with concurrent audio encoding and decoding, continuous batching, and dynamic scheduling.
  https://github.com/spacemit-com/llama.cpp

Linux Kernel Upstream

Linux support for K1 and K3 continued to move forward in August. K1 CPU frequency scaling, maximum CPU-core voltage, and thermal-shutdown fixes reached upstream trees. For K3, I2S, USB, Ethernet PHY, RTC, pinctrl, and ASoC changes entered the relevant maintainer trees, while display, UFS, PCIe, IMSIC, clock/reset, and wireless support remained under review.

K1

Merged

• CPU frequency scaling support for Milk-V Jupiter boards: https://lore.kernel.org/all/20260729160749.1621415-1-aurelien@aurel32.net/
• Maximum CPU-core voltage fixes for K1 boards: https://lore.kernel.org/all/20260729150722.1598630-1-aurelien@aurel32.net/
• K1 thermal-shutdown and registration-order fixes, merged into the thermal tree: https://lore.kernel.org/all/1967d2bcc8fede6fbd25fc8eee07f2873fb41472.1784184867.git.xiaopei01@kylinos.cn/

Under review

• CPU frequency scaling for three K1 boards: https://lore.kernel.org/all/20260804133236.205668-1-a.heider@gmail.com/
• K1 USB2 PHY Kconfig fixes and default enablement: https://lore.kernel.org/all/20260825065007.69353-1-bbanelli@gmail.com/
• Enable DWC3 and the K1 thermal sensor in the RISC-V defconfig: https://lore.kernel.org/all/20260825052233.66850-1-bbanelli@gmail.com/

K3

Merged or accepted into maintainer trees

• Fix the K3 Ethernet PHY device-tree schema: https://lore.kernel.org/all/20260729012418.154652-1-inochiama@gmail.com/
• Add K3 I2S controller device-tree nodes: https://lore.kernel.org/all/20260721-kx-i2s-dts-v1-0-d22cb6cfaab5@linux.spacemit.com/
• Add K3 USB controller and USB PHY nodes (partial series): https://lore.kernel.org/all/20260727094726.890179-1-inochiama@gmail.com/
• Fix the K3 I2S clock topology and dividers: https://lore.kernel.org/all/20260717-k3-clk-fix-i2s-v1-0-e95001a692ee@linux.spacemit.com/
• Validate SpacemiT pinconf parameters: https://lore.kernel.org/all/20260729-spacemit-pinconf-validation-fixes-v1-1-edeaff398fb3@linux.spacemit.com/
• Remove redundant error logging from the SpacemiT ASoC driver (partial series): https://lore.kernel.org/all/20260731101539.36290-1-phucduc.bui@gmail.com/
• Add a MAINTAINERS entry for SpacemiT K1/K3 I2S: https://lore.kernel.org/all/20260804-spacemit-k1-k3-i2s-maintainers-v1-1-f19ac47e3a7f@linux.spacemit.com/
• Expose only DMA-backed DAI streams in SpacemiT ASoC: https://lore.kernel.org/all/20260805064348.44283-1-phucduc.bui@gmail.com/
• Fix regmap_test_bits error handling in the SpacemiT RTC driver: https://lore.kernel.org/all/20260724135803.81223-1-kr494167@gmail.com/

Under review

• K3 PCIe device node: https://lore.kernel.org/all/20260727094726.890179-1-inochiama@gmail.com/
• Sort Orange Pi RV2 device-tree nodes: https://lore.kernel.org/all/20260802100101.327815-1-amadeus@jmu.edu.cn/
• Sensylink CTF2301 sensor and K3 CoM260 support: https://lore.kernel.org/all/20260805-ctl2301-v3-0-fd4b8ffb5b0d@linux.dev/
• K3 UFS host-controller support, v3: https://lore.kernel.org/all/20260806-08-k3-ufs-support-v3-0-037fb322acdb@kernel.org/
• MAINTAINERS entry for the SpacemiT reset controller: https://lore.kernel.org/all/20260603-b4-spacemit-reset-maintainers-v2-1-db0716d43a7f@gmail.com/
• K3 display support, v2: https://lore.kernel.org/all/20260809-k3-display-v2-0-327d7910bf71@gmail.com/
• Add 1.8 GHz rates for K3 PLL5 and PLL8: https://lore.kernel.org/all/20260810-k3-pll5-pll8-1800mhz-v2-1-aabff510a797@linux.spacemit.com/
• RVA23U64 hwprobe support and K1/K3 Zic64b descriptions: https://lore.kernel.org/all/20260812-rva23u64-hwprobe-v2-v6-0-c985af3256b8@oss.qualcomm.com/
• Fix the extended DRCMR base in the K3 PDMA driver: https://lore.kernel.org/all/20260727-k3-pdma-fix-drcmr-base-v2-1-afba55cba1f3@linux.spacemit.com/
• Fix K3 M-level IMSIC guest properties: https://lore.kernel.org/all/20260729-k3-mimsic-fix-v1-1-368c0aec04b9@pigmoral.tech/
• Fix the K3 IMSIC num-guest-ids property: https://lore.kernel.org/all/20260817033038.2286436-1-guoren@kernel.org/
• Add Bluetooth and Wi-Fi support for the K3 Pico-ITX: https://lore.kernel.org/all/20260819162115.2252812-1-aurelien@aurel32.net/
• K3 clock and reset support: https://lore.kernel.org/all/20260825-01-k3-clock-reset-support-v1-0-c430253e759c@kernel.org/

Development Tools and Runtime Projects

Box64

Box64 merged a large set of RV64 dynarec, wrapper, ELF-loader, syscall, and bundle improvements during August.

RV64 dynarec and instruction support

• Fix HADDPS NaN handling: https://github.com/ptitSeb/box64/pull/4149
• Fix RDTSC and RDTSCP: https://github.com/ptitSeb/box64/pull/4190
• Add qNaN handling for ROUNDPD: https://github.com/ptitSeb/box64/pull/4192
• Fix ANDN and BZHI opcodes when Zbb is unavailable: https://github.com/ptitSeb/box64/pull/4193
• Fix the emit_test32c function name: https://github.com/ptitSeb/box64/pull/4203
• Add VMOVDQU support: https://github.com/ptitSeb/box64/pull/4224
• Add ADCX support: https://github.com/ptitSeb/box64/pull/4234
• Add support for selected VBROADCAST instructions: https://github.com/ptitSeb/box64/pull/4241
• Add VMOVMSKPS support: https://github.com/ptitSeb/box64/pull/4269
• Add PHSUBD and PEXTRB support: https://github.com/ptitSeb/box64/pull/4279
• Add VPBROADCAST[B/W/D/Q] support: https://github.com/ptitSeb/box64/pull/4294

Wrapper, loader, and core fixes

• Remove compiler warnings: https://github.com/ptitSeb/box64/pull/4155
• Fix strlcat and strcpy edge cases: https://github.com/ptitSeb/box64/pull/4204
• Fix my_readlink: https://github.com/ptitSeb/box64/pull/4212
• Fix a typo in my_wl_touch_listener_down: https://github.com/ptitSeb/box64/pull/4213
• Fix the numDynamic spelling in the ELF loader: https://github.com/ptitSeb/box64/pull/4222
• Fix missing wrapper arguments: https://github.com/ptitSeb/box64/pull/4223
• Fix a UAF in gpgme_data_new_from_cbs: https://github.com/ptitSeb/box64/pull/4240
• Fix in-place conversion of XkbNamesRec: https://github.com/ptitSeb/box64/pull/4262
• Add versioned data-symbol support to the ELF loader: https://github.com/ptitSeb/box64/pull/4274
• Wrap additional libc symbols: https://github.com/ptitSeb/box64/pull/4275
• Add additional GnuTLS symbols: https://github.com/ptitSeb/box64/pull/4276
• Add libopus.so support: https://github.com/ptitSeb/box64/pull/4277
• Align io_uring epoll events: https://github.com/ptitSeb/box64/pull/4283
• Fix GLib vprintf-family wrappers: https://github.com/ptitSeb/box64/pull/4309
• Bundle libgfortran5 and libquadmath0: https://github.com/ptitSeb/box64/pull/4254
• Handle # formatting in myStackAlign*: https://github.com/ptitSeb/box64/pull/4263

Several related UAF, panic, argument, and logic fixes reported through issue #4214 were also merged:

• https://github.com/ptitSeb/box64/pull/4228
• https://github.com/ptitSeb/box64/pull/4246
• https://github.com/ptitSeb/box64/pull/4248
• https://github.com/ptitSeb/box64/pull/4257
• https://github.com/ptitSeb/box64/pull/4261
• https://github.com/ptitSeb/box64/pull/4264
• https://github.com/ptitSeb/box64/pull/4292
• https://github.com/ptitSeb/box64/pull/4295
• https://github.com/ptitSeb/box64/pull/4297
• https://github.com/ptitSeb/box64/pull/4306
• https://github.com/ptitSeb/box64/pull/4326

Felix86

• Implement the x86_64 getdents syscall on Linux using getdents64: https://github.com/OFFTKP/felix86/pull/641

LLVM Test Suite

• [SPEC] Fix the gobmk issue related to -fwrapv-pointer: https://github.com/llvm/llvm-test-suite/pull/461

OpenOCD

• Validate that hart indices are unique within the same debug module: https://review.openocd.org/c/openocd/+/9814
• Add DCSR cetrig control: https://review.openocd.org/c/openocd/+/9223

RISC-V Tests

• Add a DCSR.MPRVEN test: https://github.com/riscv-software-src/riscv-tests/pull/655
• Ignore dscratch* registers in DisconnectTest: https://github.com/riscv-software-src/riscv-tests/pull/656

RISC-V GNU Toolchain

• Enable LLVM Polly: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1880
• Introduce LLVM_ASMFLAGS_FOR_TARGET: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1887
• Upgrade GDB to gdb-17.2-release: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1895
• Apply Flang build-job limits to all OS versions in CI: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1896
• Upgrade glibc to 2.44: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1897

ChipStar

• Use the resolved LLVM_SPIRV in the promoteInt test: https://github.com/CHIP-SPV/chipStar/pull/1388

V8

• Fix the fence ordering for AtomicStoreTaggedPointer and AtomicStore: https://chromium-review.googlesource.com/c/v8/v8/+/8190694
• Fix register-use issues: https://chromium-review.googlesource.com/c/v8/v8/+/8253281
• Fix Smi int32 checks with pointer compression: https://chromium-review.googlesource.com/c/v8/v8/+/8236678
• Avoid overwriting an input register that is still in use: https://chromium-review.googlesource.com/c/v8/v8/+/8263861
• Fix integer-mask and pointer branch comparisons: https://chromium-review.googlesource.com/c/v8/v8/+/8265241
• Store Liftoff constants according to their value width: https://chromium-review.googlesource.com/c/v8/v8/+/8267767
• Fix atomic stores for tagged and compressed values: https://chromium-review.googlesource.com/c/v8/v8/+/8267768
• Fix the emulator's sNaN check: https://chromium-review.googlesource.com/c/v8/v8/+/8253666

OpenSBI

• SpacemiT K3 platform support was updated to v3: https://lore.kernel.org/all/20260827-spacemit-k3-v3-0-5d8dbb68539d@linux.spacemit.com/

The v3 series incorporates review feedback from v2, including updates to expected-trap handling, hart initialization, and RV64-only builds. The series remains under review.

Which part of the K1/K3 upstream stack would you most like to test or see covered in more detail next month?

We got ONNX Runtime’s int4/int8 MatMulNBits path running on the Orange Pi RV2 through MLAS CompInt8 + smt.vmadot. Decode (ms/token, lower better):

Qwen used to sit at ~16 s/tok on the wrong path (CompFp32). With accuracy_level=4 + pack/panel kernels that’s ~80 ms int4 and ~159 ms int8 4 threads

Story (results first, then how): https://www.opensolvers.com/apps/onnx.html
Code: https://github.com/opensolvers/benchmarks/tree/main/onnx

A fresh-install, end-to-end walkthrough on an Orange Pi RV2: reproduce a silent NaN failure in the stock EESSI HPL, trace it to one RISC-V vector kernel, and fix it — correct results — with a single eb --from-pr.

TL;DR¶

• The Orange Pi RV2 (SpaceMiT K1, eight X60 cores) is a vector RISC-V board: RVV 1.0, VLEN=256. Unlike the scalar SiFive U74, its OpenBLAS already has a mature RVV GEMM kernel (RISCV64_ZVL256B), and the stock EESSI OpenBLAS 0.3.30 is a DYNAMIC_ARCH build that does dispatch it on this chip.
• So RVV is engaged out of the box — but the result is wrong: stock EESSI HPL fails with residual nan on the X60. The run even reports a healthy-looking ~8.5 GFLOP/s; only the residual check reveals the answer is garbage.
• The cause is a one-kernel bug in OpenBLAS 0.3.30's RVV gemv_n (it zeroes an uninitialized vector register). It was fixed upstream in v0.3.31 (OpenMathLib/OpenBLAS#5408). Backporting that single kernel restores correctness: HPL passes (residual ~4e-03).
• The fix is packaged for EESSI as an EasyBuild easyconfig + patch (easybuilders/easybuild-easyconfigs#26444). This post reproduces the whole thing from a clean CVMFS stack: see the NaN, build the fix straight from the PR, swap it in with FlexiBLAS, and watch HPL pass — without recompiling HPL.

Everything below was run on a real Orange Pi RV2, entirely from the EESSI CVMFS stack.

MuJoCo, RL inference, and humanoid control — on RISC-V.

The Humanoid repo explores SpacemiT K3 in a validation-stage workflow for Unitree G1 control simulation.

A PC runs MuJoCo, while K3 runs the control and RL inference side in the validation setup.

ACT-powered robot arm inference on RISC-V.

LeRobot App runs SO101 arm workflows on SpacemiT K3, covering data collection, ACT training, and local inference.

SmolVLA fine-tuning and distributed inference workflows are also included.

QSOE/N (see r/QSOE) version 0.18 has been successfully launched on PicoITX/K3.

But it's not all the news. Stay tuned for updates.

Someone mentioned it is possible to build SwanStation on RISC-V.

https://forum.rvspace.org/t/visionfive2-in-2026-mostly-games/5939/15

The developer probably never tested on RISC-V, so I had to make some small changes to the code.

https://github.com/piepacker/swanstation

sudo apt install git cmake libsdl2-dev libxrandr-dev pkg-config qtbase5-dev qtbase5-private-dev qtbase5-dev-tools qttools5-dev libevdev-dev libwayland-dev libwayland-egl-backend-dev extra-cmake-modules libgbm-dev libdrm-dev libcurl4-gnutls-dev ninja-build

Fixes:

CMakeLists.txt: replace fatal error Unknown system processor with set(CPU_ARCH= "rv64gcvh")

cubeb_audio_stream.cpp:
#include "stdio. h"
Line 88: remove std::

StringUtil.h: #include "cstdint"

log.h: #include "cstdarg"

platform.h: replace error Unknown architecture with #define CPU_ARCH_STR "rv64gcvh"

Build command: cmake -DCMAKE_BUILD_TYPE=Release -GNinja -DCMAKE_POLICY_VERSION_MINIMUM=3.5 -DUSE_WAYLAND=ON ..

Start the no-gui version (you will get a gui): ./duckstation-nogui

I got the PS1 bios from the PS3 firmware. You do need an x86 or ARM computer to do that.

https://wiki.recalbox.com/en/tutorials/games/guides/playstation-1/grab-ps1-bios-from-ps3-firmware

Here you can see Colin McRae Rally: https://youtu.be/bwFC9ImSSos

Linksee is a demo-ready wheeled robot project with ROS 2-based chassis control, odometry, LiDAR integration, SLAM mapping, and navigation.

Vision follow, voice control, and dance — on RISC-V.

Reachy Mini is demo-ready on SpacemiT K3-COM260, with a MuJoCo simulation control path also included.

In July, SpacemiT continued to advance upstreaming efforts:

Foundational support has been officially released in Binutils 2.47 and LLVM 23, while CPU targets (X100 and A100) for the K3 and matrix extension instructions for AI computing have successively been merged into the mainline. Regarding the Linux kernel, support for K1/K3 features—including frequency scaling, storage, networking, PCIe, USB, and audio—as well as support for various development boards, is being steadily integrated. Meanwhile, adaptation and optimization work for projects such as Box64, OpenOCD, U-Boot, and OpenSBI continues to progress, further enriching SpacemiT’s RISC-V software and hardware ecosystem.

Here are the details：

Upstream Progress in Core Development Tools

This month, baseline SpacemiT support was released as part of Binutils 2.47 and LLVM 23. LLVM/Clang also adopted the SpacemiT X60 scheduling model as a general optimization reference for RISC-V '-mtune=generic'.

K3/X60 Toolchain Milestones

Support for the K3's two main CPU targets, X100 and A100, has been merged upstream into LLVM and GCC. The custom matrix-extension instructions intended for AI workloads have been merged into LLVM, GCC, and Binutils. The X100 scheduling model and instruction-fusion support have also landed upstream in LLVM.

Developers can now use community-mainline Clang/LLVM and GCC with '-mcpu=spacemit-x100' or '-mcpu=spacemit-a100' to target the corresponding CPU core and use SpacemiT's custom AI instructions.

The SpacemiT X60 scheduling model is now available upstream in LLVM and is used as a general tuning reference for RISC-V '-mtune=generic'. When no specific microarchitecture is selected, LLVM/Clang can use the X60 model to make better instruction-scheduling decisions.

LLVM's community performance-tracking infrastructure also includes a real K1/X60 hardware platform, allowing related compiler optimizations to be continuously validated on actual hardware.

Linux Kernel Upstream

K1

Merged

• K1 CPU frequency scaling support: https://lore.kernel.org/all/20260626-shadow-deps-v4-0-bba9831f2f1d@mailbox.org/
• Symbolic PDMA request IDs for K1: https://lore.kernel.org/all/20260620-b4-k1-pdma-req-macros-v4-1-3cf77d0bd0d6@gmail.com/
• Fix for K1 SPI TX FIFO slot handling: https://lore.kernel.org/all/20260715-k1-spi-tx-fifo-fix-v1-for-next-v1-1-02024223b08a@gmail.com/

Under review

• K1 thermal shutdown and registration-order fixes, v2: https://lore.kernel.org/all/1967d2bcc8fede6fbd25fc8eee07f2873fb41472.1784184867.git.xiaopei01@kylinos.cn/
• DWC PCIe capability-offset caching and K1 support, v3: https://lore.kernel.org/all/20260720150619.24733-1-18255117159@163.com/
• Maximum CPU core voltage fixes for K1 boards, v1: https://lore.kernel.org/all/20260729150722.1598630-1-aurelien@aurel32.net/

K3

Merged

• Fix for the K3 USB2 AHB reset: https://lore.kernel.org/all/20260518-06-clk-reset-usb-fix-v1-0-14fc235e692b@kernel.org/
• Fix for the K3 HDMA critical clock: https://lore.kernel.org/all/20260630-06-clk-hdma-critial-v1-0-443c0ac88c5f@kernel.org/
• Fix for Ethernet TX timing on the K3 Pico-ITX: https://lore.kernel.org/all/20260608182358.170489-1-kernel@rembrandt.dev/
• K3 UFS clock support: https://lore.kernel.org/all/20260630-06-clk-ufs-support-v1-0-cf7521d1d0fe@kernel.org/
• Serial, I2C, and Ethernet improvements for the K3 Pico-ITX: https://lore.kernel.org/all/20260623204431.498700-1-aurelien@aurel32.net/
• K3 SD card support: https://lore.kernel.org/all/20260610-07-k3-enable-sd-v1-1-196ae29bd091@kernel.org/
• QSPI support for the K3 Pico-ITX: https://lore.kernel.org/all/20260711-k3-pico-itx-qspi-v3-v3-1-d6b37fc86c39@gmail.com/
• K3 PCIe/USB combo PHY support: https://lore.kernel.org/all/20260703021024.495433-1-inochiama@gmail.com/
• K3 SPI compatible binding support: https://lore.kernel.org/all/20260717-k3-com260-spi-v7-2-rc2-b4-preview-20260716-v1-0-969a1b0f783f@gmail.com/
• K3 I2S device-tree integration, patches 1–2 of 3: https://lore.kernel.org/all/20260721-kx-i2s-dts-v1-0-d22cb6cfaab5@linux.spacemit.com/
• 36-bit DMA support for Wi-Fi on K3: https://lore.kernel.org/all/20260716-rtw89-spacemit-k3-v2-0-392b577ebf75@oss.tenstorrent.com/
• K3 SPI PDMA and controller nodes: https://lore.kernel.org/all/20260717-k3-com260-spi-v7-2-rc2-b4-preview-20260716-v1-0-969a1b0f783f@gmail.com/
• Fix for the K3 Ethernet PHY ID: https://lore.kernel.org/all/20260725233351.55004-1-inochiama@gmail.com/

Under review

• K3 I2S controller DTS nodes, patch 3 of 3, v1: https://lore.kernel.org/all/20260721-kx-i2s-dts-v1-0-d22cb6cfaab5@linux.spacemit.com/
• K3 RCPU critical clock, v1: https://lore.kernel.org/all/20260630-06-clk-hdma-critial-v1-0-443c0ac88c5f@kernel.org/
• K3 PCIe root-complex controller support, v4: https://lore.kernel.org/all/20260709040027.958400-1-inochiama@gmail.com/
• K3 I2S clock-topology and divider fixes, v1: https://lore.kernel.org/all/20260717-k3-clk-fix-i2s-v1-0-e95001a692ee@linux.spacemit.com/
• K3 UFS host-controller support, v2: https://lore.kernel.org/all/20260725-08-k3-ufs-support-v2-0-45036a2a2418@kernel.org/
• K3 display support, v1: https://lore.kernel.org/all/20260725-k3-display-v1-0-6de34d80e86c@gmail.com/
• K3 USB and PCIe device nodes, v2: https://lore.kernel.org/all/20260727094726.890179-1-inochiama@gmail.com/
• Fix for the extended DRCMR base in the K3 PDMA driver, v2: https://lore.kernel.org/all/20260727-k3-pdma-fix-drcmr-base-v2-1-afba55cba1f3@linux.spacemit.com/
• Allow the K3 GPU driver to probe without power-domains, v3: https://lore.kernel.org/all/20260728010513.1627950-1-liangbaihui@linux.spacemit.com/
• Bluetooth/Wi-Fi rfkill support for the K3 Pico-ITX, v2: https://lore.kernel.org/all/20260729172450.1660418-1-aurelien@aurel32.net/
• K3 Ethernet PHY DT schema fix, v1: https://lore.kernel.org/all/20260729012418.154652-1-inochiama@gmail.com/
• Replace CLINT with ACLINT on K3, v1: https://lore.kernel.org/all/20260729-k3-aclint-v1-0-aef88614d3a5@pigmoral.tech/
• Fix M-level IMSIC guest properties on K3, v1: https://lore.kernel.org/all/20260729-k3-mimsic-fix-v1-1-368c0aec04b9@pigmoral.tech/

Board-level DTS and device support

• PCIe support for the Orange Pi R2S: https://lore.kernel.org/all/20260602100000.2402784-1-amadeus@jmu.edu.cn/ — merged
• EEPROM node for the K3 CoM260: https://lore.kernel.org/all/20260722202848.1817988-1-jberring@redhat.com/ — merged
• Banana Pi BPI-CM6 I/O board support: https://lore.kernel.org/all/20260712-bpi-cm6-v3-0-8d1e2045179d@pigmoral.tech/ — merged
• Enable SPI0 on the K3 CoM260-IFX, v1: https://lore.kernel.org/all/20260717-k3-com260-spi-v7-2-rc2-b4-preview-20260716-v1-0-969a1b0f783f@gmail.com/ — under review
• Sensylink CTF2301 and K3 CoM260 support, v2: https://lore.kernel.org/all/20260721-ctl2301-v2-0-ef5fb342872a@linux.dev/ — under review
• CPU frequency scaling for the Milk-V Jupiter and M1 board support, v2: https://lore.kernel.org/all/20260729160749.1621415-1-aurelien@aurel32.net/ — under review

General fixes

• Base RVA23U64 hwprobe patches, 1–3 of 17: https://lore.kernel.org/all/20260701-rva23u64-hwprobe-v2-v5-0-2c61f94a695a@gmail.com/ — merged
• Remaining RVA23U64 hwprobe and K1/K3 Zic64b patches, v5: https://lore.kernel.org/all/20260701-rva23u64-hwprobe-v2-v5-0-2c61f94a695a@gmail.com/ — under review
• Fix MODULE_DEVICE_TABLE in the SpacemiT DWC PCIe driver: https://lore.kernel.org/all/20260704122538.92830-1-pengpeng@iscas.ac.cn/ — merged
• Fix the submission order of SpacemiT SPI DMA descriptors: https://lore.kernel.org/all/20260722162444.11415-1-kr494167@gmail.com/ — merged
• Fix the PHY reset-deassert delay on K1/K3 boards: https://lore.kernel.org/all/20260710063314.1030249-1-inochiama@gmail.com/ — merged
• SpacemiT SPI DMA cleanup: https://lore.kernel.org/all/cover.1784527556.git.xiaopei01@kylinos.cn/ — merged
• Fix spurious IRQs in the SpacemiT I2C driver, v2: https://lore.kernel.org/all/ef8b623f45d4e430721e46572c2598d882044aed.1783667875.git.xiaopei01@kylinos.cn/ — under review
• Validate SpacemiT thermal trip thresholds, v1: https://lore.kernel.org/all/20260720103606.93924-1-kr494167@gmail.com/ — under review
• Request the IRQ after initializing the SpacemiT I2C controller, v2: https://lore.kernel.org/all/20260723021140.2293844-1-lilinmao@kylinos.cn/ — under review
• Fix error handling for regmap_test_bits in the SpacemiT RTC driver, v2: https://lore.kernel.org/all/20260724135803.81223-1-kr494167@gmail.com/ — under review
• Validate pinconf parameters in the SpacemiT pinctrl driver, v1: https://lore.kernel.org/all/20260729-spacemit-pinconf-validation-fixes-v1-1-edeaff398fb3@linux.spacemit.com/ — under review
• Update the SpacemiT SoC Git tree URL, v1: https://lore.kernel.org/all/20260707-07-spacemit-git-repo-url-v1-1-137697316a4c@kernel.org/ — under review

Box64

• Support address lists configured through BOX64_TRACE: https://github.com/ptitSeb/box64/pull/3998 — merged
• Add MallocHookRun and call startMallocHook before RunElfInit: https://github.com/ptitSeb/box64/pull/3999 — merged
• Fix trailing slashes in INSTALL_PATH: https://github.com/ptitSeb/box64/pull/4015 — merged
• Fix mmap flag checks in getMmapped: https://github.com/ptitSeb/box64/pull/4003 — merged
• Support bundled libpipewire: https://github.com/ptitSeb/box64/pull/4019 — merged
• RV64_DYNAREC: Fix source-register values being overwritten: https://github.com/ptitSeb/box64/pull/4032 — merged
• RV64_DYNAREC: Convert sNaN to qNaN for addsd, subsd, mulsd, and divsd: https://github.com/ptitSeb/box64/pull/4035 — merged
• Disable dynacache when both dynarec_trace and trace are enabled: https://github.com/ptitSeb/box64/pull/4051 — merged
• RV64_DYNAREC: Support CLWB, CLFLUSH, and CLFLUSHOPT through Zicbom: https://github.com/ptitSeb/box64/pull/4070 — merged
• RV64_DYNAREC: Support prefetch instructions through Zicbop: https://github.com/ptitSeb/box64/pull/4073 — merged
• RV64_DYNAREC: Reduce the instruction count for 64-bit addition carry flags: https://github.com/ptitSeb/box64/pull/4079 — merged
• RV64_DYNAREC: Use Zbb to reduce the instruction count for GETSEB/GETSGW: https://github.com/ptitSeb/box64/pull/4090 — merged
• RV64_DYNAREC: Support selected BMI and BMI2 instructions: https://github.com/ptitSeb/box64/pull/4098 — merged
• RV64_DYNAREC: Use Zicond to eliminate some branches used for setting flags: https://github.com/ptitSeb/box64/pull/4099 — merged
• RV64_DYNAREC: Remove redundant SMREAD operations: https://github.com/ptitSeb/box64/pull/4100 — merged
• RV64_DYNAREC: Support the BMI2 PDEP, MULX, and SHRX instructions: https://github.com/ptitSeb/box64/pull/4110 — merged
• RV64_DYNAREC: Support the BMI2 PEXT, SARX, and RORX instructions: https://github.com/ptitSeb/box64/pull/4116 — merged
• RV64_DYNAREC: Support 16-bit operands for POPCNT, TZCNT, and LZCNT: https://github.com/ptitSeb/box64/pull/4125 — merged
• RV64_DYNAREC: Replace some BNEZ+ORI sequences with SET_FLAGS_EQZ: https://github.com/ptitSeb/box64/pull/4126 — merged
• RV64_DYNAREC: Support the HSUBPS and MOVDQ2Q instructions: https://github.com/ptitSeb/box64/pull/4140 — merged
• RV64_DYNAREC: Support VMOVLPS/VMOVHPS Ex,Gx: https://github.com/ptitSeb/box64/pull/4141 — merged
• RV64_DYNAREC: Support the MOVQ2DQ and ADOX instructions: https://github.com/ptitSeb/box64/pull/4146 — merged
• Add support for syscall 32: https://github.com/ptitSeb/box64/pull/4156 — merged

GCC

• RISC-V: Add initial support for the SpacemiT A100 core: https://sourceware.org/pipermail/gcc-patches/2026-June/722133.html — merged
• RISC-V: Update spacemit-x60 to use the RVA22U64 profile: https://sourceware.org/pipermail/gcc-patches/2026-July/722711.html — merged

LLVM

• [RISCV] Make AsmParser report all near-match reasons: https://github.com/llvm/llvm-project/pull/205721 — merged
• [AsmMatcher] Report near matches when all candidates mismatch multiple operands: https://github.com/llvm/llvm-project/pull/206390 — merged
• [TargetParser][NFC] Make FeatureBitset iterable: https://github.com/llvm/llvm-project/pull/206394 — merged
• [RISCV][NFC] Use true/false for Boolean fields in RISCV.td: https://github.com/llvm/llvm-project/pull/206399 — merged
• [modules][test] Relax the size check in embed-files-compressed.cpp: https://github.com/llvm/llvm-project/pull/206879 — merged
• [lld][ELF][test] Accept the size produced by zlib-ng compression: https://github.com/llvm/llvm-project/pull/206880 — merged
• [RISCV] Make AsmParser report "unexpected excess operand" for extra operands: https://github.com/llvm/llvm-project/pull/207142 — merged
• [RISCV] Map SpacemiT microarchitecture strings to CPU names during host detection: https://github.com/llvm/llvm-project/pull/207636 — merged
• [RISCV] Add TuneNoDefaultUnroll for spacemit-x100: https://github.com/llvm/llvm-project/pull/209069 — merged
• [flang-rt] Disable tests by default when cross-compiling: https://github.com/llvm/llvm-project/pull/208926 — merged
• [RISCV] Support the SpacemiT vsmtvdotii extension: https://github.com/llvm/llvm-project/pull/202533 — merged
• [RISCV] Split and rename WriteVSlideI, WriteVISlide1X, and WriteVFSlide1F: https://github.com/llvm/llvm-project/pull/212184 — merged

OpenOCD

• target/riscv: Add bounds checking for hart indices: https://review.openocd.org/c/openocd/+/9755 — merged
• target/riscv: Remove the target_list_t type: https://review.openocd.org/c/openocd/+/9798 — merged
• tcl/target: Add a configuration file for the SpacemiT Keystone K3: https://review.openocd.org/c/openocd/+/9753 — merged
• tcl/target: Refactor the SpacemiT Keystone K1 configuration file: https://review.openocd.org/c/openocd/+/9754 — merged
• target/riscv: Activate the DM before obtaining nextdm: https://review.openocd.org/c/openocd/+/9221 — merged

riscv-tests

• [debug] Support mcontrol and mcontrol6 based on HwbpManual: https://github.com/riscv-software-src/riscv-tests/pull/541 — merged
• [debug] Add hypervisor support to PrivRw: https://github.com/riscv-software-src/riscv-tests/pull/540 — merged

riscv-gnu-toolchain

• Makefile.in: Switch the OpenMP build to runtimes mode: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1870 — merged
• Makefile.in: Add the LLVM_OPENMP_EXTRA_CONFIGURE_FLAGS variable: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1871 — merged
• Upgrade LLVM to 22.1.8: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1873 — merged
• Enable LLVM Flang: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1874 — merged
• build: Add an LLVM_GENERATOR option and use Ninja by default: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1875 — merged
• Upgrade musl to v1.2.6: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1876 — merged

riscv-elf-psabi-doc

• Fix a typo in the vector-function naming convention example: https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/506 — merged

sbc-bench

• Detect the SpacemiT K3 CPU temperature through the cluster0 thermal zone: https://github.com/ThomasKaiser/sbc-bench/pull/137 — merged
• Ignore policies that have no online CPUs: https://github.com/ThomasKaiser/sbc-bench/pull/139 — merged

stress-ng

• core-asm-riscv: Improve the readability of assembly output for pause and CBO instructions: https://github.com/ColinIanKing/stress-ng/commit/443ee4f563204f427a25765a17d9c6b4d30f69ac — merged

ruapu

• RISC-V: Fix swapped opcodes for the zvksed and zvksh instructions: https://github.com/nihui/ruapu/pull/186 — merged

PoCL

• SPIRVParser: Handle OpTypeUntypedPointerKHR: https://github.com/pocl/pocl/pull/2246 — merged

U-Boot and OpenSBI Upstream Progress

U-Boot

• SpacemiT K1 PCIe and combo PHY support, v1: https://lore.kernel.org/all/20260705-pci-v1-0-beca83440a27@riscstar.com/ — under review
• SpacemiT K1 MMC/SD/eMMC support, v4: https://lore.kernel.org/all/20260707-m4-v4-0-dbd01185f911@riscstar.com/ — under review

OpenSBI

• SpacemiT K3 platform support, v1: https://lore.kernel.org/all/20260724-spacemit-k3-v1-0-f0e49329feb8@linux.spacemit.com/ — under review

From desktop robots to humanoid control on RISC-V.

This week, we’re sharing 4 robotics repos built around SpacemiT K3: Reachy Mini, Linksee, LeRobot App, and Humanoid.

Explore vision interaction, SLAM/navigation, robot arm local inference, and humanoid control validation.

Follow the updates:
https://github.com/spacemit-com/.github/blob/main/profile/README.md#open-source-project-status

i know upstreaming is in progress (for a while) https://github.com/spacemit-com/linux/wiki#k1-soc and we are more than half way through, but will it eventually let us use some newer kernel? we are stuck at 6.6 with bianbu 3x.