Redmi K60 (mondrian/SM8475): UniXNU UEFI bring-up (wohusaixing)
Redmi K60 (mondrian/SM8475). Format 2 device: the kernel builds and prelinks, the payload and the boot image still need the board ADT and the hardware bring-up.
Source record: porting.toml, 092a61d8c20364eab86b35737c6b831c4cecc1ff.
This page is generated from the device record.
| Area | Status |
|---|---|
| Configuration | implemented |
| 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 | host-verified |
| Diagnostics | planned |
Configuration
implemented
Components: ArmDTPlatform, ArmCpu, XnuPrelink.
Hardware and dependencies
- Identify the configuration hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for configuration.
Procedure
- Follow the configuration stage in the porting guide and record the actual commands.
Development findings
- Migrated from format 1 on 2026-10-28: board.toml is schema_version = 2 with soc_source sm8475 and os_profile ipados-16.6.1-20G81, the SM8475 resources live in UniXNU-sm8475-common, and the board wiring in dts/mondrian.dts.
Completion criteria
- All source pins resolve; every selected component has a record; status shows the intended overrides and patch order.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required configuration inputs before implementation.
Evidence
Firmware and boot
planned
Hardware and dependencies
- Identify the firmware and boot hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for firmware and boot.
Procedure
- Follow the firmware and boot stage in the porting guide and record the actual commands.
Development findings
- Collect the first firmware and boot observation, its cause when established, and the resulting implementation decision.
Completion criteria
- Firmware image builds, enters UniXNU, publishes the framebuffer and preserves the documented memory reservations.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required firmware and boot inputs before implementation.
Evidence
Collect evidence using the next action.
CPU and interrupts
planned
Hardware and dependencies
- Identify the cpu and interrupts hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for cpu and interrupts.
Procedure
- Follow the cpu and interrupts stage in the porting guide and record the actual commands.
Development findings
- Collect the first cpu and interrupts observation, its cause when established, and the resulting implementation decision.
Completion criteria
- Every enabled CPU reaches its entry checkpoint and timer/IPI handling works on each enabled CPU.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required cpu and interrupts inputs before implementation.
Evidence
Collect evidence using the next action.
Memory and DMA
planned
Hardware and dependencies
- Identify the memory and dma hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for memory and dma.
Procedure
- Follow the memory and dma stage in the porting guide and record the actual commands.
Development findings
- Collect the first memory and dma observation, its cause when established, and the resulting implementation decision.
Completion criteria
- All handoff regions are accounted for and each enabled DMA engine accesses its allocated range with the documented cache policy.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required memory and dma inputs before implementation.
Evidence
Collect evidence using the next action.
Storage and root
planned
Hardware and dependencies
- Identify the storage and root hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for storage and root.
Procedure
- Follow the storage and root stage in the porting guide and record the actual commands.
Development findings
- Collect the first storage and root observation, its cause when established, and the resulting implementation decision.
Completion criteria
- Host: register, clock, link and SMMU facts match the board inventory.
- Reads: SCSI capacity, GPT and known blocks are correct; OS/SystemOS windows stay within userdata.
- Root: the configured volume mounts and launchd starts. Persistence: writes survive reboot within the allocated Data region.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required storage and root inputs before implementation.
Evidence
Collect evidence using the next action.
Display
planned
Hardware and dependencies
- Identify the display hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for display.
Procedure
- Follow the display stage in the porting guide and record the actual commands.
Development findings
- Collect the first display observation, its cause when established, and the resulting implementation decision.
Completion criteria
- A known frame appears with correct geometry and colors, then userland presentation and backlight controls work.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required display inputs before implementation.
Evidence
Collect evidence using the next action.
Input
planned
Hardware and dependencies
- Identify the input hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for input.
Procedure
- Follow the input stage in the porting guide and record the actual commands.
Development findings
- Collect the first input observation, its cause when established, and the resulting implementation decision.
Completion criteria
- Touches map to the display, simultaneous contacts keep stable IDs, release events arrive, and buttons produce expected HID reports.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required input inputs before implementation.
Evidence
Collect evidence using the next action.
GPU
planned
Hardware and dependencies
- Identify the gpu hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for gpu.
Procedure
- Follow the gpu stage in the porting guide and record the actual commands.
Development findings
- Collect the first gpu observation, its cause when established, and the resulting implementation decision.
Completion criteria
- GPU submissions complete, mapping/fence handling is correct, a known image renders, and the selected Metal client presents it.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required gpu inputs before implementation.
Evidence
Collect evidence using the next action.
Network
planned
Hardware and dependencies
- Identify the network hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for network.
Procedure
- Follow the network stage in the porting guide and record the actual commands.
Development findings
- Collect the first network observation, its cause when established, and the resulting implementation decision.
Completion criteria
- Scanning, association, address configuration and sustained receive/transmit traffic pass with the selected firmware.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required network inputs before implementation.
Evidence
Collect evidence using the next action.
Audio
planned
Hardware and dependencies
- Identify the audio hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for audio.
Procedure
- Follow the audio stage in the porting guide and record the actual commands.
Development findings
- Collect the first audio observation, its cause when established, and the resulting implementation decision.
Completion criteria
- Each declared route carries the selected audio format through playback or capture and handles start/stop correctly.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required audio inputs before implementation.
Evidence
Collect evidence using the next action.
Power
planned
Hardware and dependencies
- Identify the power hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for power.
Procedure
- Follow the power stage in the porting guide and record the actual commands.
Development findings
- Collect the first power observation, its cause when established, and the resulting implementation decision.
Completion criteria
- Declared power controls and battery readings match observations; each claimed sleep/resume transition restores its dependent peripherals.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required power inputs before implementation.
Evidence
Collect evidence using the next action.
Image assembly
host-verified
Hardware and dependencies
- Identify the image assembly hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for image assembly.
Procedure
- Follow the image assembly stage in the porting guide and record the actual commands.
Development findings
- The kernel links and prelinks on macOS CI. Format 1 run 40631225483 produced 54349824 bytes; format 2 run 40650877574 produced 54419456 bytes at the same slide -0xb9c000 and the same lowest component extent 0xfffffff004426600.
- The 69632-byte difference is a real fix, not noise: the format-1 glob applied zzzzzz-pong-init-scratch-allocation.patch through fuzz and the panic string it adds is absent from that kernel, while the strict format-2 series applies it at its intended place and the string is present. The checked scratch allocation had never reached a qualified kernel before.
Completion criteria
- Kernel and prelink succeed, payload contains all declared inputs, and the boot image matches the bootloader format and size limit.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required image assembly inputs before implementation.
Evidence
host: Build kernel succeeded on macOS from this revision: prelink slide -0xb9c000, 54419456 bytes, lowest component extent 0xfffffff004426600 Command:./unixnu build kernel -D ../UniXNU-mondrian. Revision:6a10bf5e42ecfad7eed2789cc091287d31009623.
Diagnostics
planned
Hardware and dependencies
- Identify the diagnostics hardware, resources and existing component interfaces for this board.
Configuration
- Record the board.toml fields, DTS properties and defconfig values used for diagnostics.
Procedure
- Follow the diagnostics stage in the porting guide and record the actual commands.
Development findings
- Collect the first diagnostics observation, its cause when established, and the resulting implementation decision.
Completion criteria
- Each claimed milestone has a reproducible command, a matching source/image revision and an accessible result.
Current limits
- Hardware inputs and implementation are pending for this board.
Next action
- Inventory the required diagnostics inputs before implementation.
Evidence
Collect evidence using the next action.