Maintaining the N810 changes on Linux 5.15.224¶
Kernel build and device use recorded by 3 November 2026. Reconstructed on 4 November 2026 from development and test notes.
The working RGB-console system used Linux 5.15.86. We brought the N810 changes forward to Linux 5.15.224 and built a release named 5.15.224-n810-mbx-clock-wip1. This meant preserving the board support while incorporating the stable kernel's changes.
Earlier build machinery substituted frozen source files through a compiler wrapper. The maintained branch put the RGB console, CSR Bluetooth, USB, graphics clocks, device tree, and related headers directly under source control. The compiler could then build the checked-out files, and the N810 device tree was generated from the same tree as the kernel.
Understanding the Wi-Fi merge conflict¶
The merge had one conflict, in p54spi.c, the SPI transport driver for the Intersil wireless device discussed in the Wi-Fi entry. We needed to preserve the transport changes that worked on this tablet while adopting stable's interrupt setup behavior.
An interrupt is a hardware signal asking the CPU to handle an event. A driver registers a function, called an interrupt handler, for the signal. Linux normally enables the interrupt as part of registering it. IRQF_NO_AUTOEN tells Linux to register the handler while leaving the interrupt disabled. The driver later calls enable_irq() when it is ready to handle events.
The ordering matters during initialization. Requesting an interrupt and then immediately disabling it leaves a small interval in which the handler can run. Requesting it with automatic enabling disabled removes that interval. The merge retained this stable-kernel behavior alongside our N810 transport changes.
The kernel interrupt API documents handler registration and enabling. The upstream interrupt setup implementation shows where IRQF_NO_AUTOEN controls startup. Those links let readers follow the symbol beyond this particular merge.
flowchart TB
stable["Linux 5.15.224 stable source"] --> branch["Maintained N810 branch"]
board["N810 board and console changes"] --> branch
branch --> build["Configuration + ARM cross-compiler"]
build --> image["zImage + N810 DTB"]
build --> modules["199 configured modules"]
build --> symbols["Module.symvers"]
symbols --> external["Check external MBX module interfaces"]
The image, device tree, modules, and symbol-version records come from the same build.
Checking the image and its modules¶
NOLO's image budget made size a build result we had to check. The combined kernel and appended device tree occupied 2,077,948 bytes against the 2,095,104-byte limit used by this build. That left 17,156 bytes. A change can compile successfully and still exceed the boot image's available space.
The build produced 199 configured modules. We also built the experimental MBX clock module against that same output and checked all 35 of its symbol-version records. A symbol-version checksum describes the interface a module expects from the kernel. Matching the release name helps identify a build; checking these records catches interface mismatches as well.
The initial build note ended with an unbooted candidate. The later GPU tests identify this exact release running on the physical Nokia on 3 and 4 November. Reading those records in order shows the progression from a successful build to actual device execution.
Packaging the build for another checkout¶
On 4 November, we packaged the complete maintained kernel-source delta, a reviewed configuration, the export whitelist and the external clock module alongside a portable builder. An independent local Git clone reconstructed the source from the checksum-pinned Linux archive and completed the ARM build. All 199 configured modules and 35 external-module symbol checks passed. The new image occupied 2,077,084 bytes. The verification report records the inputs and distinguishes this candidate from the earlier physical runs. The input reference links the source package to the build guide.
Keeping the other kernel experiment identifiable¶
An earlier 5.15.86-n810-rgb-sandbox1 candidate added namespaces and seccomp. Namespaces give processes separate views of resources such as process IDs and networking. Seccomp filters restrict the system calls a process can make. That candidate built with 199 modules; its physical validation was still pending in the notes.
The kernel build guide gives the source requirements, compilation commands, appended-image check, and module staging procedure. The kernel reference lists the separate releases and the tests associated with each.
Code, tests and build inputs¶
| Material | Repository files |
|---|---|
| Implementation | Maintained N810 patch (GitHub) Clock module (GitHub) |
| Checks and fixtures | Fresh-checkout result (GitHub) Source hashes (GitHub) Boot-tag regression (GitHub) |
| Build inputs | Source lock (GitHub) Kernel config (GitHub) Builder (GitHub) |