Files
UniXNU/docs/devices/uke-lining520ni.md
2026-11-10 14:20:18 +00:00

114 KiB

Xiaomi Pad 7 (lining520ni)

lining520ni/UniXNU-uke

Uke iPadOS27/24A446 GPU baseline CRC90B6BC701210D9DB: user confirms prior boot, icon/widget loading, Settings and Dock UI-restart symptoms resolved. No instrumented latency, long-run concurrency or repeated-cold-boot cache measurements inferred. See docs/GPU-IOS27.md.

Source record: porting.toml, 1f23c3d7e57ff81e474ddc20908986bf85bf2864.

This page is generated from the device record.

Area Status
Configuration host-verified
Firmware and boot device-verified
CPU and interrupts device-verified
Memory and DMA device-verified
Storage and root device-verified
Display device-verified
Input device-verified
GPU device-verified
Network not-applicable
Audio not-applicable
Power device-verified
Image assembly host-verified
Diagnostics device-verified

Configuration

host-verified

Components: ArmDTPlatform, ArmCpu, SoftwareAES, XnuPrelink.

Hardware and dependencies

  • Format-2 resolver of the shared UniXNU checkout (schema_version = 2).
  • UniXNU-sm7675-common SoC layer and the ipados-27.0.1-24A446 OS profile (iPad17,3, XNU 12377.121.6, arm64e).
  • 24A446 kernelcache kernelcache.decompressed (sha256 38e6d9fa...) as the prelink reference.
  • Catalog components with the board's fork pins in feeds.toml.

Configuration

  • schema_version2, sm7675 SoC, ipados-27.0.1-24A446 arm64e, uke kit and uke_ipados27_defconfig; GPU enabled.
  • Four-layer XNU patch series; current Adreno740/Metal/GOP pins are reachable on the user forks. Workspace-only paths belong in ignored local.toml.

Procedure

  • ./unixnu defconfig uke_ipados27_defconfig -D ../UniXNU-uke-build
  • ./unixnu fetch -D ../UniXNU-uke-build && ./unixnu status --json -D ../UniXNU-uke-build
  • ./unixnu build kernel -D ../UniXNU-uke-build && ./unixnu build payload -D ../UniXNU-uke-build
  • ./unixnu build userdata -D ../UniXNU-uke-build --object OS.vroot=<policy>/manifest.bin

Development findings

  • The format-1 patch path never applied the shared patches from a cold tree (the board module shadowed them); the format-2 series replays the set statelessly.
  • Catalog archive recipes equal the board's legacy builder commands; the component aliases keep the old script names working.
  • P2 (gpucomp26): the compositor's two-plane 'b3a8' frame is scanned by the DPU natively. Plane 0's 4 B/texel colour words (rows 4*width apart) are XRGB2101010, whose SSPP SRC_FORMAT 0x000276ff is the firmware's own ARGB8888 word 0x000237ff (unpack 0x03020001) with alpha bit 8 clear and DX bit 14 set, per the stock dpu_hw_sspp_setup_format/dpu_formats.c in the reference kernel; plane 1 is the alpha byte, whose row is the record's stride field. The 34,177,024-byte frame maps only its 27,340,800-byte plane-0 prefix into one slot; the CPU decode remains the fallback when the display-bank window is unavailable.
  • gpucomp26 log (recovery, userdata window, t=16..917 s): UKE DPU: direct ready fmt=000237ff/000237ff unpack=03020001 tenbit=000276ff; four b3a8 frames mapped by their plane-0 prefix (direct slot ... bytes=27340800); UKE DPU: tenbit sample p0=18060180 p0c=37edfb7e alpha=ff/ff -- the alpha plane is 0xFF, so the frame is opaque and the XRGB2101010 word order is the right one. One stall snapshot at t=78.4 s and none after; GPU commit-to-complete still averages 50.9 ms over 8884 commits in 893 s (about 9.9/s).
  • gpucomp27 ports the upstream display's refresh tick (GopFramebuffer 33e941a): startVsync/vsyncTick/armVsync, getRefreshAttributes at slot 301 and setDisplayRefreshProperties in registerService, with the builder binding _native_legacy_vsync_notify (0xfffffff005796720) and _native_legacy_set_refresh_properties (0xfffffff00579ebb8) after checking the original bytes; board.toml sets sheng-vsync=120 (armcpu-diagnostics dropped to stay at 987 of 1000 command-line bytes). The direct path now prints UKE DPU: flip n=... tb=... skip=... fb=... latch=...us max=...us vsync=... every 120 frames and the first eight UKE DPU: skip lines, so the next log separates compositor starvation from display-path loss.

