Repository navigation
platforms: migrate the Monaco/Lemans family boards to YAML - #194
Merged
Viswanath Kraleti (vkraleti) merged 6 commits intoOct 23, 2026
Merged
Viswanath Kraleti (vkraleti) merged 6 commits into
Viswanath Kraleti (vkraleti) merged 6 commits into
Conversation
The eMMC SKU becomes its own board directory, preparing for one YAML board file per flashable configuration: iq-9075-evk/emmc -> iq-9075-evk-emmc/emmc Pure renames; the checksum manifest is regenerated in the same commit - every hash is unchanged, only paths move. Downstream consumers referencing the old path need a matching update. [1] qualcomm-linux#124 Signed-off-by: Igor Opaniuk <igor.opaniuk@oss.qualcomm.com>
The eMMC and UFS layouts share 63 byte-identical partitions but list them in unrelated orders (the layouts are identical to iq-8275-evk's, so the same measurement applies: aligning the sequences takes 18 separate runs, the longest spanning 10 partitions). Shared partition fragments splice in as ordered runs, so with these orders the YAML migration could not reuse the qcs8275 sets. Reorder the eMMC user area to follow the UFS per-LUN grouping, exactly as done for iq-8275-evk; the boot area (cdt) is unchanged. This is a deliberate layout change: GPT offsets move, while the partition set, sizes, GUIDs and attributes stay identical. The checksum manifest is regenerated for the affected eMMC artifacts only. [1] qualcomm-linux#124 Signed-off-by: Igor Opaniuk <igor.opaniuk@oss.qualcomm.com>
Igor Opaniuk (igoropaniuk)
requested review from
Dmitry Baryshkov (lumag),
Nicolas Dechesne (ndechesne) and
Viswanath Kraleti (vkraleti)
as code owners
October 23, 2026 08:29
Monaco (qcs8275, qcs8300) and Lemans (qcs9075, qcs9100) share these layouts today but may deviate later, so the shared sets get the family name instead of the first adopter's: the qcs8275-* fragments become monaco-*, and lemans-* fragments alias them through a fragment-level include. One copy per partition still holds; when the families deviate, a lemans fragment replaces its include with explicit partitions and the Monaco boards do not move. The iq-8275-evk boards repoint to the Monaco set. Source-only: generated artifacts and the checksum manifest are unchanged. [1] qualcomm-linux#124 Signed-off-by: Igor Opaniuk <igor.opaniuk@oss.qualcomm.com>
One board file per flashable configuration: iq-9075-evk.yaml <- iq-9075-evk/ufs iq-9075-evk-emmc.yaml <- iq-9075-evk-emmc/emmc Both boards compose the shared Lemans partition sets from _common/ - the layouts match iq-8275-evk's apart from the UFS rootfs size, overridden in place in the lun 0 group. No new partition definitions are added. Artifacts and the checksum manifest are unchanged. [1] qualcomm-linux#124 Signed-off-by: Igor Opaniuk <igor.opaniuk@oss.qualcomm.com>
The UFS layout is identical to iq-8275-evk's, so the board file is a pure composition of the shared Monaco partition sets from _common/ - no partition definitions of its own. Artifacts and the checksum manifest are unchanged. [1] qualcomm-linux#124 Signed-off-by: Igor Opaniuk <igor.opaniuk@oss.qualcomm.com>
The UFS layout matches iq-8275-evk's apart from the rootfs size, so the board file composes the shared Lemans partition sets from _common/ and overrides the rootfs size in place in the lun 0 group - no partition definitions of its own. Artifacts and the checksum manifest are unchanged. [1] qualcomm-linux#124 Signed-off-by: Igor Opaniuk <igor.opaniuk@oss.qualcomm.com>
Igor Opaniuk (igoropaniuk)
force-pushed
the
feat/iq-9075-evk-yaml
branch
from
October 23, 2026 10:38
92fc8c2 to
5c95a6f
Compare
Viswanath Kraleti (vkraleti)
approved these changes
Oct 23, 2026
Viswanath Kraleti (vkraleti)
merged commit Oct 23, 2026
f89ed1c
into
qualcomm-linux:main
5 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migrates
iq-9075-evk(UFS and eMMC),qcs8300-ride-sxandqcs9100-ride-sxto YAML board definitions [1]. All four layouts matchiq-8275-evk's(#186) apart from the UFS rootfs size on the Lemansboards, so every board is a pure composition of the shared partition sets - no new partition definitions are added anywhere in this PR.Since the shared sets now serve two silicon families that may deviate later, a dedicated commit renames them along the family boundary:
qcs8275-*becomesmonaco-*(qcs8275,qcs8300), andlemans-*(qcs9075,qcs9100) aliases the Monaco sets through a fragment-level include - still one definition per partition, with a one-file edit as the deviation point if the families ever diverge. Theiq-8275-evkboards repoint to the Monaco names in the same commit.The commit structure otherwise follows #186: a pure-rename commit moves the
iq-9075-evkeMMC layout to its own board directory, then its eMMC user area is reordered to follow the UFS per-LUN grouping so the shared sets apply. The reorder is a deliberate layout change (GPT offsets move, partition set/sizes/GUIDs identical) and is the only commit changing artifacts and the checksum manifest; it deserves a flash test on an eMMC-booting board. All migration commits generate byte-identical artifacts with the manifest untouched.[1] #124