Releases: microsoft/mu_silicon_intel_tiano
v2024050000.0.1
What's Changed
-
[CHERRY-PICK] IntelSiliconPkg: Add IgdOpRegion32.h to support IGD OpRegion v3.2 @kenlautner (#238)
Change Details
## Description
Cherry-pick new IgdOpRegion32.h from edk2-platforms that are needed for newer platforms. The initial PR description is listed here:
- Backlight related fields in MBOX2 has uncalibrated brightness support
- Valid Bit added for BCL in MBOX2.
Cc: Rangasai V Chaganty [email protected]
Cc: Ashraf Ali S [email protected]
Cc: Ray Ni [email protected]For details on how to complete to complete these options and their meaning refer to CONTRIBUTING.md.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested
N/A - Just adding a header file
Integration Instructions
N/A
Full Changelog: v2024050000.0.0...v2024050000.0.1
Contributors
Assets 2
v2024050000.0.0
Initial Release notes of 202405 contain a full list of mu changes on top of edk2-stable202405
PR associated with the commit can be found at the bottom of the information pane reached by clicking on the commit hash
What's Changed## 🚀 Features & ✨ Enhancements
-
pip: Update all pip-requirements to latest (#236)
-
Repo File Sync: 202405 Branch Transition Updates. (#235)
-
IntelSiliconPkg: CodeQL Fixes.
-
IntelFsp2WrapperPkg: CodeQL Fixes.
-
SiltelFsp2Pkg: CodeQL Fixes.
-
Updated Release Notes. (#231)
-
IntelSiliconPkg: Add FitQueryLib. (#229)
-
IntelSiliconPkg: Add BaseSmmAccessLibNull
-
Fixing CI break for new version of mu_tiano_plus. (#225)
-
Delay IOMMU Install until DMAR is available
-
Add stuart path_env for FSP tools
-
IntelSiliconPkg/PeiSmmAccessLibSmramc: Use consistent integer width
-
Temporary: Disable CodeQL
-
Enable CI
-
Mu compiler fixes
-
Mu DSC Changes
-
Fix line endings in repo
-
IntelSiliconPkg: Apply Uncrustify
-
Updated readme for latest MU release and to match conventions
-
TCMORPH: Remove unused packages from Tiano (command in comments).
-
Merge branch 'upstream-edk2-platforms' into upstream
-
Silicon/Intel/FitGen：FIT change for FBM entry.
-
IntelSiliconPkg/VTd: Reset the one-shot bits before modifing GCMD_REG
-
IntelSiliconPkg/VTd: Remove ASSERT in VTdSetAttribute
-
Merge commit '3e722403cd16388a0e4044e705a2b34c841d76ca' into upstream
-
Merge branch 'upstream-edk2-platforms' into upstream
-
IntelSiliconPkg/VTd: Print Flags field in DeviceScopeEntry
-
IntelSiliconPkg/Vtd: fix incorrect number of arguments
-
IntelSiliconPkg/VTd: Print Flags field in DeviceScopeEntry
-
IntelSiliconPkg/Vtd: fix incorrect number of arguments
-
Merge branch 'upstream-edk2-platforms' into upstream
-
IntelSiliconPkg/Vtd: Resolve parameter transfer errors
-
IntelSiliconPkg: Add gEndOfSiInitPpiGuid definition in DEC file
-
IntelSiliconPkg/SpiFvbService: Non-functional cleanup
-
IntelSiliconPkg/VTd: Fix wrong parameter type in VtdLog.c
Change Details
&nbs...
v2023110000.0.0
What's Changed
First 202311 Mu Silicon Intel Tiano release 🎉.
-
[Rebase \& FF] [Cherry-pick] Get all the missing commits from 202302 into 202311 @kenlautner (#178)
Change Details
## Description
Cherry-pick the commits from 202302 that are missing from 202311 since the creation of the release branch.
- Impacts functionality?
- Functionality - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- Impacts security?
- Security - Does the change have a direct security impact on an application,
flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- Security - Does the change have a direct security impact on an application,
- Breaking change?
- Breaking change - Will anyone consuming this change experience a break
in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- Breaking change - Will anyone consuming this change experience a break
- Includes tests?
- Tests - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
- Documentation - Does the change contain explicit documentation additions
outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
CI
Integration Instructions
N/A
- Impacts functionality?
-
Updated CISettings.py to use the edk2toolext codeql helpers @kenlautner (#170)
Change Details
## Description
The 202311 rebase moved the codeql plugin from .pytool to Basetools. This requires a change in CISettings.py to reference the correct codeql helper functions. Instead of using the internal versions we instead move to the edk2 pytool extensions version.
For each item, place an "x" in between
[and]if true. Example:[x].
(you can also check items in the GitHub UI)- Impacts functionality?
- Functionality - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- Impacts security?
- Security - Does the change have a direct security impact on an application,
flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- Security - Does the change have a direct security impact on an application,
- Breaking change?
- Breaking change - Will anyone consuming this change experience a break
in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- Breaking change - Will anyone consuming this change experience a break
- Includes tests?
- Tests - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
- Documentation - Does the change contain explicit documentation additions
outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
Tested with CI.
Integration Instructions
N/A
- Impacts functionality?
Full Changelog: ...v0.1.0
Contributors
Assets 2
v2023020000.0.4
What's Changed
-
Update pip-requirements.txt @Javagedes (#175)
Change Details
## Description
Updates edk2-pytool-extensions and edk2-pytool-library to work with the latest commit of MU_BASECORE
For each item, place an "x" in between
[and]if true. Example:[x].
(you can also check items in the GitHub UI)- Impacts functionality?
- Functionality - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- Impacts security?
- Security - Does the change have a direct security impact on an application,
flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- Security - Does the change have a direct security impact on an application,
- Breaking change?
- Breaking change - Will anyone consuming this change experience a break
in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- Breaking change - Will anyone consuming this change experience a break
- Includes tests?
- Tests - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
- Documentation - Does the change contain explicit documentation additions
outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
N/A
Integration Instructions
N/A
- Impacts functionality?
-
.git-blame-ignore-revs: Ignore Line Ending and Uncrustify only commits @makubacki (#167)
Change Details
## Description
Adds commits that only applied Uncrustify formatting or converted
line endings to a .git-blame-ignore-revs file so they are ignored
by git blame. This is supported by GitHub:
https://github.blog/changelog/2022-03-24-ignore-commits-in-the-blame-view-beta/This helps clean up git blame by filtering out these changes.
Note: This file needs to be updated on rebase branches. Processes
like filter-branch can automatically update relevant SHAs.- Impacts functionality?
- Functionality - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- Impacts security?
- Security - Does the change have a direct security impact on an application,
flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- Security - Does the change have a direct security impact on an application,
- Breaking change?
- Breaking change - Will anyone consuming this change experience a break
in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- Breaking change - Will anyone consuming this change experience a break
- Includes tests?
- Tests - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
- Documentation - Does the change contain explicit documentation additions
outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
git blame
Integration Instructions
N/A
- Impacts functionality?
Full Changelog: v2023020000.0.3...v2023020000.0.4
Contributors
Assets 2
v2023020000.0.3
What's Changed
🔐 Security Impacting
-
Use New Stack Cookie Library @TaylorBeebe (#151)
Change Details
## Description
MdePkg/MdeLibs.dsc.inc contains the definitions for the new stack cookie libraries.
- Impacts functionality?
- Functionality - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- Impacts security?
- Security - Does the change have a direct security impact on an application,
flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- Security - Does the change have a direct security impact on an application,
- Breaking change?
- Breaking change - Will anyone consuming this change experience a break
in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- Breaking change - Will anyone consuming this change experience a break
- Includes tests?
- Tests - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
- Documentation - Does the change contain explicit documentation additions
outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
Tested on Q35 GCC and MSVC builds
Integration Instructions
N/A
- Impacts functionality?
Full Changelog: v2023020000.0.2...v2023020000.0.3
Contributors
Assets 2
v2023020000.0.2
What's Changed
-
[CHERRY-PICK] IntelFsp2Pkg: Remove UefiCpuLib from module INFs. @srilathasridharan (#124)
Change Details
## Description
[CHERRY-PICK] IntelFsp2Pkg: Remove UefiCpuLib from module INFs.
Because UefiCpuPkg/UefiCpuLib is merged to MdePkg/CpuLib, remove the dependency of UefiCpuLib.
Cc: Chasel Chiu [email protected]
Cc: Nate DeSimone [email protected]
Cc: Star Zeng [email protected]Reviewed-by: Chasel Chiu [email protected]
- Impacts functionality?
- Functionality - No
- Impacts security?
- Security - No
validation improvement, ...
- Security - No
- Breaking change?
- Breaking change - No
- Includes tests?
- Tests - None
- Includes documentation?
- Documentation - No
How This Was Tested
Builds MTL FSP package.
Integration Instructions
N/A
- Impacts functionality?
Full Changelog: v2023020000.0.1...v2023020000.0.2
Contributors
Assets 2
v2023020000.0.1
What's Changed
-
Update pipeline builds for selfhosted Azure agents @kuqin12 (#91)
Change Details
# Preface
Please ensure you have read the contribution docs prior
to submitting the pull request. In particular,
pull request guidelines.Description
This change updated the mu_devops to use the Jobs/PrGate.yml pipeline and update synchronization files.
For each item, place an "x" in between
[and]if true. Example:[x].
(you can also check items in the GitHub UI)- Impacts functionality?
- Functionality - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- Impacts security?
- Security - Does the change have a direct security impact on an application,
flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- Security - Does the change have a direct security impact on an application,
- Breaking change?
- Breaking change - Will anyone consuming this change experience a break
in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- Breaking change - Will anyone consuming this change experience a break
- Includes tests?
- Tests - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
- Documentation - Does the change contain explicit documentation additions
outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
This was tested on selfhost-agents and existing agents.
Integration Instructions
Pipeline changes, N/A for integration.
</blockquote> <hr> </details> - Impacts functionality?
-
REBASE: Re-remove the codeql workflow @kenlautner (#95)
Change Details
## Description
Removed CodeQL workflows that were accidentally included in the rebase.
For each item, place an "x" in between
[and]if true. Example:[x].
(you can also check items in the GitHub UI)- Impacts functionality?
- Functionality - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- Impacts security?
- Security - Does the change have a direct security impact on an application,
flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- Security - Does the change have a direct security impact on an application,
- Breaking change?
- Breaking change - Will anyone consuming this change experience a break
in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- Breaking change - Will anyone consuming this change experience a break
- Includes tests?
- Tests - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
- Documentation - Does the change contain explicit documentation additions
outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
N/A
Integration Instructions
N/A
</blockquote> <hr> </details> - Impacts functionality?
🔐 Security Impacting
-
IntelSiliconPkg/PeiSmmAccessLibSmramc: Use consistent integer width i… @makubacki (#105)
Change Details
Fixes #104
Updates the code in this library instance (
PeiSmmAccessLibSmramc)
to have the same integer width fixes already in the other library
instance (PeiSmmAccessLib).Resolves CodeQL Rule ID
cpp/comparison-with-wider-type:In a loop condition, comparison of a value of a narrow type with a
value of a wide type may result in unexpected behavior if the wider
value is sufficiently large (or small). This is because the
narrower value may overflow. This can lead to an infinite loop.- Impacts functionality?
- Functionality - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- Impacts security?
- Security - Does the change have a direct security impact on an application,
flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- Security - Does the change have a direct security impact on an application,
- Breaking change?
- Breaking change - Will anyone consuming this change experience a break
in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- Breaking change - Will anyone consuming this change experience a break
- Includes tests?
- Tests - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
- Documentation - Does the change contain explicit documentation additions
outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
Build IntelSiliconPkg. Change is already in equivalent library instance.
Integration Instructions
N/A
- Impacts functionality?
Full Changelog: v2023020000.0.0...v2023020000.0.1
Contributors
Assets 2
v2023020000.0.0
What's Changed
This is the first MU Silicon Intel Tiano 202302 release 🎉
The previous branch was 202208.
These versions correspond to edk2 stable release tags that the code is based upon.
Since edk2 makes a release every 3 months, two stable tags were actually picked up in this release:
Review those release notes to understand the changes coming in from edk2. In addition, Mu repos highlight important changes in their Readme files. Review the 202302 Readme before you move code to this branch to understand major changes.