Tags: microsoft/mu_tiano_platforms
Tags
Rust Dependency: Bump hidparser from `2ecca0c` to `522f2ff` (#1043) Bumps [hidparser](https://github.com/microsoft/mu_rust_hid) from `2ecca0c` to `522f2ff`. Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
pip: bump edk2-pytool-extensions and edk2-pytool-library (#1021) ## Description edk2-pytool-extensions from 0.27.10 to 0.27.11 edk2-pytool-library from 0.21.9 to 0.21.10 - [ ] Impacts functionality? - [ ] Impacts security? - [ ] Breaking change? - [ ] Includes tests? - [ ] Includes documentation? ## How This Was Tested N/A ## Integration Instructions N/A
Add `bochs` VGA binary to QEMU release (#950) # Preface Please ensure you have read the [contribution docs](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md) prior to submitting the pull request. In particular, [pull request guidelines](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md#pull-request-best-practices). ## Description This change added an extra binary from QEMU builds to support QEMU-SBSA platform graphic operations. For each item, place an "x" in between `[` and `]` if true. Example: `[x]`. _(you can also check items in the GitHub UI)_ - [x] 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 locally by running QEMU-SBSA with the platform release UEFI binaries and booted to UEFI shell properly. ## Integration Instructions N/A
Upgrade default QEMU to v9.0.0 (#901) ## Description v9.0.0 fixed a few known issues blocking us from upgrading to QEMU of later than v7.2.0. This change is made to upgrade the default QEMU to v9.0.0 to intake the latest release. - [x] 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 change is tested locally on Windows and WSL environment. ## Integration Instructions Existing clones will need to perform `PlatformBuild.py --update` to download the latest version of QEMU. --------- Signed-off-by: kuqin12 <[email protected]>
Bump MU_BASECORE from 2023110003.1.2 to 2023110003.1.3 (#906) Bumps MU_BASECORE from `2023110003.1.2` to `2023110003.1.3` Introduces 1 new commits in [MU_BASECORE](https://github.com/microsoft/mu_basecore.git). <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/mu_basecore/commit/e8a14cbee1974c18092dcc2fbaf8f1fe05ae9812">e8a14c</a> Add NO_STACK_COOKIE to Module Entry Points (<a href="https://github.com/microsoft/mu_basecore/pull/793">#793</a>)</li> </ul> </details> Signed-off-by: Project Mu Bot <[email protected]> Signed-off-by: Project Mu Bot <[email protected]> Co-authored-by: Aaron <[email protected]>
.github/workflows/publish-qemu-bin.yml: reliability updates (#880) ## Description Updates release pipeline for the qemu binary to release qemu v7.2.0 as a external dependency and to also provide the following roms: - efi-e1000e.rom - efi-virtio.rom - [ ] 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 Terminal was not in an invalid state after exiting qemu, and that the above roms were successfully found at runtime. ## Integration Instructions Perform a release and update the qemu external dependency inside mu_tiano_platforms
Add E1000 rom to QEMU ext dep (#874) ## Description The e1000 NIC is useful for OS debugging and general "real hardware"-like network access. - [x] Impacts functionality? - [ ] Impacts security? - [ ] Breaking change? - [ ] Includes tests? - [ ] Includes documentation? ## How This Was Tested N/A ## Integration Instructions N/A
Add qemu binary release workflow: (#852) ## Description Add a new workflow that will build and prepare qemu binaries for both Windows and Linux. This workflow has three triggers: 1. A pull request to the main branch, which will only trigger when either the workflow itself, or the qemu version file is updated. This workflow will upload the binaries as an artifact to the workflow. 2. A release, which will upload the binaries as an artifact to the associated release 3. A manual trigger, which allows for testing the workflow on a custom branch. This will upload the binaries as an artifact to the workflow. - [ ] 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 A release was performed using this github action on a personal branch ([v0.1.9](https://github.com/Javagedes/mu_tiano_platforms/releases/tag/v0.1.9)), and was used as an external dependency on a mu_tiano_platforms [Draft PR](#851), which is passing, and will be merged once this PR has been merged and a release has been executed. ## Integration Instructions N/A
pip: bump edk2-pytool-library from 0.21.2 to 0.21.3 (#854) Bumps [edk2-pytool-library](https://github.com/tianocore/edk2-pytool-library) from 0.21.2 to 0.21.3. Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
PreviousNext