Synaptics targets Vino in dispute over open-source DisplayLink driver

Synaptics has cited two patents, GB2484736 and GB2485613, in a cease-and-desist against Mike Lothian’s open-source Vino DisplayLink driver, and the developer has taken the project offline.

Phoronix described the Rust project as clean-room reverse-engineered and partly developed with AI assistance. That leaves the published dispute centered on patent scope and disclosure of implementation details, rather than an allegation that Lothian copied Synaptics code.

How did a bug request become a patent dispute?

In July 2026, Lothian contacted Łukasz Spintzyk, a software engineer at Synaptics, while trying to fix bugs in his driver. About two weeks later, Michal Lukaszek, the company’s Strategic Engineering Partnerships Lead, replied that Synaptics believed Lothian was implementing the DisplayLink protocol itself in violation of its patents.

Synaptics’ legal department then sent a cease-and-desist letter demanding that he remove the Vino GitHub repository and made other requests the published exchange does not spell out. The exchange grew into a written argument over whether the project falls within the company’s patent claims.

Takeaway: A request for debugging help became a formal allegation of patent infringement.

How did Synaptics respond to the project?

After Lothian asked for a complete explanation of the alleged infringement, Synaptics did not answer. Three weeks later, the company escalated by saying it would bill him to recoup the cost and effort of creating documentation of his infringing acts.

Assistant General Counsel Andrew Bateman said: “By open sourcing our DisplayLink technology for whatever personal reasons you may have as a ‘hobbyist,’ you will be single-handedly eviscerating DisplayLink's competitive advantage in this crowded market.” He argued that the project would educate competitors and third parties about implementation details Synaptics has gone to great lengths and expense to protect.

Synaptics also gave Lothian permission to publicize its response, saying it welcomed free publicity to show shareholders and competitors that it aggressively defends its DisplayLink intellectual property. The company threatened to sue, linking the dispute to competitive harm rather than copied source code.

Takeaway: Synaptics combined a cost-recovery threat with a competitive-harm argument, but the correspondence never explained the claim in technical detail.

What do the two patents cover?

GB2484736, titled “Image generation,” covers sending screen updates through a general-purpose data network such as USB or Ethernet using a specific architecture and compression method. GB2485613, titled “Display control device,” describes hardware that works with compressed data and decompresses it only as needed.

Synaptics says both claims cover Lothian’s work. The published exchange contains no response to his request for a complete explanation of how his implementation infringes.

Takeaway: The dispute centers on two defined claims, not on whether Lothian copied Synaptics’ driver code.

How does Lothian challenge the patents?

Lothian maintains that he did not copy the code behind the driver and that both patents are invalid. His argument focuses on how the patent claims changed during prosecution.

He said: “In both cases the independent claims as filed contained no network or transport limitation. The claims were granted only after being amended to add delivery of the display data over a ‘general-purpose data network’ (and, for GB2485613, a ‘transport protocol’ with an ‘unpackaging’ step). That added feature was not new.”

His defense also touches the Open Invention Network. Synaptics is an OIN licensee, while Lothian says the company disputes whether patents from acquired subsidiaries fall under that license.

Some observers argue that an OIN license should cover patents transferred with an acquired subsidiary. The exchange shows that the parties do not agree on that interpretation.

Takeaway: Lothian challenges both the patent claims and the licensing assumption that Synaptics appears to rely on.

Where does the dispute stand?

Lothian eventually took the Vino GitHub repository offline, although he remains open to discussing a sensible resolution. The source describes a threat of litigation, not a filed lawsuit, damages award or settlement.

The complete email thread, with an attached PDF, is available through a Linux Kernel Mailing List page. The exchange discloses no licensing fee, damages figure or revenue effect.

Takeaway: The repository is offline, but the technical and licensing questions remain open.

What does the AI-assisted development change?

Lothian said he used a Claude subscription to assist with the clean-room reverse-engineering effort, and he wrote Vino in Rust. The account treats the episode as a warning about how advanced tools can shorten the work required to reproduce proprietary interfaces.

The report also cites a user who built a free Adobe Creative Suite clone in Rust with Claude and was reportedly working on an open-source office suite and Autodesk tools. Reverse-engineered games running on unintended platforms have also forced Anthropic to enforce some limitations on Opus 5.5.

The report further notes concern that widespread AI use in chipmaking could propagate a copied design or an infringed patent across thousands of chips before anyone detects it. No measured effect on chip shipments, licensing revenue or pricing accompanies that concern.

For Synaptics, the immediate commercial issue is narrower: whether an open implementation can weaken DisplayLink’s competitive position and force higher spending on protection. The correspondence frames that risk, but it provides no evidence of a change in sales, pricing or production.

Takeaway: A settlement that allows further public disclosure would preserve the competitive exposure Synaptics described, although the source offers no forecast for pricing, revenue or shipment volumes.