Completion criteria

  • Status resolves arch, soc, os and device layers with the intended pins; the output path is out/uke/ipados-27.0.1-24A446/uke_ipados27/; kernel.macho is MH_FILESET/arm64e and prelinks against the 24A446 kernelcache.

Current limits

  • The reported interactive GPU27 symptoms are user-accepted on CRC90B6BC701210D9DB; no broad multi-client stress or cross-cold-boot cache qualification inferred.

Next action

  • Keep the accepted published pins and current GPU baseline; measure future stress/performance independently.

Evidence

Firmware and boot

device-verified

Components: DarwinBoot.

Hardware and dependencies

  • Mu-Silicium UEFI checkout (uefi-uke) with the ukePkg platform.
  • Payload FAT volume UKEESP with kernel.macho, its ADT and the trust cache.

Configuration

  • [firmware]: config uke, dsc Platforms/Xiaomi/ukePkg/uke.dsc, FD 3 MiB at FD_BASE 0xa7100000, ENABLE_SECUREBOOT=1, MEMORY_PROTECTION=TRUE.

Procedure

  • ./unixnu build firmware --skip-preflight --uefi ../uefi-uke -D ../UniXNU-uke-format2
  • fastboot boot boot.img (or flash vendor_boot+boot on the inactive slot)

Development findings

  • The boot manager displays the DT/initrd status through gUkeMemStatusGuid and the previous XNU panic line through the DXE memory driver.
  • gUkeMemStatusGuid must be declared under [Guids] in both the DEC and the library INF.
  • 2026-11-02 source review: live ABL initrd 0xB2D51000..0xB7FFF41C overlaps the former DXE Heap 0xA8000000..0xC3A00000; sheng 66421cb reserves 0xA8000000..0xB8000000. Candidate reserves the handoff before SEC/DXE and starts the heap at 0xBAB00000; built; four partitions flashed and rebooted at 2026-11-02 01:38, user photo confirms kernel fold C43F1F3EC8168A4C and six tail samples, WINDOW delta=0 and overlap=0; later MMU/kernel execution unresolved.

Completion criteria

  • The FD builds, the menu boots the payload entry, and the device reaches the XNU entry point.

Current limits

  • Paired compressed-payload boot/vendor_boot reached the user-accepted 24A446 GPU system. Other devices, suspend/resume and long repeated-boot stress are not qualified by this report.

Next action

  • Use the paired UEFI decompression-capable boot and compressed vendor_boot; preserve raw FAT fallback and runtime overlap checks.

Evidence

CPU and interrupts

device-verified

Components: ArmCpu, ArmDTPlatform, ArmVirtPlatform.

Hardware and dependencies

  • Eight Kryo cores at affinity 0..7 (SM7675 cliffs).
  • PSCI over SMC for secondary bring-up.

Configuration

  • dts/uke.dts: eight arm,cortex-a720 nodes, timebase 19200000, psci method smc.
  • Kernel arguments sheng-smp=1 armcpu-spi-ipi=1 armcpu-diagnostics=1.

Procedure

  • Build the kernel with uke-gpu-userland_defconfig and boot with the SMP arguments.

Development findings

  • Single-CPU runs are stable past t=877s; SMP died around t=117s in early runs (SMP/IPI or UFS concurrency), mitigated by the SPI-IPI path and watchdog policy.

Completion criteria

  • All eight cores enter the scheduler and the system stays up under load.

Current limits

  • Long-run SMP stability under UFS load is still being watched.

Next action

  • Keep the single-CPU fallback argument documented in the record for bisecting resets.

Evidence

Memory and DMA

device-verified

Components: RamBlock.

Hardware and dependencies

  • High DRAM window at 0x8C0000000 sized 0x240000000 (9 GiB) with the owned window at 0x130000000.
  • GMU pool 0xC8000000/32 MiB reserved in the UEFI map and adopted over IODeviceMemory::withRange.

Configuration

  • [payload.adt]: owned_memory_size 0x130000000, chip_id 207, cpu_regs 0..0x700, boot-manifest-hash pinned.
  • dts/uke.dts memory node: one contiguous range, as the ADT hand-off requires.

Procedure

  • Build the payload and read the UKE MEM counters from the menu and the kernel log.

Development findings

  • owned_memory_size, not dram_size, sizes the XNU VM; the 320 MiB ceiling was lifted by the static high-bank MemoryMapLib entries (UKE MEM ~1.11M 4K pages, free ~645 MiB).
  • A sheng-style external abort can appear at the 6 GiB top; the full 6 GiB board map is configured in board.toml.

