UniXNU

简体中文

English

简体中文

English

外观

Redmi Pad format-2 qualification candidate; boot Mu and cust UniXNU must remain separate ​

woaphone/UniXNU-yunluo

Redmi Pad MT6789 format-2 qualification; Mu in boot, UniXNU in cust. Not yet build- or device-qualified.

源记录: porting.toml, c2b81b9f4f5ded51b114008e60baadc1f53ee89b.

本页按设备记录自动生成。

部分状态
配置planned
固件与启动planned
CPU 与中断planned
内存与 DMAplanned
存储与根卷planned
显示planned
输入planned
GPUplanned
网络planned
音频planned
电源planned
镜像组装planned
诊断planned

配置 ​

planned

组件: ArmDTPlatform, SoftwareAES.

硬件与依赖 ​

  • Current format-2 framework, selected OS profile, local MT6789 SoC commit d179fac7d291ae05b3546aa0abe04bf1a17475ca

配置 ​

  • Profiles resolve in arch/SoC/OS/device order; arrays replace inherited arrays.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Integrate every required runtime component and publish reviewed SoC/component pins before enabling an image build.

开发经验 ​

  • Only the qualification core is selected. The full legacy MTK storage/input/display archive set is not yet migrated; this is not baseline equivalence.
  • The initial public WIP pins woaphone/UniXNU-mt6789-common at cad9262392dd589b75c7c9bf38f3f6c256be6c31 and supplies an ignored local override example. It is source publication, not a completed runtime migration.

完成条件 ​

  • All source pins resolve; every selected component has a record; status shows the intended overrides and patch order.

当前范围 ​

  • Only the qualification core is selected. The full legacy MTK storage/input/display archive set is not yet migrated; this is not baseline equivalence.

下一步 ​

  • Integrate every required runtime component and publish reviewed SoC/component pins before enabling an image build.

证据 ​

固件与启动 ​

planned

组件: DarwinBoot.

硬件与依赖 ​

  • Mu-Silicium platform firmware, BootShim and stock boot/vendor_boot protocol inputs.

配置 ​

  • boot contains Mu firmware only; UniXNU and file-loaded DarwinBoot belong in cust.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Separate FV integration from cust EFI files, then prove the actual cust entry load path without the old ramdisk fallback.

开发经验 ​

  • The format-2 candidate has not built a complete cust chainload path.
  • The independent v4 firmware and cust-v2 artifacts have source/offline evidence, but are not a clean build of this format-2 configuration.
  • loader/ publishes the exact source-only largest-window reference and its provenance. It is not yet selected by the board build; no new device or desktop result is claimed.

完成条件 ​

  • Firmware image builds, enters UniXNU, publishes the framebuffer and preserves the documented memory reservations.

当前范围 ​

  • The old FV embeds loader/application modules; a cust chainload path has not been built or tested.

下一步 ​

  • Separate FV integration from cust EFI files, then prove the actual cust entry load path without the old ramdisk fallback.

证据 ​

CPU 与中断 ​

planned

组件: ArmCpu.

硬件与依赖 ​

  • Six Cortex-A55 plus two Cortex-A76; source ADT affinities 0..0x700 in 0x100 steps, GICv3 and 13 MHz timer.

配置 ​

  • Board DTS includes the MT6789 DTSI; selected CPU driver and Apple CPU-node ABI must be audited together.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Compare reg/cpu-id/reg-private and GIC ranges against the preserved working ABI before a new boot.

开发经验 ​

  • A DTS compile cannot prove CPU start or IPIs; old ADT vs current common-converter CPU properties need comparison.

完成条件 ​

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

当前范围 ​

  • A DTS compile cannot prove CPU start or IPIs; old ADT vs current common-converter CPU properties need comparison.
  • New common output omits cpu-id/no-aic-ipi-required present in the preserved working generator; validate the selected component/kext consumers before boot.

下一步 ​

  • Compare reg/cpu-id/reg-private and GIC ranges against the preserved working ABI before a new boot.

证据 ​

内存与 DMA ​

