Files
UniXNU/docs/devices/marble.md
2026-10-27 17:50:34 +00:00

27 KiB

Redmi Note 12 Turbo / POCO F5 (marble)

sing0626/UniXNU-marble

Community legacy XNU 8796 source port for Marble. A historical temporary boot reached iOS Hello, but touch/setup remain incomplete; no matching upstream Format-2 profile/feed or Format-2 device build is claimed.

Source record: porting.toml, a63260314d130ebf02a987f0785f5ae3258c219c.

This page is generated from the device record.

Area Status
Configuration planned
Firmware and boot planned
CPU and interrupts planned
Memory and DMA planned
Storage and root planned
Display planned
Input planned
GPU planned
Network planned
Audio planned
Power planned
Image assembly planned
Diagnostics planned

Configuration

planned

Hardware and dependencies

  • iOS 16.7.16 inputs, reviewed SM7475 feed and board-specific ADT/configuration.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • Resolve board pins, OS profile, SoC feed, source selection, array replacements and patch order. No matching iOS 16.7.16 profile or reviewed SM7475 feed was present at upstream 0fc0fc1f9d.
  • Added the schema-2 identity, a real reference-only Git lock, matching iPhone restore identity/member hashes, input inventories and the official record workflow. The matching OS/SoC implementations are still absent, so example=true remains a build guard; a 13-area record pass is not a resolved build.

Completion criteria

  • Reviewed profile/feed exists; all source pins and config resolve; selected components and overrides are recorded.

Current limits

  • The published v4 tree is based on XNU 1b191cb58250d0705d8a51287127505aa4bc0789 and is an older dirty snapshot, not the exact tested kernel source. This area is not claimed Format-2 implemented or verified.

Next action

  • Obtain reviewed matching upstream profile/feed, then resolve board pins and a clean source migration.

Evidence

Firmware and boot

planned

Hardware and dependencies

  • Matching user-supplied firmware, boot payload and qualified device tree.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • Matching restore-derived firmware, boot payload, device-qualified FDT and handoff inputs. Private firmware/system images are not included.
  • Measured legacy layout is Platforms/Xiaomi/marblePkg/marble.dsc and Build/marblePkg/{target}_CLANGPDB/FV/SILICIUM_UEFI.fd, Android header v4. Board package integration is explicitly unfinished; no fabricated Kit.toml or vendor hash is used.

Completion criteria

  • Clean payload boots and documents firmware, framebuffer and memory handoff.

Current limits

  • Historical experimental kernel reached Hello through temporary fastboot boot; the published v4 source does not exactly reproduce that image. This area is not claimed Format-2 implemented or verified.

Next action

  • Build the boot payload from public sources plus user-supplied firmware, then validate handoff on target.

Evidence

CPU and interrupts

planned

Hardware and dependencies

  • Device CPU topology, GIC, timer and interrupt map.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • SM7475-family CPU topology, GIC ranges, timer rate, interrupts and IPIs.
  • Observed boot affinity0, PSCI smc, GIC distributor0x17100000/0x10000 and redistributor0x17180000/0x200000, stride0x40000, virtual timer19200000Hz/PPI11. Only one boot CPU is described; no format-2 SMP or IPI result is claimed.

Completion criteria

  • Every enabled CPU reaches checkpoint and timer/IPI works on each.

Current limits

  • Hello establishes a historical kernel-to-userspace path, not full per-core or interrupt coverage. This area is not claimed Format-2 implemented or verified.

Next action

  • Record per-core entry, timer and interrupt checkpoints from a clean build.

Evidence

Memory and DMA

planned

Hardware and dependencies

  • Validated ADT, physical map, reservations, DMA widths/cache policy and stream ownership.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • Memory handoff/reservations, DMA widths/cache policy and SMMU ownership. Touch GPI and QUP wrapper have distinct DMA contexts.
  • The sanitized DTS omits guessed RAM/reservation ranges. Legacy firmware allocated a real512MiB window; a DRAM envelope is not RAM capacity. GPI ring SID0x5b6 and QUP payload SID0x5a3 are separate mapping roles, not a DMA-safety proof.

Completion criteria

  • Memory reservations reconcile and each enabled DMA engine stays within a verified mapped range.

Current limits

  • SMMU decoder handles already-read words only; it does not program MMIO, DMA or SMMU. This area is not claimed Format-2 implemented or verified.

Next action

  • Audit reservations and implement/verify each needed DMA context before enabling peripheral DMA.

Evidence

Storage and root

planned

Hardware and dependencies

  • Device-qualified UFS path, root layout and user-provided restore input.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • UFS controller/PHY/clocks/power, SMMU stream, GPT/root layout and restore inputs.
  • The described UFS register regions are 0x1d84000/0x3000,0x1d88000/0x8000,0x1d90000/0x9000. Legacy native UFS/HFSX work reached launchd/Hello on the maintainer root; a fresh format-2 root and driver/PHY/power integration remain unverified.

Completion criteria

  • UFS reads and root mount work; Data behavior is explicitly validated.

Current limits

  • Project status reports legacy UFS/HFS root progressed to launchd/Hello; persistence and broad storage qualification are not established. This area is not claimed Format-2 implemented or verified.

Next action

  • Reproduce UFS reads, HFS root mount and controlled Data persistence from a clean public build.

Evidence

Display

planned

Hardware and dependencies

  • Panel, framebuffer and backlight metadata for this SKU.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • Framebuffer/GOP handoff, panel timing, format, stride and backlight.
  • Legacy GOP-backed display showed Apple Logo and multilingual Hello with a clean background. No fixed framebuffer address is put in DTS. The GUI quiet latch hides normal logs after first swap, so a persistent Logo alone does not identify the blocked service.

