Repository navigation
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.
I added support for my Valkyrie V360 LCD, which shares the
345f:9132MS9132 bridge with VMAX and Jonsbo DS339 but needs its own initialization and frame header. Discovery uses EDID geometry to route it to the V360 model and pairs HID/video interfaces by serial. It uses the existing profile renderer and device supervisor, with raw UYVY frames, cached conversion invalidation and static-frame keepalive. Existing VMAX XML settings remain compatible.I also added an experimental MC360 transport, restricted to
374a:a021, product stringVk-Copl-08and a valid 640×480/614400-byte screen-info response. It uses BGR565 bulk transfers, acknowledged frame-size announcements, aligned-transfer ZLPs and idle keepalive. I do not have an MC360 to test on Linux, so the UI and documentation explicitly mark it experimental. Discovery does not change brightness or send images.The device list shows only the explicit V360 and MC360 model names. I left out ambiguous resolution/material-code groups and air-cooler aliases, and hid JPEG quality controls for these raw-frame devices.
I retained the full MIT notice for the V360 initialization adapted from LCD Fusion. I independently implemented the MC360 transport from published wire-format facts; references and limits are in
docs/VALKYRIE-MC360.md. No vendor binaries or private driver core are bundled.Validation:
I have not tested MC360 on physical Linux hardware, physical suspend/resume, or simultaneous operation with VMAX/DS339.