planned

硬件与依赖 ​

  • Six-GiB board DRAM declaration, 2.5-GiB requested loader window, existing reservations and DMA ownership.

配置 ​

  • DRAM starts at 0x40000000; requested owned window 0xa0000000, not proof of a new allocation.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Account for every firmware reservation and DMA engine; compare generated ADT and actual loader allocation.

开发经验 ​

  • No new DMA/SMMU/reservation qualification; historical 2.5-GiB log is not evidence for this proposed branch.
  • The largest-window source helper and tests preserve reserved edges and real allocation accounting. This source reference is not yet enabled by the format-2 candidate and does not prove successful device allocation.

完成条件 ​

  • All handoff regions are accounted for and each enabled DMA engine accesses its allocated range with the documented cache policy.

当前范围 ​

  • No new DMA/SMMU/reservation qualification; historical 2.5-GiB log is not evidence for this proposed branch.

下一步 ​

  • Account for every firmware reservation and DMA engine; compare generated ADT and actual loader allocation.

证据 ​

存储与根卷 ​

planned

硬件与依赖 ​

  • MTK UFS LU2/4096-byte blocks and host 0x11270000/0x2300; actual cust GPT/LP identity and capacity are required.

配置 ​

  • cust owns the separate UniXNU filesystem. Persistent Data is independent and is not enabled by this layout.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Obtain saved GPT/LP metadata, qualify direct firmware visibility, and migrate the real MTK transport without Qualcomm aliases.

开发经验 ​

  • No cust geometry/type/GUID/filesystem has been established. NativeMtkUfs is not ShengUfs; UFS transport is not in this core-only candidate.
  • Boot-Mu/cust-UniXNU separation is enforced as a source-policy and release gate; cust geometry/discovery remain unknown, so the build-readiness gate correctly refuses progression.

完成条件 ​

  • Actual cust partition type/capacity and firmware block/filesystem visibility are established without guessed geometry.
  • Qualified MTK reads identify GPT/LUN/root windows correctly and launchd starts; persistent Data tests remain a separate explicit scope/authorization.

当前范围 ​

  • No cust geometry/type/GUID/filesystem has been established. NativeMtkUfs is not ShengUfs; UFS transport is not in this core-only candidate.

下一步 ​

  • Obtain saved GPT/LP metadata, qualify direct firmware visibility, and migrate the real MTK transport without Qualcomm aliases.

证据 ​

显示 ​

planned

硬件与依赖 ​

  • UEFI GOP handoff, 1200x2000 panel and 2048-pixel/8192-byte stride from existing source records.

配置 ​

  • Preserve the qualified mod_init ordering and donor vtable/selector ABI when integrating the actual implementation.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Port the actual display component and probe lifecycle, then test a known frame and userspace presentation.

开发经验 ​

  • No display runtime or physical presentation is qualified on this branch; unknown SIGBUS fault PC remains unresolved.

完成条件 ​

  • A known frame appears with correct geometry and colors, then userland presentation and backlight controls work.

当前范围 ​

  • No display runtime or physical presentation is qualified on this branch; unknown SIGBUS fault PC remains unresolved.

下一步 ​

  • Port the actual display component and probe lifecycle, then test a known frame and userspace presentation.

证据 ​

输入 ​

planned

硬件与依赖 ​

  • Yunluo PMIC state helper plus reusable Novatek protocol/core models; actual MTK bus/IRQ and yunluo sensor firmware remain separate inputs.

配置 ​

  • Power uses TOPSTATUS bit1, volume-up bit3; inherited Qcom clock/pin/SMMU helpers are excluded.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Run scoped host regressions and qualify the actual sensor/firmware/bus/HID ABI before claiming touch works.

开发经验 ​

  • Novatek tests model NT36532-family behavior, not a physical yunluo sensor. No real firmware blob, SPI rate, IRQ or HID consumer path is qualified here.
  • Committed-source host models pass; their scope excludes real firmware, MTK bus timing, physical keys, IRQ and HID consumers. The area remains planned as an end-to-end input capability.
  • The added largest-window host test is a loader arithmetic test, not additional physical input or HID qualification.

