phase30: productize XArch validation and UiApp replacement path#23
Merged
Conversation
新增 Phase30 XArch/productization validation matrix，覆盖 X64、AARCH64、LOONGARCH64、RISCV64 的产品化验证状态与 App/provider 边界。 同步 README、Docs、Tests 文档入口，并扩展 smoke gate 检查 XArch 不替代 edk2 ARCH、native HII/FormBrowser/ConfigAccess ownership、Hardware Health demo-only/read-only、ModernUiPreferencesLib app-owned preferences，以及 PCIe native policy 边界。 Validation: - python3 Tests/Smoke/smoke_validate.py - Scripts/xarch-validate.sh --all --mode dry-run --format markdown - Scripts/xarch-validate.sh --all --mode dry-run --format json - git diff --check
Add a LoongArchVirt opt-in path that provides the UiApp/Firmware Setup FFS GUID with ModernSetupApp while keeping native BootManagerMenuApp responsible for Boot#### launch.\n\nThe replace-UiApp overlay keeps PcdBootManagerMenuFile on the native UiApp GUID, includes BootManagerMenuApp in the FV, and lets ModernSetupApp hand off boot launch to the native manager. Smoke validation now checks the generated overlay contract.\n\nValidation:\n- python3 Tests/Smoke/smoke_validate.py\n- git diff --check\n- MODERN_SETUP_REPLACE_UIAPP=1 MODERN_SETUP_DISPLAY_ENGINE=modern Scripts/build-loongarchvirt.sh
Replace the old OVMF dashboard display with a Graphite Gold themed ModernSetupApp homepage capture and update the English and Chinese README wording to match.\n\nValidation:\n- ARCH=X64 Scripts/build-modern-app.sh\n- Scripts/build-ovmf-x64.sh\n- QEMU screendump capture via Scripts/capture-ovmf-x64.sh\n- git diff --check
MarsDoge
changed the title
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
1 participant
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.
Summary
MODERN_SETUP_REPLACE_UIAPP=1build mode where ModernSetupApp provides the UiApp/Firmware Setup frontend while native BootManagerMenuApp remains responsible for Boot#### launch.Architecture note
BootManagerMenuAppkeeps native Boot#### launch semantics;ModernSetupAppreplaces/augmentsUiApp/ Firmware Setup as the modern front-page UI.PcdBootManagerMenuFileon the native UiApp GUID and keeps native BootManagerMenuApp in the FV.Validation
python3 Tests/Smoke/smoke_validate.py: PASSgit diff --check: PASSMODERN_SETUP_REPLACE_UIAPP=1 MODERN_SETUP_DISPLAY_ENGINE=modern Scripts/build-loongarchvirt.sh: PASSARCH=X64 Scripts/build-modern-app.sh: PASSScripts/build-ovmf-x64.sh: PASSAssets/Screenshots/modern-ovmf-x64-dashboard-graphite-gold.png: PASS, 1280x800 PNGManual validation