Completion criteria

  • The kernel owns the 4.75 GiB window and jetsam no longer fires at the old ceiling.

Current limits

  • Host-only verification of the migrated ADT; the on-device counters come from the pre-migration images.

Next action

  • Re-read the UKE MEM counters after flashing the format-2 image.

Evidence

Storage and root

device-verified

Components: ShengUfs, RamBlock, VirtioMmioBlock, VirtioMmioConsole, VerifiedRoot.

Hardware and dependencies

  • UFS host at 0x1d84000 (GCC windows 0x177000/0x19e000).
  • 24A446 OS disk image: raw APFS, 9,613,344,768 B, image sha256 8a12cdad... (equals profile [root]), volume UUID 2F8E6EED-...; the VerifiedRoot OS policy verified all 2,347,008 blocks.
  • userdata SHNGROOT v2 image (9,689,890,816 B): OS window at 0x100000 (block 512, read-only) and the OS.vroot data object at 0x23D100000 (75,104,800 B, block 4096).

Configuration

  • Source storage: ShengUfs + VerifiedRoot + RamBlock + VirtioMmioBlock; the 544-byte policy header travels as kernel.macho.vroot and the hash table as the OS.vroot userdata object.
  • Kernel arguments native-source-storage=1 native-ufs-root=1; there is no unverified transport on this line.

Procedure

  • ./unixnu build kernel -D ../UniXNU-uke-build
  • ./unixnu build userdata -D ../UniXNU-uke-build --object OS.vroot=<policy>/manifest.bin

Development findings

  • The display bank's stage-1 window functions (native_ufs_dpu_map/table/l2) belong to ShengUfs; the display builder stubs only their data when the source storage is absent, so the display backend and the storage link into one kernel (the map stub is compiled only without storage).
  • The root policy hashes every 4 KiB block of the OS image: the host verification ran vr_host_block over all 2,347,008 blocks and the image sha256 equals the profile root (8a12cdad...); the 592-byte kernel.macho.vroot bundle's 544-byte manifest header is byte-identical to manifest.bin.
  • The OS member of the IPSW is an 8.25 GB AEA archive that decrypts to the raw APFS image; on Linux build userdata reuses it through a .dmg.json cache record instead of the macOS aea tool (rules 7.22).

Completion criteria

  • The kernel mounts the OS volume from the userdata window through the verified policy and bsd_init reaches launchd.

Current limits

  • Original OS/SystemOS and persistent Data were used for the accepted GPU27 system. Power-loss recovery/failure injection was not newly tested.

Next action

  • Preserve the current authenticated OS/SystemOS and immutable Data seed; do not clear userdata during GPU publication.

Evidence

Display

device-verified

Components: GopFramebuffer, NativeUfs.

Hardware and dependencies

  • UEFI GOP framebuffer; panel O82 3200x2136 with the splash at 0xe3940000/0x2b00000.
  • Overlay-present Legacy driver and the recorded mobile-graphics ABI candidates.
  • DPU track: cliffs DTB mdss_mdp@0xae00000 (sde-off 0x1000, VIG 0x5000/0x7000, CTL0 0x16000, INTF1/2 0x36000/0x37000, PP0 0x6a000, LM0 0x45000), apps_smmu 0x15000000 display streams SID 0x1c00 mask 0x02.

Configuration

  • Kernel arguments offline-legacy-* (register, gop, phase 4), offline-mobile-graphics-load=1.
  • offline-legacy-base-present=1 and offline-legacy-noconsole=1 gate the own-present path (the gpu-framepresent v2/v3 verified set); without base-present presentBase returns at its first line and the screen stays on the boot frame.
  • The GPU track arguments (sheng-gpu-power=9, sheng-gpu-metal=1, offline-mobile-graphics-client=1, sheng-gpu-pool=0, sheng-fb-gpu=0) restore the compositor's 1200-byte overlay records whose layer 6 frame the own-present path resolves.
  • The default-surface fallback is disabled so only resolved overlay surfaces present.
  • DPU track: uke-dpu=<1|2> runs the read-only live DPU snapshot (default off); uke-dpu-test=<1..4> runs the bounded controlled-pipe test (default off); uke-dpu-scanout>=1 builds the display bank's stage-1 window in NativeUfs (default off).

Procedure

  • Build the legacy display archive and boot with the offline-legacy arguments.