完成条件 ​

  • Touches map to the display, simultaneous contacts keep stable IDs, release events arrive, and buttons produce expected HID reports.

当前范围 ​

  • Novatek tests model NT36532-family behavior, not a physical yunluo sensor. No real firmware blob, SPI rate, IRQ or HID consumer path is qualified here.

下一步 ​

  • Run scoped host regressions and qualify the actual sensor/firmware/bus/HID ABI before claiming touch works.

证据 ​

  • source: Explicit source/qualification boundary and outstanding runtime work; no new device proof.
  • host: PASS under ASan/UBSan: 4096 PMIC state combinations and polling cases; register model only. Command: /usr/bin/g++ -O1 -g -Wall -Wextra -fsanitize=address,undefined -fno-sanitize-recover=all -fno-omit-frame-pointer -std=c++17 tests/board-key-state.cpp -o /home/ubuntu/unixnu-ext4/yunluo-upstream-20261030/release/UniXNU-yunluo/out/host-committed/pmic-state && /home/ubuntu/unixnu-ext4/yunluo-upstream-20261030/release/UniXNU-yunluo/out/host-committed/pmic-state. Revision: 238f33cda2750f52c19748607cee6ca56f56e2a3.
  • host: PASS under ASan/UBSan: reusable protocol model; real-firmware cases explicitly skipped. Command: /usr/bin/gcc -O1 -g -Wall -Wextra -fsanitize=address,undefined -fno-sanitize-recover=all -fno-omit-frame-pointer -std=c11 drivers/NativeNovatekTouch/Test/nvt-protocol.c drivers/NativeNovatekTouch/NvtProtocol.c -o /home/ubuntu/unixnu-ext4/yunluo-upstream-20261030/release/UniXNU-yunluo/out/host-committed/novatek-protocol-model && /home/ubuntu/unixnu-ext4/yunluo-upstream-20261030/release/UniXNU-yunluo/out/host-committed/novatek-protocol-model. Revision: 238f33cda2750f52c19748607cee6ca56f56e2a3.
  • host: PASS under ASan/UBSan: synthetic contact/core model; no physical sensor or HID client qualified. Command: /usr/bin/gcc -O1 -g -Wall -Wextra -fsanitize=address,undefined -fno-sanitize-recover=all -fno-omit-frame-pointer -std=c11 drivers/NativeNovatekTouch/Test/touch-core.c drivers/NativeNovatekTouch/NvtTouchCore.c -lm -o /home/ubuntu/unixnu-ext4/yunluo-upstream-20261030/release/UniXNU-yunluo/out/host-committed/novatek-touch-core-model && /home/ubuntu/unixnu-ext4/yunluo-upstream-20261030/release/UniXNU-yunluo/out/host-committed/novatek-touch-core-model. Revision: 238f33cda2750f52c19748607cee6ca56f56e2a3.

GPU ​

planned

硬件与依赖 ​

  • MT6789 Mali hardware identity and a compatible driver/frontend ABI, not Adreno firmware or GMU recipes.

配置 ​

  • No Adreno/Qcom components are selected.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Inventory the actual Mali submission, memory/fence and presentation interfaces before choosing an implementation.

开发经验 ​

  • GPU/Metal acceleration is planned and unsupported, not declared not-applicable to a device with a GPU.

完成条件 ​

  • GPU submissions complete, mapping/fence handling is correct, a known image renders, and the selected Metal client presents it.

当前范围 ​

  • GPU/Metal acceleration is planned and unsupported, not declared not-applicable to a device with a GPU.

下一步 ​

  • Inventory the actual Mali submission, memory/fence and presentation interfaces before choosing an implementation.

证据 ​

网络 ​

planned

硬件与依赖 ​

  • Board wireless bus, chipset, firmware, IRQ/DMA and OS network interface.

配置 ​

  • No WLAN implementation is selected.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Inventory verified wireless resources and choose an implementation compatible with this board.

