This repository was archived by the owner on Oct 30, 2026. It is now read-only.
Repository navigation
Recognize RAM payload USB devices on Linux - #13
Merged
henrikklee merged 1 commit intoOct 30, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
On Linux, a RAM payload using the USB helper's
05ac:4144endpoint is discovered asother, soorchard exec,pushandpullrefuse to connect. Add the missingramPID mapping, matching the existing Darwin discovery behavior.The regression fixture checks the mode, boot identity, serial endpoint and absence of an ECID for this RAM gadget.
Validation:
orchard exec,pushandpullworked, including reconnecting after physical Lightning unplug/replug and live driver replacement.resolvetest invocations omit the now-required--profile, and one local-receipt fixture rejects the virtualenv'slib64symlink. The editable-environment run also exposed the olderresolvetest and installed-wheel isolation assumptions. No unrelated tests or command behavior were changed.