[dimerr]

build-allwinner.yml now builds v3s and v851s next to v831 and v833, and smoke-tests the -nor and -mmc kind of each: two boots, and the second must load the environment the first saved.

• Order: merge after allwinner: add the V3s and V851s #72 (the SoCs) and allwinner: V3s and V851s machines; DRAM sizing and watchdog fixes qemu-bench#205 (the v3s/v851s machines the smoke legs boot on). Until then the new build and smoke legs fail.
• publish leaves out u-boot-v851s-*, in both the upload and the openipc.org report. OpenIPC/u-boot-allwinner already publishes a camera-tested u-boot-v851s-nor.bin to OpenIPC/firmware latest. With --clobber, this workflow would replace it with an image that has only run under QEMU. The V851s images are still built, smoke-tested and attached to the Allwinner release. Lift the filter once they have run on a camera.
• The README and CLAUDE.md are updated to match.

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Build and smoke-test Allwinner V3s and V851s images

✨ Enhancement ⚙️ Configuration changes 📝 Documentation 🕐 20-40 Minutes

AI Description

• Build V3s and V851s NOR and MMC images alongside V831 and V833.
• Smoke-test both boot types while keeping V851s out of firmware publishing until camera-tested.
• Document the expanded SoC support and the V851s publishing exception.

Diagram

graph TD
  R["Resolve revision"] --> B["Build four SoCs"] --> S["Smoke NOR MMC"] --> F{"V851s image?"}
  Q["QEMU machines"] --> S --> L["Allwinner release"]
  F -->|"Other SoCs"| U["Firmware latest"] --> P["openipc.org report"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Allowlist publishable SoCs

• ➕ New SoCs would not be published automatically before hardware validation.
• ➖ Every newly validated SoC would require an explicit workflow change.

Recommendation: The targeted V851s exclusion addresses the known collision with a camera-tested firmware image and keeps the upload and report consistent. An allowlist would provide a safer default for future SoCs, but adds maintenance; consider it if hardware validation becomes a standing publishing requirement. Merge the new legs only after the referenced U-Boot SoCs and QEMU machines are available.

Files changed (3) +52 / -33

Enhancement (1) +18 / -6

build-allwinner.ymlAdd V3s and V851s build and smoke legs with a V851s publish exclusion +18/-6

Add V3s and V851s build and smoke legs with a V851s publish exclusion

• Adds V3s and V851s to the build matrix and NOR/MMC QEMU smoke matrix. Keeps all images eligible for the Allwinner release, but excludes V851s binaries from both the firmware-latest upload and the openipc.org report to avoid replacing a camera-tested image.

.github/workflows/build-allwinner.yml

Documentation (2) +34 / -27

CLAUDE.mdDocument expanded Allwinner coverage and publishing policy +12/-9

Document expanded Allwinner coverage and publishing policy

• Lists the new SoCs and their QEMU machines. Explains why V851s images remain in the release but are excluded from firmware publishing until camera-tested.

CLAUDE.md

README.mdDescribe V3s and V851s images and release behavior +22/-18

Describe V3s and V851s images and release behavior

• Expands the supported-SoC list and clarifies differences in DRAM drivers and kernel hand-off. Documents the V851s camera-testing status and its exclusion from firmware-latest publishing.

README.md

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can enable the Remediation agent and Qodo fixes findings in a dedicated fix PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