Development findings

  • 2026-11-03 ca-surface-track: user explicitly confirms normal upward-swipe entry without the previous freeze; CRC0485290E96ACC9B3/final988d162c/vendor150b5c06. Evidence is user report, not only flash or host checks.
  • The present chain resolved the overlay layer and put real UI on screen (white lock screen, home indicator, swipe prompt).
  • A blank after a few seconds was the blank/idle transaction falling back to the pure-black default surface; v3 presents only resolved overlay surfaces.
  • 2026-10-28 fmt2 boot: the swap path rejects every frame (UKE: swap accepted=0 reason=2 surface=0) and the screen stays on the boot console while the system runs fully in userland; identical to the 2026-10-27 session, so the patch adoption is not the cause.
  • 2026-10-28 root cause: those frozen-screen runs never set offline-legacy-base-present=1, so presentBase returned before doing anything and never logged; the accepted=0 reason=2 surface=0 line is the self-kick's pre-translation validation (the request's +2624 surface slots fill only inside the original swap_submit), not an own-present resolution failure.
  • presentBase now also honors the family's own second rule from swap_submit: a record ID equal to the default surface's ID names fb+0x1618 directly (the CPU-renderer 1288-byte records name that surface on layer 0).
  • The Data seed handoff is closed out: the scratch Data mount panic (ENOENT at kern_exec.c:8196) was a missing PackedRAMDisk/TrustCache handoff in the test payload, fixed by wiring data-seed-200/owner-data-200.dbr and the owner trust cache into unixnu.local.toml.
  • DPU archaeology: the cliffs DTS block offsets minus sde-off (0x1000) equal the DPU 9.x anchors sheng's DisplayTimingProbe uses (VIG0/1 0x4000/0x6000, CTL0 0x15000, INTF1/2 0x35000/0x36000, PP0 0x69000, LM0 0x44000); the stock DPU driver in this drop stops at DPU 7.x, so the DTB plus the live firmware snapshot are the register authority.
  • DPU surface addressing: the display streams are SID 0x1c00/0x1c02 with qcom,handoff-smrs in the cliffs apps_smmu node; the pipe address registers are 32-bit while XNU memory starts at 0x8C0000000, so scanout needs the ShengUfs display-bank stage-1 window (ported as native_ufs_dpu_map in NativeUfs).
  • P2 (gpucomp26): the compositor's two-plane 'b3a8' frame is scanned by the DPU natively. Plane 0's 4 B/texel colour words (rows 4*width apart) are XRGB2101010, whose SSPP SRC_FORMAT 0x000276ff is the firmware's own ARGB8888 word 0x000237ff (unpack 0x03020001) with alpha bit 8 clear and DX bit 14 set, per the stock dpu_hw_sspp_setup_format/dpu_formats.c in the reference kernel; plane 1 is the alpha byte, whose row is the record's stride field. The 34,177,024-byte frame maps only its 27,340,800-byte plane-0 prefix into one slot; the CPU decode remains the fallback when the display-bank window is unavailable.
  • gpucomp26 log (recovery, userdata window, t=16..917 s): UKE DPU: direct ready fmt=000237ff/000237ff unpack=03020001 tenbit=000276ff; four b3a8 frames mapped by their plane-0 prefix (direct slot ... bytes=27340800); UKE DPU: tenbit sample p0=18060180 p0c=37edfb7e alpha=ff/ff, so the alpha plane is 0xFF, the frame is opaque and the XRGB2101010 word order is the right one. One stall snapshot at t=78.4 s and none after; GPU commit-to-complete still averages 50.9 ms over 8884 commits in 893 s (about 9.9/s).
  • gpucomp27 ports the upstream display's refresh tick (GopFramebuffer 33e941a): startVsync/vsyncTick/armVsync, getRefreshAttributes at slot 301 and setDisplayRefreshProperties in registerService, with the builder binding _native_legacy_vsync_notify (0xfffffff005796720) and _native_legacy_set_refresh_properties (0xfffffff00579ebb8) after checking the original bytes; board.toml sets sheng-vsync=120 (armcpu-diagnostics dropped to stay at 987 of 1000 command-line bytes). The direct path now prints UKE DPU: flip n=... tb=... skip=... fb=... latch=...us max=...us vsync=... every 120 frames and the first eight UKE DPU: skip lines, so the next log separates compositor starvation from display-path loss.
  • gpucomp27 counters: flips ran at 10-28 fps with skip=0 and fb=0, so the display path drops nothing; the latch waits for the frame boundary (mean 4.1 ms, max 8.4 ms, one 120 Hz frame) and the flip is tear-free. The compositor commits every 85-100 ms when idle and 12-30 ms in bursts, one full-screen pass with 60 draws over 6.68 Mpx per frame, commit-to-complete 27-41 ms; the GMU perf vote is accepted (X v0/0, index 9 = 950 MHz, bandwidth 6), so the frame cost is fill work, not clock.
  • Flicker root cause found in the display code: dpuSlot rotated the four slots round-robin and could pick the slot the pipes were scanning, remapping that IOVA to a new surface while the pipe still fetched the old frame, one mixed frame per burst of new surfaces (app transitions, blur effects). gpucomp28 selects by LRU and never the shown slot (upstream directSlot rule) and records it after each flip.
  • gpucomp28 also removes the one-frame delay: CoreAnimation completes its command buffer before submitting the swap (the runtime WC row is its waitUntilCompleted, 29 calls, 738 ms), and upstream flips the submitted surface; the delay only added up to a whole frame of display latency (about 100 ms at 10 fps).
  • Open on the GPU side: SR 5 refusals of 3200x2136 surface textures (pf80 BGRA / pf554 ten-bit) with OutOfMemory(Device), and 220 GB of shadow copy-backs (J surface cache) over a 320 s run; both may add cost to the compositor path and need a separate look.
  • gpucomp29 counted 22 drained and 1298 busy flips: the GPU ring was non-empty in 98 percent of flips, so holding each frame one swap longer did not mean holding a complete one (the compositor submits before its work retires). That is why transitions and blur effects kept flickering and why the first seconds after boot flashed black.
  • gpucomp30 gives the direct path a completion fence: dpuPrepareFrame does the sleepable work (slot mapping, source format) at swap time, a work-loop timer polls native_gpu_idle (the CP ring drained) every 500 us and only then writes the registers (dpuFlipPrepared), forcing the flip after 30 ms and counting it (fence=drained/forced) so a ring that never drains cannot freeze the panel; dpuSlot now avoids both the shown and the pending slot and a newer frame replaces one still waiting.
  • The CPU levels are logged again without a new boot argument: CpuFreqProbe runs its read-only mode on the GPU track (sheng-gpu-power>=9), reports the level each EPSS domain runs at (f<MHz>, LUT[perf_state]) and logs UKE CPU: ...; the windows are 0x17d91000/0x17d92000/0x17d93000, referenced by the vendor crash-dump link lists.
  • gpucomp30 showed that CP_RB_RPTR==CP_RB_WPTR is not a completion signal (the CP has read the commands, the pixel work may still run), so that fence behaved like the unfenced gpucomp28: everything that moved flickered.
  • gpucomp31 takes the fence from the only party that knows: the plugin Metal runtime. NativeGOPWire gains NGP_DIRECT ('DIRC'), the presenter offers it when sheng-fb-gpu=1 and uke-dpu-scanout>=3, the client waits in NBWaitInFlight for every command buffer committed before the offer (exactly this frame's work, the earlyOn gate removed) and completes, and the display flips its pipes in that completion (completeDirect) with a 100 ms watchdog that drops an unanswered frame; clients without the mode are refused and the display keeps its own timing.
  • The plugin had to be rebuilt for the direct mode (CDHashes c063675e/4be6b25b/ee022a5f, owner trust regenerated, addon blob 21,178,648 bytes, 12 entries). On Linux the plugin build must not pass -fuse-ld=lld: the iOS xcrun wrapper already injects --ld-path to its ld shim, and the two together hand clang driver flags to ld64.lld.
  • gpucomp37 measured the GPU path itself: a 27 MB fill takes 14.8 ms (1.76 GB/s) and a copy 13.9 ms (3.75 GB/s), so the compositor's ~67 MB of shadow traffic per frame is about 18 ms before any rendering. The bottleneck is GPU-to-host memory throughput, not shading.
  • Upstream was fetched with its feature branches: NativeAdreno feat/ipados27-gpu-parity (14 commits, 2026-10-29 02:39) carries the work that targets this exactly - cache maintenance counted per phase with uncached imports skipped (its message: the 1.5 GiB pool took 41 ms with preemption off), no XNU contiguous search when the pool exists, BO pool growth in chunks, on-demand GPU page tables, msm hangcheck with restart. ArmSmmu4K has the matching feat branch (30ec63b, page tables on demand).
  • gpucomp38 is those branches merged: our nine A732/GMU commits rebased onto the adreno feat branch with the conflicts resolved (borrow and adopt side by side, the GMU pool adopt taking only the five payloads because page tables are on demand now, the GPU pool adopt for the five buffers, at(i) for the grown entry table, dropViews split into a locked form and a wrapper), plus a weak native_pmap_user_mappings stub and a UKE GPU: maint phase row. The SMMU kit is the feat commit; the build needs --local-module kit:ArmSmmu4K= that checkout.
  • Local toolchain fixes on the way: build-arm-driver.py dropped the recipe's -Wno-missing-designated-field-initializers and -Wno-unused-but-set-global, which made clang reject the XNU headers and then assert inside RecordLayoutBuilder (the earlier 'clang frontend command failed due to signal'); both are back, and a compile that dies by signal is retried.
  • The upstream feature branch was merged and boots: gpucomp46 (kernel 15ad83d8, payload 48967bf0) ran 918 s with conn switch=0 cp=0 mode=1 mount=0/0 shared=0 tables=10/1 in=31 out=40, o2/0/1 and fence=4892/28 (99.4 percent fenced, drops down from 11-12 percent), gpu=12.1 ms offer-to-completion. The per-process client address space works on the fused 31-bit aperture because clientWindow() places every client at 0x10000000 + 1.75 GiB (its own page tables make the same window free for all of them); createVm, setScope and the client opens then all succeed.
  • A later boot of the same image panicked with OSMetaClass::applyToInstances+0xf4 (caller OSKext::loadExecutable, pc 0xfffffff007904548, esr 0x56000004 SVC, x8 NativeLegacyDisplay::getMetaClass); the string resolves to '>maxDepth' at libkern/c++/OSMetaClass.cpp:1118, i.e. a metaclass superclass chain deeper than sDeepestClass. That is kernel data being overwritten, and it appeared only after the feature branch's per-process address spaces and on-demand page tables, intermittently (one boot 918 s clean, the next panics during kext load).
  • The gpu_qcom_scm aperture call (SVC_MP 0x0c / cmd 0x1b, ARGS(4)) succeeds for context banks 0-3 but the SMMU keeps reporting a 31-bit stage-1 input (in=31), so the upstream 2^ias model cannot be used here; the client window is what adapts instead.
  • Panic capture: the pram hand-off (uke_panic_flush) produced no UKE PANIC line and a variadic call to the kernel printf printed only the prefix (Darwin passes variadic arguments on the stack), so the panic screen now copies its text into uke_panic_shadow (exported by the probe) and the probe heartbeat prints it; the screen also mutes the console on entry and draws only the message at scale 3.
  • The revert to the bootable baseline exposed how a local build picks its driver: feeds.toml's Adreno740 commit (f1a2aee, the m9f-era tip) is documentation only for a local= source, and the build stages whatever that checkout has. gpucomp47/48 therefore built with f1a2aee and rendered on the CPU, while the image that rendered on the GPU was gpucomp37, built from uke-a732-single @ c950906 (the local A732 commits rebased onto upstream perf/gpu-smoothness). The two payloads' kernel.macho symbol tables settle it: gpucomp37 has retiredReaper, NativeAdrenoRing::kick/writeWptr, native_adreno_stall*/ring_window/wptr_fence/unstick, AGXDeviceUserClient::dropViewsLocked and NativeAdrenoHandleIndex; f1a2aee has none of them. gpucomp49 (driver c950906, plus the probe's pool_mib write before bring-up and the &#123;1,9,6&#125; initial HFI vote that the same commit had) has exactly gpucomp37's kernel size (52,281,344 B) and differs only in __LINKEDIT (216 B) and the six omitted feat telemetry symbols; user-verified on device on 2026-10-29.
  • 2026-10-30 (branch uke-b3a8-scanout, GopFramebuffer 4458e4d, image gpucomp72, built not flashed): the upstream feat display refuses the render server's two-plane frame, so the spelling joins nativeScanoutFormat with its own 5-bytes-a-texel bound (native_legacy_b3a8_bounds) instead of the 4 B/px model its pixel-unit stride can never satisfy; plane 0 is scanned through the same VIG pipes with the ten-bit source word ((firmware word & ~0x100) | 0x4000 = 0x000276ff, unpack 0x03020001) and only that plane's 27,340,800-byte prefix mapped, and native_legacy_convert_xr10 decodes it on the CPU when the pipes are not reachable. The direct path also needed the display bank window back: its argument is NativeUfs's uke-dpu-scanout, which the 2026-10-30 02:16 move to the upstream chain dropped while keeping only the display's sheng-dpu-scanout, so from gpucomp50 on every frame took the copy path; board.toml now sets both (sheng-dpu-scanout=2 uke-dpu-scanout=1) at 974 of 1000 command-line bytes, dropping offline-legacy-base-present, which only the retired NativeMobileDisplay read.

Completion criteria

  • A known frame appears with correct geometry and colors and stays up.

Current limits

  • User confirms boot, icons/widgets and Settings/Dock interactions on GPU27 CRC90B6BC701210D9DB. Historical iOS17 frame-rate/stall numbers do not describe this build. No instrumented display throughput or long-run stress inference.

Next action

  • Retain accepted upstream fence/cancellation and requested-scanout behavior; collect future timing under a separately defined workload.

Evidence

Input

device-verified

Components: ShengHidInput, ShengNovatekTouch, QcomGeniSpi.

Hardware and dependencies

  • Novatek NT36532 (o82 firmware, csot and tm variants) over Qcom Geni SPI.
  • HID delivery through the workloop (NativeHidInput runAction on the touch thread).

Configuration

  • 60x40 scan geometry; TLMM per-GPIO base 0x0f100000; poll mode frames flow after first valid frame type 4.
  • Kernel arguments offline-hid-home=1 offline-hid-input=1 offline-key-events=1.

Procedure

  • Boot with the touch diagnostics and read the UKE TCH counters.

Development findings

  • 2026-11-03 ca-surface-track: user explicitly confirms normal upward-swipe entry without the previous freeze; CRC0485290E96ACC9B3/final988d162c/vendor150b5c06. Evidence is user report, not only flash or host checks.
  • Full bring-up runs on device through stage 4: firmware download CRC-ok and scanning 60x40.
  • The v3 argument set is sheng-fb-gpu=0 plus offline-legacy-base-present=1; the desktop-era fb-gpu=1 hangs identically.

Completion criteria

  • Frames reach HID and the on-screen swipe responds.

Current limits

  • Current 27-line acceptance is user-confirmed upward swipe without freeze; duration, all-app coverage, cross-reboot stability and GPU acceleration are outside this report.
  • Split touch HID delivery and visible swipe are now user-confirmed; the former weak-stub/no-delivery limit is superseded. Multi-touch, full direction coverage and latency were not measured in this report.

Next action

  • Preserve ca-surface-track as the 27-line interactive baseline; continue other feature or longer-duration validation when requested.

Evidence

GPU

device-verified

Components: Adreno740, AdrenoMetal, AdrenoFirmware, AdrenoPM4, ArmSmmu4K, Sm7675Platform, Sm8550Platform, AirNir.

Hardware and dependencies

  • Real 0x43030b00/gen7_11_0, pinned gen71100 firmware, OEM DT and OEM gen7_11_0 source ed4ad0d1ad00.
  • Upstream main Adreno740 6fa7bae, Metal 243d63c, GOP e47c1b8; existing 24A446 OS/SystemOS and immutable Data seed.

Configuration

  • NATIVE_ADRENO enabled; per-process VM, preemption mode2, DCVS, BGRA8/SYSMEM and upstream transient GMEM policy.
  • 160 MiB raw FAT with standard UEFI compression; paired uke UEFI required.

Procedure

  • Build kernel, UEFI, Turnip ios27, Metal ios27, addon/trust and payload; pack boot/vendor_boot.
  • Only the compression round trip and required artifact/record checks; hardware tests follow delivery.

Development findings

  • Real gen7_11_0 GPU stack preserves upstream features and uses original OS resources. Turnip chained fixups avoids prior dyld stack overflow; scoped CoreImage nil-result library retry is present.
  • On CRC90B6BC701210D9DB the user confirms all previously reported boot/icon/widget/Settings/Dock UI-restart symptoms resolved. Device result, not just flash transport.

Completion criteria

  • Real Metal rendering/presentation and unlock work on uke 24A446.
  • Concurrent clients, CP preemption, teardown and persistent warm shader cache work on hardware.

Current limits

  • Acceptance is the user's direct report on the exact flashed image; no fresh post-fix logs or instrumented frame-time figures were collected this turn.
  • Long-run multi-client stress and cache reuse across repeated cold boots remain independently unmeasured.

Next action

  • Current accepted GPU27 baseline CRC90B6BC701210D9DB is published to the seven user-fork mains; divergent old mains saved as documented. No remaining reported icon/widget/Settings/Dock blocker. Future frame-time, multi-client stress and repeated cold-boot cache measurements are separate work.

Evidence

Network

not-applicable

Hardware and dependencies

  • The board has no network driver in this port.

Configuration

  • No network component is selected; the kernel runs with IF_HEADLESS.

Procedure

  • Nothing to run.

Development findings

  • The port boots and tests over serial and the local display only.

Completion criteria

  • Out of scope: no network bring-up is planned for the first boot target.

Current limits

  • Wi-Fi and Bluetooth are not in scope; the catalog lists Ath12kWifi for boards that need it.

Next action

  • Revisit if userland networking becomes a goal.

Evidence

Collect evidence using the next action.

Audio

not-applicable

Hardware and dependencies

  • No audio codec bring-up in this port.

Configuration

  • The ADT product node keeps the audio routing properties of the OS identity only.

Procedure

  • Nothing to run.

Development findings

  • Audio is carried by the OS identity properties; no board codec work has started.

Completion criteria

  • Out of scope for the current bring-up goals.

Current limits

  • The speaker path is untested.

Next action

  • Revisit after the display and input goals.

Evidence

Collect evidence using the next action.

Power

device-verified

Components: Adreno740, AppleKeyStoreState.

Hardware and dependencies

  • PMGR power policy and the GMU voltage/clock voting over the AOSS/RPMH path.
  • Hardware watchdog policy (sheng-disable-watchdogd=1) and the gh_virt_wdt pet.

Configuration

  • Kernel arguments sheng-pmgr=2 sheng-lite=1 sheng-aks=1 sheng-disable-watchdogd=1.
  • GMU core 220 MHz / hub 200 MHz with the validated vote sequence.

Procedure

  • Boot the staged power modes and read the GX/S0 heartbeat rows.

Development findings

  • Mode 8 passed: GX off/on and the perf vote acked with the heartbeat H0.. every 2 s.
  • The scm secure-watchdog path is a dead end; the gh_virt_wdt pet is accepted and disable is refused.

Completion criteria

  • GPU power states transition and the board keeps running with the watchdog policy applied.

Current limits

  • Suspend/resume is not implemented (the ADT defaults pin sleep-disabled=1).

Next action

  • Keep the watchdog policy documented; revisit sleep only after userland is stable.

Evidence

Image assembly

host-verified

Components: DarwinBoot, XnuPrelink, VerifiedRoot.

Hardware and dependencies

  • Stock vendor_boot DTB with the board's dtb_node patches (splash reservation, payload at 0x1000000).
  • Trust cache bundle and the recorded Data seed.

Configuration

  • 160MiB raw FAT, payload.compression=uefi; EDK II standard UEFI compression transport in vendor_boot. Paired uke UEFI expands into reserved0xA8000000..0xB2000000 after overlap checks.
  • Android v4 vendor_boot retains original DTB/table/bootconfig/vbmeta. Accepted boot1519616B and vendor_boot44859392B fit the96MiB partitions.

Procedure

  • ./unixnu build payload --kernel kernel.macho --unique-chip-id HEX -D ../UniXNU-uke-build
  • ./unixnu bootimg --uefi ../uefi-uke --dtb ../uke-port/data/vendor_boot.dtb --ramdisk none -D ../UniXNU-uke-build

Development findings

  • The v4 header parsing and the existing-/chosen tolerance are in unixnu bootimg (core 5525d18); the boot image carries an empty ramdisk because the payload is the vendor_boot vendor ramdisk.
  • payload, boot, vendor_boot and userdata all build on Linux; only the Data skip-setup seed still needs macOS.

Completion criteria

  • payload.img contains kernel.macho, its ADT, the trust cache, the Data seed and kernel.macho.vroot; boot.img boots from the stock DTB.

Current limits

  • Exact binary identity is the accepted release manifest and CRC90B6BC701210D9DB; later documentation/pin commits do not imply a rebuilt image.

Next action

  • Use the paired accepted images and preserved CPU rollback. Keep the original Data seed and owner trust inputs.

Evidence

Diagnostics

device-verified

Components: AppleKeyStoreState, XnuPrelink.

Hardware and dependencies

  • Embedded panic log at 0xFF800000/0x380000 read by the menu before XNU clears it.
  • Boot progress stages and the uke log ring (sheng-log=1).

Configuration

  • panic_screen true with the vendored Font.h; boot-progress=2 for the stage bars.
  • UKE MEM counters (gUkeMemStatusGuid) and the previous panic line on the menu.

Procedure

  • Boot with boot-progress=2 and read the menu status, then the kernel log.

Development findings

  • The panic screen, ramoops print and the last-panic line work; the jetsam OOM vs corpse messages are distinguished in the log.
  • The migration's own diagnostics: from-scratch kernel builds and the ADT baseline diff run on the host.

Completion criteria

  • Failures leave a readable panic line on screen and in the log.

Current limits

  • Fresh UKELLOG1 and sameboot Data reports were recovered for prior failing27 builds. Current success is direct user feedback; post-fix fault counters were not recaptured this publication turn.

Next action

  • Keep bounded client/recovery reasons available for any new failure; high-cost frame/pixel capture remains disabled.

Evidence