Skip to content

Releases: microsoft/mu_tiano_platforms

v2.3.0

01 May 20:18
636090d
Compare
Choose a tag to compare

What's Changed

🚀 Features & ✨ Enhancements

  • Remove MorLockTestApp from Q35 and SBSA @TaylorBeebe (#511)
    Change Details
      ## Description

    Remove MorLockTestApp from Q35 and SBA and link bugzilla related to the omission reason.

    • 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




  • Enable Advanced Logger in DXE on Q35 @TaylorBeebe (#506)
    Change Details
      ## Description

    Adds Project Mu's Advanced Logger functionality to Q35.

    An issue has been created to enable Advanced Logger in MM and PEI: #522

    • 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

    Booting on Q35

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    

🛠️ Submodule Updates

  • Bump Features/DFCI from 2.3.1 to 3.0.0 @ProjectMuBot (#527)
    Change Details
      Bumps Features/DFCI from `2.3.1` to `3.0.0`

    Introduces 11 new commits in Features/DFCI.

    Commits
    • 6fcec9 Repo File Sync: synced file(s) with microsoft/mu_devops (#59)
    • a8afe5 Repo File Sync: synced file(s) with microsoft/mu_devops (#82)
    • 9d9b73 pip: bump edk2-pytool-library from 0.14.0 to 0.14.1 (#68)
    • 725ce1 pip: bump edk2-basetools from 0.1.40 to 0.1.43 (#79)
    • da81bb pip: bump edk2-pytool-extensions from 0.22.2 to 0.23.0 (#85)
    • c8d699 Repo File Sync: Update to Mu DevOps 2.4.0 (#86)
    • cde24e pip: bump edk2-basetools from 0.1.43 to 0.1.44 (#87)
    • f01e1c pip: bump edk2-basetools from 0.1.44 to 0.1.45 (#88)
    • 507a1a Repo File Sync: Update Fedora 37 container f1c7a20 from to 3b3eb8f (#89)
    • f6b55c Repo File Sync: Always publish logs in CodeQL workflow, fix container safe dir, add issue assignment workflow (#90)
    • 3bfb66 Dfci support for using a QemuQ35Pkg virtual system as the device under test (#84)

    Signed-off-by: Project Mu Bot [email protected]




Full Changelog: v2.2.0...v2.3.0

v2.2.0

28 Apr 22:54
63d0de1
Compare
Choose a tag to compare

What's Changed

  • Add platform libraries DfciDeviceIdSupportLib and DfciUiSupportLib @mikeytdisco (#471)
    Change Details
      ## Description

    Fixes #470

    Dfci requires the platform to supply a couple of libraries. The following libraries are added to Qemu package:

    DfciDeviceIdSupportLib
    DfciUiSupportLib

    and replacing the Null libraries used in the QemuQ35Pkg.dsc file.

    For each item, place an "x" in between [ and ] if true. Example: [x].
    (you can also check items in the GitHub UI)

    • Impacts functionality?

      • Yes, it impacts functionality by enabling Dfci to work in Qemu.
    • Impacts security?

    • Breaking change?

    • Includes tests?

    • Includes documentation?

    How This Was Tested

    Tested in a QemuQ35Pkg test system.

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    
  • Transition virtual drive functionality to a Helper Plugin @Javagedes (#475)
    Change Details
      ## Description

    With the creation of QemuSbsaPkg, nearly all of the Virtual hard drive functionality (hard drive management, test management, startup script management) had to be duplicated between QemuSbsaPkg and QemuQ35Pkg. This commit moves all of this functionality into a plugin found under QemuPkg/Plugins/VirtualDriveManager for maintainabilities sake.

    Additionally provides some QOL improvements:

    1. Error handling RunCmd's use for managing virtual drives
    2. Displaying debug information to the user on CLI settings
    3. Checking if a test has been run so the image does not need to be loaded and executed before being skipped. (An issue for tests that reset)
    4. Updated the way we ignore exempt tests to make it more comprehensible.
    5. Used RunCmd rather than popen for finding the unused drive on a linux system
    6. Check the result of grep rather than the output of grep as it will return 0/1/2 for files_found/no_files_found/error occurred (respectively).
    7. Set the virtual drive path in SetPlatformEnvAfterTarget rather then in FlashRom

    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

    Verified testing continued to work on Windows/Linux QemuQ35Pkg and Linux QemuSbsaPkg

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    
  • Add Configuration Profiles to QemuQ35Pkg @os-d (#507)
    Change Details
      # Preface

    Please ensure you have read the contribution docs prior
    to submitting the pull request. In particular,
    pull request guidelines.

    Description

    Add two dummy configuration profiles to QemuQ35Pkg as a proof of concept of the configuration profile feature. These profiles are controlled by gOemPkgTokenSpaceGuid.PcdActiveProfileIndex. Full details are in mu_feature_config's profiles doc.

    This defaults to using profile 1, which enables GFX and sets some dummy values.

    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 by booting QemuQ35Pkg to different profiles and dumping via ConfApp to see the knobs change.

    Integration Instructions

    N/A.

      </blockquote>
      <hr>
    </details>
    

🚀 Features & ✨ Enhancements

  • Add FrontPageButtons to QemuQ35Pkg @mikeytdisco (#473)
    Change Details
      Add the smbios FrontPageButton driver

    Description

    Add the driver that maps the Type3.version Smbios data to the respective Vol+ or Vol- action.

    One PR for #472

    For each item, place an "x" in between [ and ] if true. Example: [x].
    (you can also check items in the GitHub UI)

    • Impacts functionality?

    • Impacts security?

    • Breaking change?

    • Includes tests?

    • Includes documentation?

    How This Was Tested

    Tested on a Q35 system

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    

🛠️ Submodule Updates

  • Bump MU\_BASECORE from 2022080001.2.2 to 2022080001.4.1 @ProjectMuBot (#524)
    Change Details
      Bumps MU_BASECORE from `2022080001.2.2` to `2022080001.4.1`

    Introduces 12 new commits in MU_BASECORE.

    Commits
    • 9fdb5b pip: bump edk2-basetools from 0.1.43 to 0.1.44 (#373)
    • 0df8a0 Adding base tool build for Linux ARM (#362)
    • fef5df pip: bump edk2-basetools from 0.1.44 to 0.1.45 (#377)
    • 4face8 Add Windows ARM 64-bit base tools (#376)
    • a98f55 Mark NonDiscoverablePciDeviceIo Memory XP By Default (#374)
    • 3d7ad1 Updated Base Crypto Version to 2022.8.6 (#365)
    • 8211df Revert #168. Move changes into Terminal driver"s Terminal ConIn. (#378)
    • cad30b [CHERRY-PICK] BaseTools/Plugin: Clarify code coverage failure message (#375)
    • c51f3d Updated Crypto Tests (#372)
Read more

v2.1.0

25 Apr 02:11
e5bc3be
Compare
Choose a tag to compare

What's Changed

  • Publish "No SMM" Q35 binaries on release @makubacki (#515)
    Change Details
      ## Description

    Resolves #513

    Updates the release process to also include the QemuQ35Pkg binaries built without SMM.

    • 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

    PR gates and test release on fork.

    Integration Instructions

    N/A - Affects release publication




🐛 Bug Fixes

  • Fix DeviceIdTest on Q35 and SBSA @TaylorBeebe (#512)
    Change Details
      ## Description

    To fix the DeviceIdTestApp, SMBIOS Type 3 needed to be added to the qemu run command. The version field is based on the release tag for the mu_tiano_platforms repo.

    • 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

    DeviceIdTestApp building and passing on Q35 and SBSA

    Integration Instructions

    N/A




Full Changelog: v2.0.0...v2.1.0

v2.0.0

24 Apr 22:15
57e90f7
Compare
Choose a tag to compare

What's Changed

  • Update release pipeline for refactor @makubacki (#459)
    Change Details
      ## Description

    Fixes #465

    • Updates the Release.yml pipeline to accommodate the recent refactor
      in mu_tiano_platforms.
    • Updates some versions used in related YAML files to latest.
    • Makes the Job ID in Platform-Build-Job.yml unique so it can be
      invoked multiple times from a single stage.
    • Relies entirely upon the tool_chain_tag parameter in
      Platform-Build-Job.yml to remove assumptions about pipeline
      variables in the environment (which allows the file to be reused
      across different values of the variables) in the same stage.

    Note: Some versions (like Linux container image) are directly
    specified in Release.yml. The file will be synced fom mu_devops
    in the future to reuse the single definition for these versions
    maintained 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

    Mu Tiano Platforms fork.

    Integration Instructions

    N/A - Release pipeline for this repo.




  • Enable features used by the Windows hypervisor @cfernald (#496)
    Change Details
      ## Description

    Enables access to the HCRX register and functionality which is used by the Windows hypervisor. For information on this flag and feature see, https://trustedfirmware-a.readthedocs.io/en/latest/getting_started/build-options.html.

    Launching the Windows hypervisor in SBSA requires fixes coming in QEMU 8.0 and Windows fixes whose release build is not yet determined.

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

    How This Was Tested

    Manually tested locally.

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    
  • Update Build-UefiExt.yaml to publish on manual action. @cfernald (#497)
    Change Details
      ## Description

    Updates Build-UefiExt.yaml to upload the dll artifact on manual runs to allow manual refresh of binary.

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

    How This Was Tested

    N/A

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    
  • pip: bump xmlschema from 2.2.2 to 2.2.3 @dependabot (#491)
    Change Details
      Bumps [xmlschema](https://github.com/sissaschool/xmlschema) from 2.2.2 to 2.2.3.
    Release notes

    Sourced from xmlschema's releases.

    v2.2.3 (2023-04-14)

    • Add support for Python 3.12
    • Detach content iteration methods from ModelVisitor
    Changelog

    Sourced from xmlschema's changelog.

    v2.2.3_ (2023-04-14)

    • Add support for Python 3.12
    • Detach content iteration methods from ModelVisitor
    Commits
    • bc42319 Bump release and update CHANGELOG
    • 7c772c2 Add Python 3.12 support and update static typing checks
    • 62e317e Refactor _PurePath to not use PurePath internals
    • c9548da Add a test with a resolution for issue #341
    • 7a842ce Clean model check and processing
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Read more

v1.1.4

25 Mar 00:25
7f7cd14
Compare
Choose a tag to compare

What's Changed

  • pip: bump regex from 2022.10.31 to 2023.3.23 @dependabot (#443)
    Change Details
      Bumps [regex](https://github.com/mrabarnett/mrab-regex) from 2022.10.31 to 2023.3.23.
    Commits
    • 15cbd1e Git issue 495: Running time for failing fullmatch increases rapidly with inpu...
    • 5954c51 Git issue 494: Backtracking failure matching regex ^a?(a?)b?c\1$ against st...
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

  • Enable graphics for dev container @cfernald (#441)
    Change Details
      ## Description

    Enabled the graphics through the hosts WSL x11 graphics.

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

    How This Was Tested

    Tested on local container setup.

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    

🛠️ Submodule Updates

  • Bump Features/CONFIG from `01528fa` to `ab9501f` @dependabot (#433)
    Change Details
      Bumps [Features/CONFIG](https://github.com/microsoft/mu_feature_config) from `01528fa` to `ab9501f`.
    Commits
    • ab9501f pip: bump edk2-basetools from 0.1.29 to 0.1.40 (#137)
    • 496ecf1 Repo File Sync: .devcontainer: Update from Fedora 35 to Fedora 37 image (#139)
    • 9ec8e94 Unify pip-requirements from tools and base repo (#140)
    • e59678c Repo File Sync: Sync CodeQL workflow to additional repos (#138)
    • See full diff in compare view

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

  • Bump Silicon/Arm/MU\_TIANO from `54bd48c` to `17f0637` @dependabot (#432)
    Change Details
      Bumps [Silicon/Arm/MU_TIANO](https://github.com/microsoft/mu_silicon_arm_tiano) from `54bd48c` to `17f0637`.
    Commits
    • 17f0637 pip: bump edk2-basetools from 0.1.29 to 0.1.40 (#72)
    • 9c3bd96 Fixing truncated affinity value when constructing SGI values (#78)
    • a5e1bd8 Repo File Sync: Update from Fedora 35 to Fedora 37 image (#77)
    • See full diff in compare view

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

  • ...
Read more

v1.1.3

18 Mar 00:55
22b2223
Compare
Choose a tag to compare

What's Changed

  • .pytool/CISettings: Return all package paths @makubacki (#426)
    Change Details
      ## Description

    While only the NO-TARGET and NOOPT targets are active in the CI
    settings file, plugins active for those targets can depend on the
    package paths to accurately represent the workspace.

    Current package paths returned in GetPackagesPath():

    • Platforms
    • MU_BASECORE
    • Common/MU_TIANO
    • Common/MU
    • Common/MU_OEM_SAMPLE

    Current submodules returned in GetRequiredSubmodules():

    • MU_BASECORE
    • Common/MU_TIANO
    • Common/MU
    • Common/MU_OEM_SAMPLE
    • Silicon/Arm/MU_TIANO
    • Silicon/Arm/TFA
    • Features/DFCI
    • Features/CONFIG
    • Features/MM_SUPV

    A more complete and accurate list of package paths can be maintained
    over time by simply using the submodule list + the Platforms
    directory.

    • 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

    PR gates.

    Integration Instructions

    N/A

    Signed-off-by: Michael Kubacki [email protected]




  • Add Gfx Config to QemuSbsaPkg and Split QemuSbsaPkg and QemuQ35Pkg Video Drivers @os-d (#419)
    Change Details
      # Preface

    Please ensure you have read the contribution docs prior
    to submitting the pull request. In particular,
    pull request guidelines.

    Description

    This integrates the latest mu_feature_config changes to QemuSbsaPkg, as was done for QemuQ35Pkg. This also reenables GFX for QemuSbsaPkg, which was disabled.

    The majority of these changes copy files from QemuQ35Pkg to QemuSbsaPkg to start to eliminate the dependency QemuSbsaPkg has on QemuQ35Pkg; it should not have any dependency, but as a bringup vehicle it has significant dependency. In the future, some of these components could be moved to a common layer if they stay common between each platform in this repo.

    Furthermore, functionality was removed from QemuQ35Pkg that had been added to support QemuSbsaPkg and vice versa.

    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 manually by changing the config to enable/disable gfx.

    Integration Instructions

    N/A. Note that on GCC builds, a clean build is required after changing the XML to see config changes.




🛠️ Submodule Updates

  • Bump Silicon/Arm/MU\_TIANO from `c33d078` to `54bd48c` @dependabot (#424)
    Change Details
      Bumps [Silicon/Arm/MU_TIANO](https://github.com/microsoft/mu_silicon_arm_tiano) from `c33d078` to `54bd48c`.
    Commits
    • 54bd48c Remove the CodeQL workflow (#75)
    • 5b018fe Repo File Sync: Sync CodeQL workflow to additional repos (#74)
    • a8881f0 .pytool/CISettings.py: Use all CodeQL filter files (#73)
    • 7ee8a6f Repo File Sync: synced file(s) with microsoft/mu_devops (#64)
    • cebc981 pip: update edk2-pytool-extensions requirement from ~=0.21.8 to ~=0.22.2 (#71)
    • 44fd1ee pip: bump antlr4-python3-runtime from 4.11.1 to 4.12.0 (#65)
    • See full diff in compare view

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

  • Bump Common/MU from `a8192ed` to `97fbad8` @dependabot (#427)
    Change Details
      Bumps [Common/MU](https://github.com/microsoft/mu_plus) from `a8192ed` to `97fbad8`.
    Commits
    • 97fbad8 Add MemoryAttributeProtocolFuncTestApp (#192)
    • 09baaa8 Update DecodeUefiLog ReadMe.md - Simple Typo Fixes (
Read more

v1.1.2

09 Mar 19:20
2078183
Compare
Choose a tag to compare

What's Changed

  • QemuQ35Pkg.dsc: Remove Redundant Library Class @os-d (#389)
    Change Details
      # Preface

    Please ensure you have read the contribution docs prior
    to submitting the pull request. In particular,
    pull request guidelines.

    Description

    With PR #355, a duplicate library class was added to QemuQ35Pkg.dsc. This removes it. No functional change.

    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

    Built the platform.

    Integration Instructions

    N/A.

      </blockquote>
      <hr>
    </details>
    
  • Update feature repos to be submodules @Javagedes (#385)
    Change Details
      ## Description

    Updates MU_FEATURE_CONFIG and MU_FEATURE_MM_SUPV to be submodules rather then git dependencies. Additionally moves MU_FEATURE_DFCI into the features subfolder. Updates necessary information in the PlatformBuild files of QemuQ35Pkg and QemuSbsaPkg.

    Additionally, since QemuSbsaPkg and QemuQ35 are begging to diverge in necessary submodules, I've changed the functions that specify to stuart what submodules to download. Instead of downloading all submodules available, only the submodules necessary to the individual platform is downloaded.

    • 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

    Passing QemuQ35 and QemuSbsa CI

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    

📖 Documentation Updates

  • QemuQ35Pkg: Fix broken link in building.md @yangrongwei (#401)
    Change Details
      ## Description

    fix broken link.

    • 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

    Check doc link by hand.

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    

Full Changelog: v1.1.1...v1.1.2

v1.1.1

25 Feb 00:35
5a71cae
Compare
Choose a tag to compare

What's Changed

  • pip: bump edk2-pytool-extensions from 0.21.8 to 0.22.0 @dependabot (#373)
    Change Details
      Bumps [edk2-pytool-extensions](https://github.com/tianocore/edk2-pytool-extensions) from 0.21.8 to 0.22.0.
    Release notes

    Sourced from edk2-pytool-extensions's releases.

    Version 0.22.0

    What's Changed

    Integration Instructions

    This release has no integration instructions, however git management for edk2_setup, edk2_ci_setup, and git_depenencies has been completely rewritten. While this change has passed all unit and integration tests, it is expected that there will be some growing pains. Please raise an issue for anything that comes up here.

    Full Changelog: tianocore/edk2-pytool-extensions@v0.21.9...v0.22.0

    Version 0.21.9

    What's Changed

    Other Changes

    Full Changelog: tianocore/edk2-pytool-extensions@v0.21.8...v0.21.9

    Commits
    • f03cc88 Remove edk2_git.py (#407)
    • b202e95 Update vscode settings
    • 12acb07 edk2_logging: filter secrets from logs
    • 0ee5614 Add CLI env information to the argument parser --help (#417)
    • 439b70a Bump mkdocs-material from 9.0.12 to 9.0.13 in /docs/user (#448)
    • 88043ec Bump setuptools from 67.3.1 to 67.3.2 (#447)
    • f0aab31 Bump setuptools from 67.2.0 to 67.3.1 (#444)
    • 921b8ab edk2_logging: Add GCC compilation error info to log
    • c09a684 edk2_logging: Strip whitespace from errors
    • f7d91d4 test_edk2_logging: Add initial set of logging unit tests
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

  • Migrate to XML Based Configuration @os-d (#355)
    Change Details
      # Preface

    Please ensure you have read the contribution docs prior
    to submitting the pull request. In particular,
    pull request guidelines.

    Description

    mu_feature_config has moved to an XML based configuration system. This PR integrates changes from that repo and mu_oem_sample to demonstrate and run tests on an end to end XML based configuration system.

    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 manually by changing config knobs in XML and seeing different behavior, dumping config, applying config via SVD in ConfApp.

    Integration Instructions

    N/A, this is the example integration f...

Read more

v1.1.0

10 Feb 16:23
d2a6576
Compare
Choose a tag to compare

What's Changed

  • Job-Publish.yml: Remove temp NuGet publish workaround @makubacki (#325)
    Change Details
      Closes #324

    Description

    edk2-pytool-extensions 0.21.5 was recently published. As planned,
    this reverts 82a2ab7 which contained a temporary change until a
    new edk2-pytool-extensions release is available.

    Also updates pip-requirements.txt to 0.21.5.

    • 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 a separate Web page, ...

    How This Was Tested

    Test pipeline and PR gates.

    Integration Instructions

    N/A - pip module update and pipeline only change

    Signed-off-by: Michael Kubacki [email protected]




🚀 Features & ✨ Enhancements

  • QemuQ35Pkg and QemuSbsaPkg: Add varpolicy shell command @makubacki (#336)
    Change Details
      ## Description

    Adds the varpolicy EFI shell command to both packages.

    For more information about the command itself, please review
    the mu_ba...

Read more

v1.0.0

07 Feb 18:35
Compare
Choose a tag to compare

About This Release

This is the first Mu Tiano Platforms release 🎉

Moving forward this repository will be following semantic versioning and regularly making
releases. You will always be able to find the latest release on the repo landing page under
the "Releases" section on the right side.

The release notes will categorize changes to make it easy to see what's changed since the
last release and the source code will be tagged with the release version to reproduce the
release build.

Release binaries are published in two formats, both contain the same contents.

  • A NuGet feed in the mu_tiano_platforms repo
    • You will find a "Packages" section on the right side of the repo page with all of the
      NuGet packages published, just match the version to the release you're looking for
  • A zip file attached to the release
    • Look in the "Assets" section under the release to find the zip file

What's Changed

Read more