Synaptics Targets AI-Assisted Linux DisplayLink Driver With Patent Claims

DisplayLink is a proprietary graphics transport technology enabling computers to connect external displays via USB through docks or adapters containing DisplayLink chips. The system operates by compressing video data on the host machine and transmitting it to a chip in the connected device, which then decodes the signal for output to monitors through HDMI or DisplayPort interfaces.

On Linux systems, the closed-source nature of DisplayLink support has prompted some developers to seek alternatives. Mike Lothian, known online as FireBurn, created Vino as an open-source replacement, designed to let the Linux kernel communicate directly with DisplayLink docks without relying on proprietary software or the open-source EVDI kernel module.

Synaptics, which owns DisplayLink, has responded with legal action. The company sent Lothian cease-and-desist letters asserting that his project violates DisplayLink patents covering the protocol and codec technology.

Development and Initial Contact

Lothian developed Vino with assistance from Claude Code, submitting an incomplete first version to the kernel mailing list in June. He encountered technical difficulties coordinating between the dock and driver and sought input from other developers.

In early July, Lothian emailed a Synaptics employee requesting technical guidance and mentioned his Rust rewrite of EVDI. Two weeks later, a different Synaptics employee responded, stating that the Rust rewrite itself was not problematic. Instead, Synaptics expressed concern about the DisplayLink protocol and codec, which the company maintains are protected by its patent portfolio.

Legal Escalation

On August 17, Synaptics delivered a cease-and-desist letter demanding that Lothian halt development and remove all submissions from maintainers and hosting platforms, with written confirmation required by August 28. The letter included an appendix listing more than 125 patents without specifying which ones applied to Vino.

Lothian published version 3 of Vino on August 26 and requested clarification from Synaptics the following day about which patent claims were at issue. Synaptics responded in October with claim charts mapping specific claims from two patents—GB2484736 and GB2485613—to sections of his source code.

The October 5 letter from Synaptics stated the company would demand $25,000 to cover the cost of preparing the claim charts if Lothian failed to meet an October 11 deadline, with the amount increasing by at least $25,000 each subsequent week.

Lothian replied on October 6, proposing to suspend public development of the encoding code identified in the charts if Synaptics would pause both the deadline and the weekly financial penalties. He also inquired about obtaining a non-commercial license for that code.

Synaptics rejected the proposal on October 7, declining to grant any patent license or non-assertion promise and establishing October 18 as a final deadline.

Clean-Room Design Strategy

Lothian characterizes Vino as a clean-room driver, stating he reverse-engineered it by analyzing captured USB traffic and vendor applications. In a clean-room approach, one party examines the original implementation and produces documentation, while a separate party writes new code based solely on that documentation, not the original source.

This methodology is intended to serve as a defense against copyright infringement claims by demonstrating that no code was directly copied. However, Synaptics' July response contended that clean-room or independently developed code can still violate patent rights.

Broader Context

Vino emerges during a period of increased activity in AI-assisted reverse engineering, spanning projects from smart television modifications to office productivity software clones. Legal challenges have also targeted other projects developed with AI assistance.

Lothian has removed the Vino repository in response to Synaptics' demands. Synaptics has not issued any public statement regarding the matter. The ultimate outcome of this dispute remains uncertain, though the removal of the repository may complicate efforts for other developers to build upon the work.