Kernel tree exists only as an uncommitted working tree on ouranos #4
Labels
No labels
blocked-physical
cleanup
hardware
infra
kernel
P1-critical
P2-high
P3-normal
P4-later
reliability
security
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tiagoagueda/a80#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
uname -ris7.2.0-g45c13f3f9e3b-dirty, built from~/a80/linuxon ouranos, which hasno commits. Modified there:
arch/arm/mach-sunxi/mc_smp.c— A15 v-f tables, rail enable, domain isolation, NEON resetordering, and the
cpu_tablefix (an upstream bug)drivers/soc/sunxi/sunxi_arisc.c+include/linux/soc/sunxi/arisc.h— ~330 lines thatexist nowhere else; the AR100 beacon handshake was expensive to work out and is undocumented
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c— the MDIO settle pollarch/arm/boot/dts/allwinner/sun9i-a80.dtsiand the board DTSdrivers/phy/allwinner/phy-sun50i-usb3.c,drivers/thermal/sun8i_thermal.c, clk and cpufreqglue
If that host's disk dies, this board becomes unreproducible and every fix — DRAM sizing, USB3,
the real pin map, the MDIO settle — is gone. This is the only risk in the tracker that is
genuinely irreversible.
Done when
patches/Done 2026-08-28. Both working trees are committed on
draco-aw80branches on ouranos, and exported intopatches/as ten series split along maintainer boundaries.The AR100 driver was the irreplaceable part. Verified after export by reconstructing the file from the patch and comparing against the original:
Bases: linux
45c13f3f9e3b, u-boot964ad5b5c91b(v2026.10-rc3).patches/configs/holds savedefconfig output for both, so a build is reproducible without the original.config.Not fully closed by this, deliberately: the trees on ouranos are committed but still live only on that host. The patches here are a faithful export, but an export is not the tree with its history. Pushing those branches to a remote of their own would close the loop.
Nothing has been submitted upstream.