docs: describe the current Bluetooth driver and key wrapping

Rewrite the QcaBluetooth page as current state, list it with the official drivers and describe software key wrapping.
This commit is contained in:
UniXNU Docs
2026-11-06 02:15:52 +08:00
committed by bluseliu50
Unverified
parent 3299798659
commit e2fdae4312
8 changed files with 149 additions and 197 deletions
+2
View File
@@ -8,6 +8,8 @@ AppleKeyStore state queries and state hooks for the selected userland ABI.
The component handles AppleKeyStore selectors and the state callbacks used by the selected OS profile. Its runtime service and symbols are recorded in the catalog.
Key wrapping is software: the device key derives from the identity the board returns through `native_aks_device_id`, and the keychain uses it to store and read items. This is not hardware data protection. Reference key operations and device lock are unsupported.
## Integration
The catalog records implementation scope, hardware and OS requirements, board dependencies, revision, build stage, outputs, and runtime identifiers. The selected profile orders build commands by dependency.
+74 -110
View File
@@ -1,143 +1,107 @@
# QcaBluetooth
QcaBluetooth connects a Qualcomm WCN7850 UART controller to Apple's Bluetooth
stack. Board integration lives in `UniXNU-sheng`; the component is under
`drivers/QcaBluetooth` during development.
stack.
[Source repository](https://github.com/UniXNU/QcaBluetooth).
## Status
Device: Xiaomi Pad 6S Pro (sheng), iPadOS 27.0.1 (24A446).
| State | Features |
| --- | --- |
| Working | Pairing, reconnection after reboot, power toggle, A2DP playback, AirPods noise control and battery, use alongside Wi-Fi |
| Not tested | Calls and microphone (HFP/SCO), sleep and wake |
| Unavailable | Features that need Apple vendor commands |
## Layers
The board supplies WCN power ownership, clocks, pins, DMA mappings and IRQs.
`WcnPower.h` exposes independent Wi-Fi and Bluetooth votes over the shared
six supplies. The last owner releases them; Bluetooth-only startup skips the
PCIe bus vote. Wi-Fi's startup uses this ownership path.
The driver runs the locked Linux `btqca.c` initialization, H4 framing and IBS.
UART.SK/Skywalk carries H4 bytes to `bluetoothd`; BlueTool requests controller
startup through `kern.sheng_bt_control`. Apple's stack owns scanning, pairing,
keys, BLE and audio profiles.
UART.SK/Skywalk carries H4 bytes to `bluetoothd`. Apple's stack owns scanning,
pairing, keys, BLE and audio profiles.
GENI uses four 2048-byte RX buffers and one 4096-byte TX buffer. Hard IRQ
masks its line and wakes the worker. RX backpressure retains buffer ownership
and stops RFR when full. TX completion checks DMA and wire drain. IBS control
bytes enter only between complete H4 packets. Physical clock-off requires
completed RX quiescence and an armed hardware wake source.
GENI uses four 2048-byte RX buffers and one 4096-byte TX buffer. Hard IRQ masks
its line and wakes the worker. RX backpressure retains buffer ownership and stops
RFR when full. TX completion checks DMA and wire drain. IBS control bytes enter
only between complete H4 packets. Clock-off requires RX quiescence and an armed
hardware wake source.
The board stages hashed firmware under `firmware/qca` in the Data addon.
`package/BluetoothFirmware.h` defines the same path used by
`scripts/stage-bluetooth-firmware.py`. VFS reads wait for addon installation.
| Sysctl | Meaning |
| --- | --- |
| `kern.qbt_boot` | Controller state |
| `kern.qbt_power_on` | Reading starts the controller and returns the result |
| `kern.qbt_firmware` | Loaded firmware name |
`sheng-bluetooth=1` starts the UART14 worker after addon installation. The board
binds GENI SE6 at 0x898000, IRQ 493 and QUP2 DMA SID 0x423. SM8550 operations
select the exact 51.2 MHz source for 3.2 Mbaud. The board maps its 32 KiB DMA
buffers through the firmware-managed bypass bank shared with touch and audio,
using 64-bit physical addresses. Configuration locks coordinate clock votes and SMMU
allocation with touch and audio. GPIO79 wakes the gated UART through the shared
TLMM IRQ. The UART requires protocol-2 microcode from the boot firmware.
All three are read-only because BlueTool's sandbox denies sysctl writes.
Connecting to UART.SK also starts a stopped controller.
The board exports a Bluetooth device-tree node and a matching IOService before
userland starts. H4 UART.SK encoding and 3.2 Mbaud use four-byte little-endian
properties. Both carry the stable private address derived from the platform
identity. The Linux boundary converts the public address to bdaddr_t order.
## Board integration
The resolved QcaBluetooth checkout supplies both kernel and userland builds.
UART clock-restore failures end the transport with the original error and stop
forwarding and retries.
The board supplies WCN power, clocks, pins, DMA mappings, IRQs and firmware.
`WcnPower.h` keeps independent Wi-Fi and Bluetooth votes over the shared supplies;
the last owner releases them.
Controller shutdown and faults wake both UART.SK rings. Their synchronization
callbacks return the controller error before moving data. Notifications retain
the rings until completion so disconnect can drain them.
On sheng, `sheng-bluetooth=1` starts the UART14 worker after the Data addon
installs. It binds GENI SE6 at 0x898000, IRQ 493 and QUP2 DMA SID 0x423. An exact
51.2 MHz source gives 3.2 Mbaud. DMA buffers use the firmware-managed bypass bank
shared with touch and audio. GPIO79 wakes the gated UART. The UART needs
protocol-2 microcode from the boot firmware.
The worker retains its DMA memory, services bounded batches and sleeps on IRQ,
ring-space or deadline events. Hardware faults abort command waiters immediately.
The `[bluetooth]` boot-log row records phase, transfers, sleep, power ownership
and SMMU status. `log-bluetooth=1` adds initialization messages.
The board exports `/arm-io/bluetooth` and a matching IOService before userland
starts, with H4 encoding, baud rate and a stable private address.
## Native adapter
The iPadOS 27 adapter is locked to one `bluetoothd` binary:
- Every product runs as controller type zero with standard HCI initialization.
- Capabilities follow Supported Commands and LE Features. Advertising capacity
comes from 0x203b, capped at six sets.
- Extended scanning uses 0x2041 and 0x2042. Random addresses are sent before a
scan or an advertising set starts.
- The patch keeps authenticated fixups and PACIBSP entry pads.
`payload.runtime` selects `build-bluetooth-userspace.py`, which stages signed
BlueTool, `bluetoothd` and `QcaBTType0.dylib` with pinned firmware. Read-only
unions expose them under `/usr/lib` and `/usr/sbin`. Wi-Fi and Bluetooth share
one signed launchd cache.
Pairing keys need the keychain, which needs [AppleKeyStoreState](/drivers/apple-key-store-state)
key wrapping.
## Audio
The audio overlay hides the system HAL plug-in directory. List
`BTAudioHALPlugin.driver` in `audio_system_plugins` under `payload.runtime`, and
the runtime builder copies the unchanged bundle from the OS image.
## Build and checks
From the component checkout:
```sh
python3 tools/test-runtime.py
python3 tools/test-geni.py
python3 tools/check-kernel.py /path/to/assembled/tree
python3 tools/build-bluetool.py
python3 tools/build-type0.py
python3 tools/check-kernel.py /path/to/tree --record <kernel source compile record> \
--extra-source <board source> --board-export <symbol>
```
Runtime and DMA simulations pass ASan/UBSan. The protocol, Linux adapter,
original `btqca.c`, DMA engine, Skywalk transport and board firmware reader
compile with the iPadOS 27 arm64e kernel command. Their references exist in the
selected kernel. BlueTool compiles and passes code-signature verification.
The board power check covers both radio startup orders, independent release,
idempotent votes and failed transitions; the Wi-Fi consumer compiles for arm64e.
From the workspace root, board checks are:
Run these from the component checkout. `native-ios27.md` lists the native adapter
checks. From the workspace root, the sheng board checks are:
```sh
python3 UniXNU-sheng/scripts/check-bluetooth-platform.py
python3 UniXNU-sheng/scripts/check-bluetooth-shared.py
python3 UniXNU-sheng/scripts/check-bluetooth-board.py /path/to/assembled/tree
python3 UniXNU-sheng/scripts/check-bluetooth-board.py /path/to/tree
python3 UniXNU-sheng/scripts/check-bluetooth-runtime.py
```
The platform model checks frequency ratios, DFS handoff, independent DMA tables,
ASID conflicts and timeout bounds. The shared-resource model checks IRQ dispatch,
concurrent registration and UART/audio clock ownership. UART14, ArmCpu, touch,
audio and boot-log sources compile for the selected target; the build recipe
compiles eight protocol and SoC objects into the board archive inputs.
`log-bluetooth=1` adds initialization messages to the boot log's `[bluetooth]`
rows, and `log-bluetooth=2` adds process and controller output rows.
The version-locked iPadOS 27 adapter selects controller type zero and retains
standard HCI initialization. Capabilities follow Supported Commands and LE
Features, including coded and 2M PHY. An asynchronous 0x203b query supplies
advertising capacity, capped at the native array's six records. Model getters,
configuration caches, lower flags and broadcaster mode receive the same values.
Normal packet traffic stays in UART.SK and the native stack.
The offline patch retains authenticated fixup metadata and PACIBSP entry pads.
It passes 144 native instruction cases at two ASLR slides; PAC operations are
modeled without device keys. The production publisher passes 58 ASan/UBSan HCI
and policy cases. `tools/build-type0.py` builds and signs the arm64e library.
The board's `payload.runtime` selects `build-bluetooth-userspace.py` for ios27.
It stages signed BlueTool, bluetoothd and QcaBTType0.dylib with pinned firmware.
The native daemon keeps its original identifier and entitlements. Read-only
unions expose /usr/lib and /usr/sbin entries, with the library mounted first.
BlueTool keeps its Mach service and runs as root with transactions enabled.
Wi-Fi and Bluetooth share one signed launchd cache; other native jobs remain
unchanged. Missing code hashes are appended to the preserved trust bundle.
`check-bluetooth-runtime.py` validates the packed addon, signatures, firmware,
launchd jobs, trust modules and original Data seed. The combined addon verifies
45 files, three signed Bluetooth binaries and 716 launchd jobs. Host libxpc
accepts the cache. The complete kernel, fileset, FAT payload and temporary boot
image build successfully with the explicit local component. The packed payload
contains the Bluetooth exports, H4/baud properties, signed runtime and preserved
Data seed, with automatic reset disabled. Device scanning, pairing, audio,
power and coexistence measurements are pending.
The device reaches the overlays, then launchd reports `No service cache`.
The complete parser, system-path and Data-path copies contain the packed cache
followed by 55 stale bytes. The addon writer explicitly sets the replacement
file size after successful writes. The ASan/UBSan writer fixture reproduces the
tail and verifies truncation; device verification is pending.
The firmware-managed UART DMA route and protocol-2 microcode are confirmed.
The initial version request reports a line error before TX. The board starts RX
after controller reset release, and GENI clears reset-time IRQ status before
arming RX. Live fault IRQ values are retained for one error report. This keeps
16 KiB of private tables and shared-bank polling out of the path. Target
compilation and the GENI model pass; native features, power and coexistence
measurements remain pending.
`sheng-cache-log=1` captures the loader log and exports bounded parser and
filesystem cache snapshots on a matched 24A446 failure. GPU and latency capture
stay disabled.
Select the local component from the UniXNU checkout:
```sh
./unixnu build kernel payload -D /path/to/UniXNU-sheng --os 27 \
--local-module driver:QcaBluetooth=/path/to/QcaBluetooth
```
Supply the preserved installation inputs from [Runtime inputs](/porting/packaging#runtime-inputs-for-ios-27),
then follow [Boot image](/concepts/payload) for temporary device startup.
Supply the installation inputs from [Runtime inputs](/porting/packaging#runtime-inputs-for-ios-27),
then follow [Boot image](/concepts/payload).
Sources: [Linux](https://github.com/ianchb/sm8550-mainline),
[Debian sheng](https://github.com/ianchb/debian-sheng),
+1
View File
@@ -23,6 +23,7 @@ These repositories are maintained in the UniXNU organization.
| ShengNovatekTouch | [UniXNU/ShengNovatekTouch](https://github.com/UniXNU/ShengNovatekTouch) | XNU touch | [ShengNovatekTouch](/drivers/sheng-novatek-touch) |
| XnuPrelink | [UniXNU/XnuPrelink](https://github.com/UniXNU/XnuPrelink) | Kernel tooling | [XnuPrelink](/drivers/xnu-prelink) |
| Ath12kWifi | [UniXNU/Ath12kWifi](https://github.com/UniXNU/Ath12kWifi) | XNU Wi-Fi | [Ath12kWifi](/drivers/ath12k-wifi) |
| QcaBluetooth | [UniXNU/QcaBluetooth](https://github.com/UniXNU/QcaBluetooth) | XNU Bluetooth | [QcaBluetooth](/drivers/qca-bluetooth) |
| ArmCpu | [UniXNU/ArmCpu](https://github.com/UniXNU/ArmCpu) | XNU CPU and GIC | [ArmCpu](/drivers/arm-cpu) |
| ArmDTPlatform | [UniXNU/ArmDTPlatform](https://github.com/UniXNU/ArmDTPlatform) | XNU platform expert | [ArmDTPlatform](/drivers/arm-dt-platform) |
| ArmVirtPlatform | [UniXNU/ArmVirtPlatform](https://github.com/UniXNU/ArmVirtPlatform) | XNU platform | [ArmVirtPlatform](/drivers/arm-virt-platform) |
+1 -1
View File
@@ -67,7 +67,7 @@ OS requirements, and board inputs.
A new component can use an explicit local source before catalog publication:
```sh
./unixnu tree -D /path/to/device --local-module driver:QcaBluetooth=/path/to/QcaBluetooth
./unixnu tree -D /path/to/device --local-module driver:MyDriver=/path/to/MyDriver
```
The new module is linked into the assembled tree. Its consuming board supplies
+2
View File
@@ -8,6 +8,8 @@
该组件处理 AppleKeyStore selector 和所选 OS 配置使用的状态回调,运行时服务与符号记录在组件目录中。
密钥封装由软件完成:设备密钥来自板级通过 `native_aks_device_id` 返回的标识,keychain 用它存取条目。这不是硬件数据保护。不支持引用密钥操作和设备锁定。
## 集成
组件目录记录实现范围、硬件与 OS 要求、板级依赖、源码版本、构建阶段、输出和运行时标识符。所选配置按依赖顺序运行构建命令。
+67 -85
View File
@@ -1,117 +1,99 @@
# QcaBluetooth
QcaBluetooth 将高通 WCN7850 串口控制器接入苹果蓝牙栈。板级集成位于
`UniXNU-sheng`,开发中的组件位于 `drivers/QcaBluetooth`。
QcaBluetooth 将高通 WCN7850 串口控制器接入苹果蓝牙栈。
[源码仓库](https://github.com/UniXNU/QcaBluetooth)。
## 状态
设备:小米平板 6S Pro(sheng),iPadOS 27.0.1(24A446)。
| 状态 | 功能 |
| --- | --- |
| 可用 | 配对、重启后回连、开关蓝牙、A2DP 播放、AirPods 降噪和电量、与 Wi-Fi 同时使用 |
| 未测试 | 通话和麦克风(HFP/SCO)、休眠唤醒 |
| 不可用 | 依赖苹果厂商命令的功能 |
## 分层
板级代码提供 WCN 电源共享、时钟、引脚、DMA 映射与中断。驱动复用固定版本
Linux `btqca.c` 初始化流程,处理 H4 和 IBS。UART.SK/Skywalk 将 H4 数据交给
`bluetoothd`,BlueTool 通过 `kern.sheng_bt_control` 请求启动控制器。
扫描、配对、密钥、BLE 和音频协议由苹果系统负责。
`WcnPower.h` 为 Wi-Fi 和蓝牙分别记录共享六路电源的使用票,最后一方释放时关闭
电源。单独启动蓝牙跳过 PCIe 总线票;Wi-Fi 的启动路径已使用这个共享接口。
驱动复用固定版本 Linux `btqca.c` 的初始化流程,处理 H4 和 IBS。UART.SK/Skywalk
将 H4 数据交给 `bluetoothd`。扫描、配对、密钥、BLE 和音频协议由苹果系统负责。
GENI 使用四块 2048 字节接收缓冲和一块 4096 字节发送缓冲。硬中断只屏蔽中断线、
唤醒工作线程。接收侧保留未消费的缓冲,满时关闭 RFR;发送侧确认 DMA 完成且
串口排空。IBS 控制字节只插在完整 H4 包之间。物理关时钟要求接收侧停止完成,
并已启用硬件唤醒源。
唤醒工作线程。接收侧保留未消费的缓冲,满时关闭 RFR;发送侧确认 DMA 完成且串口
排空。IBS 控制字节只插在完整 H4 包之间。关时钟要求接收侧已停止,并已启用硬件
唤醒源。
固件按哈希校验后打入 Data 插件的 `firmware/qca`。读取端与打包脚本共用
`package/BluetoothFirmware.h` 定义的路径,VFS 读取等待插件安装完成。
| Sysctl | 含义 |
| --- | --- |
| `kern.qbt_boot` | 控制器状态 |
| `kern.qbt_power_on` | 读取即启动控制器并返回结果 |
| `kern.qbt_firmware` | 已加载的固件名 |
`sheng-bluetooth=1` 在插件安装后启动 UART14 工作线程。板级代码绑定 0x898000 的
GENI SE6、中断 493 和 QUP2 DMA 流 0x423。SM8550 代码使用精确的 51.2 MHz 时钟
生成 3.2 Mbaud。32 KiB DMA 缓冲使用 64 位物理地址,通过与触摸、音频共用的
固件管理直通上下文。配置锁协调触摸、音频
与蓝牙的时钟票和 SMMU 分配。GPIO79 通过共享 TLMM 中断唤醒已关时钟的串口。
UART 需要启动固件提供协议号为 2 的微码。
三者都是只读,因为 BlueTool 的沙盒禁止写 sysctl。连接 UART.SK 也会启动已停止的
控制器。
板级代码在用户态启动前导出蓝牙设备树节点和同名 IOService。H4 UART.SK 编码及
3.2 Mbaud 使用四字节小端属性,两者携带从平台标识派生的稳定私有地址。
Linux 接口把网络顺序的地址转换为 bdaddr_t 顺序。
## 板级集成
内核与用户态构建使用同一份已解析的 QcaBluetooth 源码。串口时钟恢复失败时,
驱动结束当前传输并保留硬件错误,停止转发和重试。
板级代码提供 WCN 电源、时钟、引脚、DMA 映射、中断和固件。`WcnPower.h` 为 Wi-Fi
和蓝牙分别记录共享电源的使用票,最后一方释放时关闭电源。
控制器关闭或故障时会唤醒 UART.SK 的收发队列,同步回调在搬运数据前返回控制器
错误。通知期间保留队列引用,断开流程等待通知完成后再释放。
在 sheng 上,`sheng-bluetooth=1` 在 Data 插件安装后启动 UART14 工作线程,绑定
0x898000 的 GENI SE6、中断 493 和 QUP2 DMA 流 0x423。精确的 51.2 MHz 时钟生成
3.2 Mbaud。DMA 缓冲使用与触摸、音频共用的固件管理直通上下文。GPIO79 唤醒已关
时钟的串口。UART 需要启动固件提供协议号为 2 的微码。
工作线程保留 DMA 内存,每次处理有界批量,等待中断、队列空间或期限事件。
硬件错误立即结束命令等待。启动日志的 `[bluetooth]` 行记录阶段、收发、休眠、
供电归属和 SMMU 状态;`log-bluetooth=1` 增加初始化信息。
板级代码在用户态启动前导出 `/arm-io/bluetooth` 和同名 IOService,带 H4 编码、
波特率和稳定的私有地址。
## 原生适配
iPadOS 27 适配固定匹配一个 `bluetoothd` 二进制:
- 所有产品都按控制器类型零运行,使用标准 HCI 初始化。
- 能力来自 Supported Commands 和 LE Features。广播组数来自 0x203b,上限六组。
- 扩展扫描使用 0x2041 和 0x2042。启动扫描或广播组前先发送随机地址。
- 补丁保留认证修正信息和 PACIBSP 入口。
`payload.runtime` 选择 `build-bluetooth-userspace.py`,打入已签名的 BlueTool、
`bluetoothd`、`QcaBTType0.dylib` 和固定版本固件。只读联合挂载在 `/usr/lib` 和
`/usr/sbin` 下暴露这些文件。Wi-Fi 和蓝牙共用一份签名启动缓存。
配对密钥依赖 keychain,keychain 依赖 [AppleKeyStoreState](/zh/drivers/apple-key-store-state)
的密钥封装。
## 音频
音频覆盖层会遮住系统的 HAL 插件目录。在 `payload.runtime` 的
`audio_system_plugins` 中列出 `BTAudioHALPlugin.driver`,运行时构建脚本会从系统
镜像原样复制该插件。
## 构建与检查
在组件目录运行:
```sh
python3 tools/test-runtime.py
python3 tools/test-geni.py
python3 tools/check-kernel.py /path/to/assembled/tree
python3 tools/build-bluetool.py
python3 tools/build-type0.py
python3 tools/check-kernel.py /path/to/tree --record <内核源码的编译记录> \
--extra-source <板级源码> --board-export <符号>
```
协议与 DMA 模拟通过 ASan/UBSan。协议核心、Linux 适配、原始 `btqca.c`、DMA 引擎、
Skywalk 桥接和板级固件读取代码通过 iPadOS 27 arm64e 内核参数编译,引用符号可在
目标内核中找到。BlueTool 已编译并通过签名检查。
电源模拟检查覆盖两种启动顺序、独立释放、重复申请和失败处理;Wi-Fi 消费端通过
arm64e 编译。
在工作区根目录运行板级检查:
以上在组件目录运行。原生适配的检查见 `native-ios27.md`。sheng 的板级检查在工作区
根目录运行:
```sh
python3 UniXNU-sheng/scripts/check-bluetooth-platform.py
python3 UniXNU-sheng/scripts/check-bluetooth-shared.py
python3 UniXNU-sheng/scripts/check-bluetooth-board.py /path/to/assembled/tree
python3 UniXNU-sheng/scripts/check-bluetooth-board.py /path/to/tree
python3 UniXNU-sheng/scripts/check-bluetooth-runtime.py
```
平台模型检查频率比例、DFS 切换、独立 DMA 页表、ASID 冲突和超时边界;共享资源
模型检查中断分发、并发注册和串口与音频的时钟归属。UART14、ArmCpu、触摸、音频
与启动日志代码通过目标编译,构建脚本为板级归档编译八个协议和 SoC 对象。
`log-bluetooth=1` 在启动日志的 `[bluetooth]` 行增加初始化信息,`log-bluetooth=2`
增加进程和控制器输出行。
iPadOS 27 原生适配固定匹配目标二进制,选择控制器类型零并保留标准 HCI 初始化。
扫描、连接、广播及 coded、2M PHY 能力来自 Supported Commands 和 LE Features。
异步 0x203b 查询取得广播组数,上限为原生数组的六组。模型查询、配置缓存、
底层开关及广播模式使用同一份能力。正常数据收发留在 UART.SK 和原生栈。
离线补丁保留指针修正链的认证信息与 PACIBSP 入口。144 项原生指令模拟覆盖两种
ASLR 偏移,PAC 操作按无设备密钥模型处理;生产能力发布代码通过 58 项 ASan/UBSan
HCI 与策略测试。`tools/build-type0.py` 构建并签名 arm64e 能力发布库。
板级 `payload.runtime` 为 ios27 选择 `build-bluetooth-userspace.py`,打入已签名的
BlueTool、bluetoothd、QcaBTType0.dylib 和固定版本固件。原生守护进程保留原有
标识与权限。只读联合挂载暴露 /usr/lib 和 /usr/sbin 文件,先挂载库再挂载程序。
BlueTool 保留原有 Mach 服务,以 root 身份运行并启用事务。Wi-Fi 和蓝牙共用一份
签名启动缓存,其他原生任务保持原样;缺少的代码哈希追加到原有信任包。
`check-bluetooth-runtime.py` 检查实际打包内容、签名、固件、启动任务、信任模块
和原有 Data 种子。联合插件通过 45 个文件、3 个签名蓝牙程序及 716 个启动任务
验证,宿主 libxpc 接受缓存。显式选择本地组件后,完整内核、fileset、FAT 载荷和
临时启动镜像均构建成功。实际载荷包含蓝牙入口、H4/波特率属性、签名运行时和
原有 Data 种子,并关闭自动重启。扫描、配对、音频、功耗和共存的上机验证待完成。
当前设备已完成覆盖挂载,随后 launchd 报 `No service cache`。完整导出确认,解析
输入、系统路径和 Data 路径下的文件均为新版缓存加上 55 字节旧尾巴。插件写入器
现已显式设置替换后的文件长度,ASan/UBSan 回归测试验证了截断,待设备验证。
固件管理的 UART DMA 映射和协议号为 2 的微码已确认。首次版本查询在发送前报
线路错误;板级代码改为控制器退出复位后再开启接收,GENI 启动时清除复位期间
残留的中断状态,并在真实故障时保留中断值。该路径无需 16 KiB 私有页表或共享
上下文轮询。目标编译与 GENI 模型通过,原生功能、功耗及共存验证待完成。
`sheng-cache-log=1` 采集加载器日志,并在匹配的 24A446 失败栈上导出有界的解析
输入及文件系统缓存快照。GPU 和延迟采样保持关闭。
在 UniXNU 仓库显式选择本地源码:
```sh
./unixnu build kernel payload -D /path/to/UniXNU-sheng --os 27 \
--local-module driver:QcaBluetooth=/path/to/QcaBluetooth
```
按[运行时输入](/zh/porting/packaging#ios-27-运行输入)提供原有安装输入,再按
[启动载荷](/zh/concepts/payload)封装临时启动镜像。
按[运行时输入](/zh/porting/packaging#ios-27-运行输入)提供安装输入,再按
[启动载荷](/zh/concepts/payload)操作。
参考:[Linux](https://github.com/ianchb/sm8550-mainline)、
[Debian sheng](https://github.com/ianchb/debian-sheng)、
+1
View File
@@ -23,6 +23,7 @@
| ShengNovatekTouch | [UniXNU/ShengNovatekTouch](https://github.com/UniXNU/ShengNovatekTouch) | XNU 触控 | [ShengNovatekTouch](/zh/drivers/sheng-novatek-touch) |
| XnuPrelink | [UniXNU/XnuPrelink](https://github.com/UniXNU/XnuPrelink) | 内核工具 | [XnuPrelink](/zh/drivers/xnu-prelink) |
| Ath12kWifi | [UniXNU/Ath12kWifi](https://github.com/UniXNU/Ath12kWifi) | XNU Wi-Fi | [Ath12kWifi](/zh/drivers/ath12k-wifi) |
| QcaBluetooth | [UniXNU/QcaBluetooth](https://github.com/UniXNU/QcaBluetooth) | XNU Bluetooth | [QcaBluetooth](/zh/drivers/qca-bluetooth) |
| ArmCpu | [UniXNU/ArmCpu](https://github.com/UniXNU/ArmCpu) | XNU CPU 和 GIC | [ArmCpu](/zh/drivers/arm-cpu) |
| ArmDTPlatform | [UniXNU/ArmDTPlatform](https://github.com/UniXNU/ArmDTPlatform) | XNU 平台专家 | [ArmDTPlatform](/zh/drivers/arm-dt-platform) |
| ArmVirtPlatform | [UniXNU/ArmVirtPlatform](https://github.com/UniXNU/ArmVirtPlatform) | XNU 平台 | [ArmVirtPlatform](/zh/drivers/arm-virt-platform) |
+1 -1
View File
@@ -63,7 +63,7 @@ include = ["ArmDTPlatform", "ArmCpu", "Adreno740", "AdrenoMetal", "GopFramebuffe
新组件发布到目录前,可以显式选择本地源码:
```sh
./unixnu tree -D /path/to/device --local-module driver:QcaBluetooth=/path/to/QcaBluetooth
./unixnu tree -D /path/to/device --local-module driver:MyDriver=/path/to/MyDriver
```
新模块会链接到装配树,由使用它的板级代码提供集成步骤。目录中已有的组件仍需在