Note
9base status: Preserved · Lifecycle: archived reference copy.
This is a historical fork of TinkerBoard2/buildroot. 9base retains it for provenance and reference and does not actively maintain it. Upstream source and inherited authorship remain attributed to their original contributors.
This is the Buildroot component of the Tinker Board 2 Linux BSP source graph.
Its retained linux4.19-rk3399-debian10 branch contains the cross-compilation
build system and vendor platform material. The 8 October 2026 audit compared
it 0 commits ahead / 411 behind the same-named upstream branch, with no
fork-only commits exposed. Account-linked Zaryob author queries returned no
commits; this is not proof about every possible unlinked historical alias.
The upstream README, manual source, COPYING and source history remain unchanged. Historical upstream build guidance is preserved; this archive does not claim a currently tested build or continuing 9base maintenance.
| Layer | Preserved 9base repository |
|---|---|
| Linux checkout manifests | Tinkerboard2-manifest |
| Linux kernel | Tinkerboard2-kernel |
| U-Boot bootloader | Tinkerboard2-uboot |
| Buildroot build system | Tinkerboard2-buildroot |
| Debian/rootfs scripts | Tinkerboard2-debian |
| Rockchip firmware and loaders | Tinkerboard2-rkbin |
| Poky/OpenEmbedded/BitBake | yocto-poky |
| Android checkout manifests | Tinkerboard2Android-manifest |
The Linux release manifest explicitly names the kernel, U-Boot,
Buildroot, Debian, rkbin and yocto-poky components. Its remote still points to
TinkerBoard2, not these 9base forks; it does not automatically select 9base's
historical Debian fix. This family is only a retained subset of the vendor's
larger source graph, not a self-contained complete BSP checkout.
The Android manifests concern the same board family but target a separate
TinkerBoard2-Android source graph; they do not establish use of these 9base
Linux components.
These preservation notes were reconstructed on 8 October 2026 from the repository tree, exposed branches, commit history and upstream comparisons. They are new archival documentation, not evidence that this explanation existed at the historical fork date. The original reason for retention or any deployment is not established by the inspected record. No contemporary build, support or upstream synchronization commitment is implied.
The original upstream README is retained as a separate, unchanged file. Its historical content and other README variants are preserved.