Skip to content

Add Valkyrie V360 LCD support and experimental MC360 support - #13

Merged
emaspa merged 3 commits into
emaspa:mainfrom
EsiksonX:feat/valkyrie-v360-lcd
Oct 18, 2026
Merged

emaspa merged 3 commits into
emaspa:mainfrom
EsiksonX:feat/valkyrie-v360-lcd

Conversation

@EsiksonX

Copy link
Copy Markdown
Contributor

I added Valkyrie V360 (320×240) and experimental MC360 (640×480) LCD support.

Changes:

  • Dedicated Valkyrie section, streaming switch and profile/hotkey support.
  • Model-specific USB transport, brightness and rotation controls.
  • EDID-based MS9132 identification and migration of misidentified DS339 entries.
  • RPM permissions applied to already-connected screens.

Status:

  • I verified V360 display, discovery, brightness, rotation and task restart on Linux.
  • MC360 remains experimental; I have not tested it on hardware.
  • 361 tests passed; Linux x64 publish and Fedora 44 RPM builds passed.

@emaspa
emaspa self-requested a review October 18, 2026 12:56
Follow-up to the Valkyrie V360/MC360 support from @EsiksonX.

- VMAX 4.6" scan no longer needs a USB serial: a lone MS9132 bridge pairs
  its HID and video interfaces without one. A readable EDID that is neither
  320x240 (V360) nor 376x960 (DS339) stays on the VMAX path, since no VMAX
  EDID has been captured yet.
- HID serial reads during the scan can no longer abort the MS9132 scan.
- The VMAX init skips HID interfaces whose EDID identifies a V360 or DS339,
  so a VMAX entry never programs another screen on the shared VID/PID.
- Earlier releases added a V360 as a VMAX 4.6" (path-based ID). A scan that
  confirms the V360 now replaces that entry, carrying over profile, enabled
  state, brightness, rotation and hotkeys.
- The deb postinst and AUR install hook re-trigger udev for connected
  V360/MC360 screens, matching the RPM spec.
- V360 frame layout uses its own prefix length for the pixel and suffix
  offsets.
- Docs: trimmed the Valkyrie pages, user guide mentions the family, README
  credits EsiksonX.
@emaspa
emaspa merged commit 701d06a into emaspa:main Oct 18, 2026
@emaspa

emaspa commented Oct 18, 2026

Copy link
Copy Markdown
Owner

Thanks a lot for this, @EsiksonX! The V360 support was well put together, and testing it on real hardware made it easy to merge. It shipped in 0.3.8, and you're in the README credits now.

Before merging I pushed one follow-up commit (701d06a):

  • A VMAX 4.6" without a USB serial is found again when it's the only MS9132 attached. Any readable EDID that isn't 320×240 or 376×960 still goes to the VMAX path, since nobody has captured a VMAX EDID yet.
  • The VMAX init skips HID interfaces whose EDID says V360 or DS339, so it can't program your screen by accident.
  • Older releases added a V360 as a "VMAX 4.6"" entry. Scan now moves that entry to the Valkyrie section with its profile, brightness, rotation and hotkeys.
  • The deb and AUR packages re-trigger udev like your RPM change does. lintian didn't accept read in maintainer scripts, so all three use cat now.
  • I trimmed the two Valkyrie docs a bit.

If you notice anything off on your V360 with 0.3.8, especially after suspend/resume, please open an issue. And if you ever get an MC360 tester, I'd like to hear how that driver does on a real panel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants