Skip to content

Releases: microsoft/mu_plus

v2023020000.1.0

22 Jun 15:22
@github-actions github-actions
v2023020000.1.0
092c55e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v2023020000.1.0

What's Changed

  • [REBASE \&\& FF] Cherry-Pick BootAuditTestApp Update and DxePagingAuditTestApp Update from 202208 @TaylorBeebe (#258)
    Change Details
     
  • Onboarding ARM64 builds on selfhosted Azure pipeline agents @kuqin12 (#240)
    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 added a few new matrix entries to support building mu_tiano_platforms on native ARM64 systems. The PR will cover both microsoft/mu_basecore#369 and microsoft/mu_basecore#305.

    The PR should also be incorporated with mu_devops 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

    This was tested on selfhost-agents and existing agents.

    Integration Instructions

    Pipeline changes, N/A for integration.

      </blockquote>
  <hr>
</details>

🚀 Features & ✨ Enhancements

  • [CHERRY-PICK] Remove bootmode from con var update 202302 [Rebase \& FF] @makubacki (#260)
    Change Details
      ## Description

    Cherry picks commits from PR #259 into release/202208 into release/202302.

    Some platforms may not reach BDS on a boot mode expected by the
    current implementation to update the ConIn variable with a new
    console input device.

    For example, support for a new device might be added in a firmware
    update, the update is performed, and the system is reset one or
    more times before reaching PlatformBootManagerBeforeConsole().

    This change always evaluates a potential update to ConIn regardless
    of boot mode to reduce ConIn update complexity.

    • 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 and boot with the change. Since only the boot mode check
    is removed, the underlying behavior within the boot mode condition remains
    the same

    Integration Instructions

    Review the change to when console may be updated relative to boot mode in
    change and the implementation of EfiBootManagerUpdateConsoleVariable()
    being used by the platform to determine if you would like to make any
    changes to that function. No required changes are expected.



Full Changelog: v2023020000.0.0...v2023020000.1.0

Contributors

makubacki, TaylorBeebe, and kuqin12
Loading

v2023020000.0.0

26 May 18:18
@cfernald cfernald
v2023020000.0.0
4f2a915
Compare
Choose a tag to compare
v2023020000.0.0

What's Changed

This is the first MU Plus 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.

Loading