The porting flow covers the macos-27.3-26C5035r profile from profile
selection to the porting record: the macOS profile page lists the profile
contents, host inputs, board.toml override, Data seed, build commands,
driver adaptations and boot checkpoints, and the steps, arm64e, packaging,
records, bring-up, building, requirements and reference pages point to it.
The iPadOS instructions are unchanged.
Porting pages link porting pages for driver topics: Develop a driver and
Brightness interface are porting pages, and component names in porting
pages are plain text. English and Chinese pages.
The target table names the iOS 16.7.16 (iPhone X), iPadOS 17.7.11,
iOS 27.0.1 (iPhone 16 Pro) and iPadOS 27.0.1 restore images from
ipsw.me with their architecture. iOS 16 and iPadOS 17 are both arm64 and
share the arm64 patch series. Pages that named iPadOS alone now name iOS
or iPadOS where both apply, and the iPadOS 26 profile is no longer
described.
The packaging page describes the implemented unixnu release command, its
board.toml keys, the outputs and the checks verify makes. The arm64e page states
that arm64e needs native PAC hardware, that iPadOS 18 is the last version that
supports arm64, recommends PAC devices and the iOS or iPadOS 27 profile, and
states that every driver and optimization must work for 17 and 27 with the
build target as the only difference.
The arm64e page states that the method needs native PAC hardware, that iPadOS
18 is the last release whose endpoints are arm64, and that a new port should
pick a device that meets the requirements and prefer the iOS or iPadOS 27
profile, whose drivers and patches are the ones under maintenance. Every
optimization in this repository is maintained against both 17 and 27 and is
selected by build parameter alone. sheng's current profile is recorded as
ipados-27.0.1-24A446, with the earlier 26.5.2 profile kept beside it.
Sm8550Platform gets its own page in both languages, and the repository table
lists it.
The device packaging script page defines the mandatory one-command script:
fixed steps, configuration read from TOML only, one shared script text, the
OS target passed as a parameter, and the two required outputs with their
manifest.