mu_tiano_platforms/.gitignore

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

19 строки
222 B
Plaintext
Исходник Обычный вид История

2020-10-21 21:44:48 +03:00
/Build/
.DS_Store
*_extdep/
*.pyc
2020-10-21 21:44:48 +03:00
__pycache__/
tags/
.vscode/
.vs/
*.bak
2020-10-21 21:44:48 +03:00
BuildConfig.conf
UefiDbgExt/x64/
*.vcxproj.user
2020-10-21 21:44:48 +03:00
/Conf/
Migrate to XML Based Configuration (#355) # 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 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)_ - [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, ... - [x] 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 for a platform. --------- Co-authored-by: Kun Qin <kuqin@microsoft.com>
2023-02-23 00:47:17 +03:00
/**/Include/Generated/**
Use secureboot binary blob external dependency (#790) ## Description Use secureboot binary blobs generated from https://github.com/microsoft/secureboot_objects for the PK, KeK, Db, Dbx, and 3PDb. The secureboot binary blobs are downloaded as an external dependency, which enables the contents of the secureboot variables to be strongly versioned and easily tracked. This change uses a new version of SecureBootKeyStoreLib (from MsCorePkg), which consumes the secureboob binary values from PCDs and a new helper plugin (BuildSecurebootPcds) generates these PCDs on each build. - [ ] Impacts functionality? - **Functionality** - Does the change ultimately impact how firmware functions? - Examples: Add a new library, publish a new PPI, update an algorithm, ... - [x] 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 QemuPkg and QemuSbsaPkg continue to boot and can have secureboot enabled. ## Integration Instructions N/A
2023-12-06 02:00:57 +03:00
/**/AutoGen/**
# Ignore Rust build output
/target