Synaptics threatens open-source DisplayLink driver Vino with patent litigation

Mike Lothian, a hobbyist developer, received a cease-and-desist letter from Synaptics demanding he take down Vino, his open-source DisplayLink driver written in Rust and developed with assistance from Claude AI. The dispute began in July 2026 when Lothian contacted a Synaptics engineer about bugs, but the company soon accused him of patent infringement rather than copyright violation. Synaptics claims Vino infringes two UK patents, GB2484736 and GB2485613, covering image compression and transmission over general-purpose data networks and hardware-based selective decompression.

Lothian requested detailed infringement analysis but was met with escalation: Synaptics' Assistant General Counsel Andrew Bateman threatened to bill him for the cost of preparing legal documentation and dared him to publicize the correspondence. Lothian has since taken the GitHub repository offline but disputes patent validity, arguing the claims were amended post-filing to add network transport limitations that were not novel. He also notes Synaptics is an Open Invention Network licensee and suggests acquired subsidiaries' patents may fall under that commitment, a position Synaptics disputes.

Patent claims and reverse-engineering methodology

• Clean-room reverse-engineering: The Vino driver was developed through clean-room reverse-engineering of the DisplayLink protocol, with development assisted by a Claude AI subscription, using Rust as the implementation language.
• Patent GB2484736 (Image generation): Covers transmitting screen updates over general-purpose data networks such as USB or Ethernet using a specific architecture and compression method.
• Patent GB2485613 (Display control device): Describes hardware that operates on compressed data and performs decompression only as needed.
• OIN license dispute: Lothian argues Synaptics' status as an Open Invention Network licensee may extend to patents from acquired subsidiaries, though Synaptics contests this interpretation.
• Prior art challenge: Lothian contends both patents were amended after initial filing to add network and transport protocol limitations, and that these added features were not novel at the time of amendment.

Why it matters

This case highlights growing legal risks for independent open-source hardware driver developers, particularly those using AI-assisted reverse-engineering tools that may accelerate protocol analysis but create new evidentiary questions in patent disputes. The outcome could influence whether other developers attempt clean-room implementations of proprietary display protocols, and whether corporate OIN membership provides meaningful protection for downstream open-source projects.