fix(devices): mark Pulsar X3 Medium test-needed until XS-1 driver lands - #103
Merged
Merged
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
2 participants
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.
Pulsar X3 Medium currently claims
supported, but no @openmouse/protocol driver can drive the X3 yet (the Sonix XS-1 feature-report driver is pending in OpenMouse-Project/mouse-protocol#21).likely(shows "Test Needed") and pins its aspirational PIDs (0x3409/0x3410/0x5402/0x5403) with a note pointing at the pending driver.supported/quickwin) are validated against the protocol registry, so aspirational PIDs on test-needed rows don't break the build. Once the XS-1 driver lands, flipping the row tosupportedis validated automatically.No other devices are affected.