v2024050000.0.2

What's Changed

• Make PlatformInitPreMem independent to IntelSiliconPkg and IntelFsp2WrapperPkg @PaddyDengKC (#293)
  
  Change Details

    ## Description

  This driver is shared across different Silicon vendors. So it should not use any Intel specific packages.

  In order to achieve this, added a new lib FspSupportLib to isolate silicon related PCDs

  • 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, ...
  • 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, ...
  • 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, ...

  How This Was Tested

  CI build passed.

  Integration Instructions

  No additional change is required for the consuming platforms.
  

  
  

  ---

  
  

• MinPlatformPkg SerialPortTerminalLib: Fixing CodeQL issue Pointless comparison of unsigned value to zero (#282)
  
  Change Details

    ## Description

  Description

  Cherry-pick Commit 03664aa #282 from release/202311 to dev/202405.
  CodeQL is reporting Pointless comparison of unsigned value to zero for a value derived from an unsigned PCD PcdDefaultTerminalType.

  For details on how to complete these options and their meaning refer to CONTRIBUTING.md.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?
  • Backport to release branch?

  How This Was Tested

  Ran Local CI including codeQL setting and pipeline codeQL build.

  Integration Instructions

  N/A

  upstream repo in EDK2?

  tianocore/edk2-platforms#246
  

  
  

  ---

  
  

Full Changelog: v2024050000.0.1...v2024050000.0.2

v2024050000.0.1

What's Changed

• [CHERRY-PICK] BoardModulePkg: Added Mock library for BiosIdLib @v-bhavanisu (#305)
  
  Change Details

    ## Description Added a gmock for GoogleTests that pull in BiosIdLib.

  Cherry picked from dev/202405

  e566d57

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  Consumed mock in GoogleTest

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

• [Cherry-Pick] Add Standalone Mm BiosIdLib and format code with Uncrus… @apop5 (#306)
  
  Change Details

    ## Description [Cherry-Pick] Add Standalone Mm BiosIdLib and format code with Uncrustify.

  Cc: Eric Dong [email protected]
  Reviewed-by: Nate DeSimone [email protected]

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  N/A

  Integration Instructions

  N/A
  

  
  

  ---

  
  

Full Changelog: v2024050000.0.0...v2024050000.0.1

v2023110000.0.2

What's Changed

• MinPlatformPkg SerialPortTerminalLib: Fixing CodeQL issue Pointless comparison of unsigned value to zero. @apop5 (#282)
  
  Change Details

    ## Description

  CodeQL is reporting Pointless comparison of unsigned value to zero for a value derived from an unsigned PCD PcdDefaultTerminalType.

  • 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, ...
  • 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, ...
  • 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, ...

  How This Was Tested

  Ran Local CI.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• [CHERRY-PICK] MinPlatformPkg/Test: Fix DumpAcpiMadt infinite loop @srilathasridharan (#266)
  
  Change Details

    ## Description

  Update the MadtLen varaible before the next record is read, to avoid infinite loop.

  Cc: Chasel Chiu [email protected]
  Reviewed-by: Nate DeSimone [email protected]
  Cc: Liming Gao [email protected]
  Cc: Eric Dong [email protected]

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  N/A

  Integration Instructions

  N/A
  

  
  

  ---

  
  

Full Changelog: v2023110000.0.1...v2023110000.0.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 (#289)
  
  Change Details

    5665f25

  ---

• REBASE: Update Readme and CISettings for 202405
  
  Change Details

    f389bc4

  ---

• Removed OpensslLib and IntrinsicLib libraries
  
  Change Details

    6b114d4

  ---

• pip: Update all requirements (#49)
  
  Change Details

    ca4fb3f

  ---

• [REBASE&FF] Repo File Sync: Enable code coverage uploads to codecov (#214)
  
  Change Details

    61e1fb2

  ---

• REBASE: Updated Readme for the 202311 release
  
  Change Details

    2bee5da

  ---

• Update TestPoint ID for TestPointLibAppendErrorString() (#203)
  
  Change Details

    df15c3a

  ---

• Update TestPointStubDxeMm to correctly print MM test results when using Standalone MM. (#176)
  
  Change Details

    dfc9815

  ---

• Convert files in repo to CRLF
  
  Change Details

    863b996

  ---

• AcpiPlatform.c Codeql fixes (#185)
  
  Change Details

    c43bc6e

  ---

• MinPlatformPkg: Update X_GPE1_BLK AddressSpaceId with PCD value (#177)
  
  Change Details

    0e43c35

  ---

• ci.yaml: add PrEval entry (#169)
  
  Change Details

    6f3b117

  ---

• Fixing CodeQL issues in AcpiPlatform.c (#129)
  
  Change Details

    f9c750d

  ---

• [Cherry-Pick] MinPlatformPkg: Fix array indexing issue (#115)
  
  Change Details

    d2fbdca

  ---

• Add CodeQL Stuart parameter to this repo (#109)
  
  Change Details

    9b447fd

  ---

• MinPlatformPkg.dsc: Add stack cookie support libs (#110)
  
  Change Details

    8cb989c

  ---

• Add scheduled maintenance workflow (#92) (#94)
  
  Change Details

    d6791bc

  ---

• Convert line endings from LF to CRLF (#92)
  
  Change Details

    df2c2ba

  ---

• Added BoardModulePkg (#82)
  
  Change Details

    b6a31f2

  ---

• Enable Label Sync GitHub Action
  
  Change Details

    3f1af2f

  ---

• Enable stale bot GitHub Action
  
  Change Details

    478088d

  ---

• MinPlatformPkg: Ignore line endings (#60) (#70)
  
  Change Details

    9911dd5

  ---

• Add Dependabot (#44)
  
  Change Details

    bee5bfa

  ---

• Add Standalone MM test point support (#40)
  
  Change Details

    4042ae6

  ---

• Add TestPointPciEnumerationDonePcieGenSpeed to TestPointCheckLibNull.c (#42)
  
  Change Details

    f41d49d

  ---

• Adding PCI Speed Testpoint (#41)
  
  Change Details

    2f26054

  ---

• Add option to compress the FspNvsBuffer var to reduce varstore usage. (#39)
  
  Change Details

    04f4c7f

  ---

• Add support for minimum memory type allocations to DxeCheckMemoryTypeInformation
  
  Change Details

    bd7ef7e

  ---

• Add support for reporting minimum allocation HOB for memory type info
  
  Change Details

    9fce6da

  ---

• Handle scenarios around transitioning to this implementation from older implementations (#37)
  
  Change Details

    b80d6f4

  ---

• MinPlatformPkg/SmmMultiBoardAcpiSupportLib: Use MmServicesTableLib (#35)
  
  Change Details

    05a28cf

  ---

• CHERRY_PICK: [TCBZ3541] MinPlatformPkg/TestPointCheckLib: Add support for BME device exemption
  
  Change Details

    d65511e

  ---

• CHERRY_PICK: MinPlatformPkg/PlatformConfigCheckLibNull: Fix LIBRARY_CLASS name (#20)
  
  Change Details

    ed2743f

  ---

• CHERRY_PICK: Implement a Dxe TestPoint library to allow for Platform specific tests
  
  Change Details

v2023110000.0.1

What's Changed

• [CHERRY-PICK] Add StackCheckLib Instances to Platform DSC Files (#251) @TaylorBeebe (#253)
  
  Change Details

    ## Description

  An instance of StackCheckLib must be in each DSC to accommodate -fstack-protector and /GS flags.

  • 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, ...
  • 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, ...
  • 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, ...

  How This Was Tested

  Tested in pipelines

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• remove edk2-basetools @Javagedes (#246)
  
  Change Details

    ## Description

  Removes edk2-basetools from pip-requirements.txt and any usage of it in the CISettings.py. The is done as there are changes in the build tools python source code that are available locally in BaseTools (as it is managed by Project Mu) that is not available in edk2-basetools.

  • 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, ...
  • 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, ...
  • 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, ...

  How This Was Tested

  Verified the build system continues to use the local python source

  Integration Instructions

  N/A - only effects this repository's CI system.
  

  
  

  ---

  
  

Full Changelog: v2023110000.0.0...v2023110000.0.1

v2023020000.0.8

What's Changed

• Update pip-requirements.txt @Javagedes (#237)
  
  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, ...
  • 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, ...
  • 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, ...

  How This Was Tested

  N/A

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• Removed references to openssllib and it's associated libraries @kenlautner (#230)
  
  Change Details

    ## Description

  There are some references to BaseCryptLib and Openssl in package dsc files. In MU_BASECORE Openssl and its BaseCryptLib implementations were removed so we need to update to using the NULL lib.

  • 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, ...
  • 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, ...
  • 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, ...

  How This Was Tested

  Tested with CI

  Integration Instructions

  N/A
  

  
  

  ---

  
  

Full Changelog: v2023020000.0.7...v2023020000.0.8

v2023110000.0.0

First 202311 Mu Common Min Platform release 🎉.

v2023020000.0.7

What's Changed

🔐 Security Impacting

• Use New Stack Cookie Library @makubacki (#219)
  
  Change Details

    ## Description

  MinPlatformPkg/Include/CoreCommonLib.dsc includes MdePkg/MdeLibs.dsc.inc
  to bring in the new stack cookie library instances from there.

  • 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, ...
  • 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, ...
  • 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, ...

  How This Was Tested

  • MinPlatformPkg build and CI

  Integration Instructions

  • N/A
    

  
  

  ---

Full Changelog: v2023020000.0.6...v2023020000.0.7

v2023020000.0.6

What's Changed

• Update TestPoint ID for TestPointLibAppendErrorString() @Ken-Pong (#203)
  
  Change Details

    ## Description

  Update TestPoint ID when TestPointLibAppendErrorString() is executed, otherwise error string will not be recorded correctly.

  • 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, ...
  • 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, ...
  • 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, ...

  How This Was Tested

  Test on different silicon families and check error string can be recorded correctly when verified error happens.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

Full Changelog: v2023020000.0.5...v2023020000.0.6

v2023020000.0.5

What's Changed

• Update TestPointStubDxeMm to correctly print MM test results when using Standalone MM. @kenlautner (#176)
  
  Change Details

    ## Description

  Currently when running the TestPointDump efi from the uefi shell only PEI and DXE results will be printed out when using Standalone MM. This change fixes the issue where the memory that stored the SMM testing results structure consumed by TestPointDump wasn't being created.

  This is due to the memory pages being blocked by MM and then trying to use them in the MM user data buffer. This change unwinds that buffer as it's essentially a pointer in the MM comm buffer. Now we use the comm buffer itself to store the MM test point data that we report through the TestPointStubDxeMm driver.

  Additionally, identifiers are now being used in the tests when updating verified features to fill the correct phase data structure. This makes test reporting in the dump app more clear.

  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, ...
  • 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, ...
  • 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, ...

  How This Was Tested

  Tested on several different silicon families using Standalone MM. The MM test results are now being correctly published.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

Full Changelog: v2023020000.0.4...v2023020000.0.5