Expand AMD xHCI IMOD allowlist to five devices - #1
Open
Softhe wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Expands the AMD xHCI IMOD allowlist from
15B7and43FDto the five-device union15B6,15B7,15B8,43F7, and43FD.This changes only the allowlist. The existing xHCI class, BDF, BAR, mapping, bounds, active-interrupter, 32-bit RMW, readback, rollback, and unmap protections are unchanged.
Evidence boundaries
15B6,15B8,43F7: locally exercised through discovery, read-only enumeration, bounded write/readback/restore, reboot, cold boot, and resume testing.15B7,43FD: retain PR Add restricted AMD xHCI IMOD module namazso/PawnIO.Modules#111's discovery/BDF evidence; live register execution is still pending on that hardware.Reproducible build
Pawn 4.1.7152 with the repository CI flags produced byte-identical 21,808-byte AMX files across two builds.
SHA-256:
cc91910714a6e1a7fba075684a9836728ea7c5439518ab5a0a0019866544a16aThe AMX is development evidence only. It is not proposed as a production release artifact and does not replace maintainer signing.