Completion criteria

  • Known geometry/colors are correct through userland transition and backlight control.

Current limits

  • Historical legacy kernel showed a clean multilingual Hello screen and home indicator; broader rendering/backlight validation is absent. This area is not claimed Format-2 implemented or verified.

Next action

  • Capture geometry/format/timing from a reproducible build and validate UI transition/backlight.

Evidence

Input

planned

Hardware and dependencies

  • Goodix protocol, pin/power state, GPI ownership and verified mappings.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • Goodix SPI SE4/static GPII0, TLMM, power/interrupt state and separate GPI/wrapper SMMU contexts.
  • Goodix9916R uses SPI0x990000,CS0,15MHz child limit, GPIO20reset/GPIO21IRQ. GCC IDs94/134/135 and GPI TX0/RX1/SEID4/protocol1/64TREs are inventoried. Clock enable/read/restore and snapshot return are observed; no Goodix SPI transaction or physical iOS touch exists.

Completion criteria

  • Goodix transaction completes with bounded DMA/events and iOS HID contacts operate through setup.

Current limits

  • Physical iOS touch is not implemented. Clock/prerequisite probes and host decoders do not implement a GPI DMA provider or HID event path. This area is not claimed Format-2 implemented or verified.

Next action

  • Establish DMA ownership/mappings, implement GPI completion and Goodix protocol, then verify HID delivery.

Evidence

GPU

planned

Hardware and dependencies

  • GPU firmware, SMMU context and OS submission ABI.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • GPU/GMU generation, firmware, clocks/votes, SMMU and submission ABI.
  • No GPU/Metal support is claimed. The current Adreno740 catalog entry is SM8550-specific and is not selected for this SM7475 board.

Completion criteria

  • Verified GPU/GMU init and submission/fence path; acceleration scope documented.

Current limits

  • No GPU acceleration result is claimed; Hello display does not prove GPU operation. This area is not claimed Format-2 implemented or verified.

Next action

  • Inventory the stack and define a bounded submit/fence checkpoint before component selection.

Evidence

Network

planned

Hardware and dependencies

  • Device network firmware, transport and DMA mapping.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • Wi-Fi/cellular hardware, firmware, interrupts, DMA and OS interfaces.
  • No iOS Wi-Fi/cellular association or packet transfer is verified; firmware, DMA and OS-interface wiring remain pending rather than filled with assumed values.

Completion criteria

  • Device associates and transfers packets through the OS interface.

Current limits

  • No network association or packet transfer is claimed. This area is not claimed Format-2 implemented or verified.

Next action

  • Inventory one network transport and firmware dependency before implementation.

Evidence

Audio

planned

Hardware and dependencies

  • DSP/codec firmware, clocking and routes.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • DSP, codec, clocks, firmware services and routes.
  • No DSP/codec route or iOS playback/capture is verified. The record does not infer working audio from kernel or Hello progress.

Completion criteria

  • At least one documented playback/capture route works.

Current limits

  • No audio playback or capture is claimed. This area is not claimed Format-2 implemented or verified.

Next action

  • Trace the DSP/codec dependencies and define a playback or loopback checkpoint.

Evidence

Power

planned

Hardware and dependencies

  • Rail/clock ownership, battery units and transition policy.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • Regulators, clocks, battery units, firmware ownership and supported transitions.
  • The bounded legacy S4 probe temporarily set its owned GCC vote and restored it; this is not complete touch rail/reset sequencing or battery/power-management support.

Completion criteria

  • Rails/clocks are owned and a supported power transition recovers correctly.

Current limits

  • Touch clock probe has narrow read/restore scope; it is not system power management. This area is not claimed Format-2 implemented or verified.

Next action

  • Document ownership and validate a controlled suspend/resume transition.

Evidence

Image assembly

planned

Hardware and dependencies

  • Pinned public source inputs and user-provided proprietary restore data.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • Matching iOS restore input, XNU, ADT, generated trust-cache data, payload and boot-image format.
  • The restore input is iPhone10,6/d221ap iOS16.7.16/20H392, chip0x8015 board0x0e; six exact member SHA256 pins were recomputed without publishing binaries. The 64MiB payload/header-v4 legacy recipe and monolithic patch are inventoried, not validated as a modern format-2 stack.

Completion criteria

  • Clean build/package from pinned source plus user inputs reproduces checksummed output.

Current limits

  • No IPSW/root filesystem/firmware/boot image is published; current snapshot is not a full reproduction package. This area is not claimed Format-2 implemented or verified.

Next action

  • Reconstruct from pinned public inputs and user-provided data; produce clean auditable package before migration claims.

Evidence

Diagnostics

planned

Hardware and dependencies

  • Recoverable boot/log path and identified source/image artifacts.

Configuration

  • Record actual board keys, device-tree properties, build flags and source revisions as resolved; no placeholder profile or feed value is treated as established.

Procedure

  • Use the documented offline workflow with explicit user-supplied inputs; preserve the command, source revision and observable result for each milestone.

Development findings

  • Log transport, checkpoints, recovery and source/image identities.
  • Official pinned checker reports13 structured areas, and the sanitized DTS compiles without diagnostics. Actual defconfig/status/tree attempts stop at the absent reviewed sm7475 SoC source; even an implemented local SoC would still need the missing iOS16 OS profile. Reference lock verification ran on Linux/WSL, not a whole-target build.

Completion criteria

  • Recovery and logs correlate checkpoints with exact source and artifact revisions.

Current limits

  • Private recordings/logs are excluded; only sanitized observation summary is public. Logo-only probes do not establish a specific failure cause. This area is not claimed Format-2 implemented or verified.

Next action

  • Publish reproducible source/image identifiers and bounded log checkpoints.

Evidence