How tinkerboard-linux/rockchip-linux-manifest works
Project type and purpose
• From the file tree and README (“rockchip-linux-manifest” + “default.xml”), this is not a typical application codebase but a “repo” manifest repository. Its sole purpose is to drive the “repo” tool (Google’s meta-repo manager) to fetch and sync multiple Git sub-repositories needed to build Rockchip Linux (kernel, bootloader, BSP layers, rootfs, etc.).
File structure
• Top level:
• README.md – describes the manifest
• default.xml – the actual repo manifest listing all component repositories (kernel, U-Boot, BSP packages, meta-layers, etc.)
• No src/ or code directories here, because the code lives in the external repos referenced by default.xml.
README for additional insights
• The README title matches the repository name. There are no further sections, so we know this repo exists purely to orchestrate downstream checkouts via “repo init” and “repo sync.”
a. Main components
• Developer/CI host (the machine running the repo tool)
• “repo” tool itself (initializes workspace, parses default.xml)
• Git servers/remote repositories (each project referenced in default.xml)
• Local workspace (cloned project directories)
• Build system (Yocto/Buildroot or custom build scripts)
• Target Rockchip hardware (where the built images are deployed)
b. Relationships and interactions
1. Developer/CI invokes “repo init –u <this‐manifest>”
2. Repo tool reads default.xml and creates local .repo/ metadata
3. Developer/CI runs “repo sync”
4. Repo tool fetches/clones/pulls each Git project listed in default.xml from their remotes into the workspace
5. The build system processes the combined source tree to produce images (kernel, bootloader, rootfs)
6. Deployment: images are flashed onto the Rockchip target board
c. Architectural patterns / design principles
• Meta-repository pattern: a single manifest driving multiple Git repos
• Clear separation of concerns: manifest repo vs. code repos vs. build/deployment
• Idempotent initialization: “repo init” + “repo sync” always yield the exact same combined source tree
d. Relevant technologies
• “repo” tool (Python-based, from AOSP)
• Git (distributed VCS)
• Build tools (Yocto / Buildroot / custom Makefiles)
• Rockchip BSP components (u-boot, kernel, vendor drivers, meta-layers)