开发经验 ​

  • Association and packet transfer are unimplemented; this is not not-applicable.

完成条件 ​

  • Scanning, association, address configuration and sustained receive/transmit traffic pass with the selected firmware.

当前范围 ​

  • Association and packet transfer are unimplemented; this is not not-applicable.

下一步 ​

  • Inventory verified wireless resources and choose an implementation compatible with this board.

证据 ​

音频 ​

planned

硬件与依赖 ​

  • MTK DSP/codec, clocks, firmware services and physical route inventory.

配置 ​

  • No Qualcomm DSP/GLINK/QMP recipe is selected.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Establish the actual MTK audio resources and services before porting a route.

开发经验 ​

  • Playback/capture are not implemented or verified.

完成条件 ​

  • Each declared route carries the selected audio format through playback or capture and handles start/stop correctly.

当前范围 ​

  • Playback/capture are not implemented or verified.

下一步 ​

  • Establish the actual MTK audio resources and services before porting a route.

证据 ​

电源 ​

planned

硬件与依赖 ​

  • MTK regulator/clock/battery units, firmware ownership and transition dependencies.

配置 ​

  • A pure PMIC key-state model is not battery or suspend/resume support.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Identify source-confirmed controls and define per-transition observable tests.

开发经验 ​

  • Sleep/resume, battery and peripheral power transitions remain unqualified.

完成条件 ​

  • Declared power controls and battery readings match observations; each claimed sleep/resume transition restores its dependent peripherals.

当前范围 ​

  • Sleep/resume, battery and peripheral power transitions remain unqualified.

下一步 ​

  • Identify source-confirmed controls and define per-transition observable tests.

证据 ​

镜像组装 ​

planned

组件: XnuPrelink.

硬件与依赖 ​

  • XNU 10063.141.1/21H461 ABI inputs and separately built Mu boot and UniXNU cust images.

配置 ​

  • No UniXNU payload in boot ramdisk. Exact cust image size/filesystem awaits partition evidence.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Implement and test two-artifact manifests, boot payload exclusion and exact cust EFI/kernel/ADT contents before usability testing.

开发经验 ​

  • No complete archive/bootstrap chain, kernel/prelink or split image build has passed; current upstream boot packer is not proven for this board v4 path.
  • Boot-Mu/cust-UniXNU separation is enforced as a source-policy and release gate; cust geometry/discovery remain unknown, so the build-readiness gate correctly refuses progression.

完成条件 ​

  • Separate boot firmware and cust UniXNU artifacts build from reviewed source pins; boot contains no UniXNU payload ramdisk; cust contains all declared EFI/runtime/kernel/ADT inputs.
  • An explicitly authorized device test identifies both artifact hashes and proves Mu loads the intended cust path, not an old ramdisk or unrelated ESP.

当前范围 ​

  • No complete archive/bootstrap chain, kernel/prelink or split image build has passed; current upstream boot packer is not proven for this board v4 path.

下一步 ​

  • Implement and test two-artifact manifests, boot payload exclusion and exact cust EFI/kernel/ADT contents before usability testing.

证据 ​

诊断 ​

planned

硬件与依赖 ​

  • Exact source/firmware/image revisions, accessible logs and official record/base-diff checks.

配置 ​

  • Host and device evidence are distinct; publication is gated on real build and usable-boot proof.

操作步骤 ​

  • Use the corresponding current UniXNU common guide; preserve source pins and collect the result before progressing.
  • Record real commands/results and full source revisions, then run the official normal and --base checks.

开发经验 ​

  • No proposed-branch device log exists. Historical logs are not relabeled as fresh test evidence.

完成条件 ​

  • Each claimed milestone has a reproducible command, a matching source/image revision and an accessible result.

当前范围 ​

  • No proposed-branch device log exists. Historical logs are not relabeled as fresh test evidence.

下一步 ​

  • Record real commands/results and full source revisions, then run the official normal and --base checks.

证据 ​

Released under the BSD-2-Clause-Patent License.

Copyright 2026 UniXNU contributors