Project
Yocto + QEMU EDU Lab
A hands-on lab for building Linux images and learning how drivers communicate with simulated devices on two processor architectures.
Engineering reading paths
Virtual embedded Linux
Follow QEMU device discovery into Linux drivers, Yocto images and bounded evidence.
Start here
Key idea
Compare the independent PCI and platform-device contracts in the lab. Shared build inputs do not make their peripheral interfaces interchangeable, and virtual-device results do not establish physical hardware behavior.
Curated connections
Systems
Curated connections
Engineering notes
Engineering update
Independent PCI and ARM64 learning paths
Closed lab manifests now separate x86-64 PCI MSI/INTx and bounded DMA from an ARM64 Device Tree and platform-driver path. The ARM64 peripheral has its own hardware contract and does not expose DMA.
Curated connections
Long-form writing
Article
PCI Driver vs Platform Driver: What Changes Between x86-64 and ARM64?
Compare two explicit virtual-device contracts across discovery, MMIO, interrupts and evidence without confusing CPU architecture with bus type.
Article
What a QEMU Driver Lab Can Establish
Reading the independent PCI and ARM64 lab contracts without turning virtual-device evidence into physical-hardware claims.
Curated connections
Experiments and explorers
Bounded evidence
Compare PCI and platform contracts
Source-based explorer. Explore discovery, registers, interrupts and DMA in the two documented lab compositions. No virtual or physical device runs in this explorer.
Curated connections
Evidence
System map and source
Yocto + QEMU EDU Lab: inspect the evidence
Explore the documented boundaries and pinned sources in this case study. Evidence reviewed 30 September 2026.