v2023110001.0.2
·
1 commit
to refs/heads/release/202311
since this release
What's Changed
-
Set PciFunction to 0xFFFF for \_PRT per specification @Javagedes (#258)
Change Details
## Description
partially reverts #37 which updated the PciFunction to no longer be 0xFFFF for _PRT which goes against the ACPI specification that states that the PciFunction should be 0xFFFF for _PRT.
This is per ACPI specification 6.4 section 6.2.13
- 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, ...
- Security - Does the change have a direct security impact on an application,
- 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, ...
- Breaking change - Will anyone consuming this change experience a break
- 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, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
N/A - Spec compliance
Integration Instructions
Platforms should verify PciFunction for _PRT is 0xFFFF
- Impacts functionality?
Full Changelog: v2023110001.0.1...v2023110001.0.2