Legal notice sent over AI-assisted DisplayLink Linux driver
Archived — this story has rotated out of today’s deck. It is kept here in full.
The gist
Synaptics told hobbyist developer Mike Lothian to halt his Vino DisplayLink driver and withdraw it from repositories.
The dispute tests how patent claims apply to AI-assisted, clean-room open-source work.
Background
Mike Lothian (FireBurn) is a hobbyist developer who built Vino, an open-source Rust driver for DisplayLink docks, using clean-room reverse engineering with help from Claude Code. DisplayLink is a proprietary graphics transport technology for connecting computers to external displays over USB; Synaptics, which acquired DisplayLink in 2020, owns it and provides its closed-source software. Vino was meant to replace that closed-source software and the open-source EVDI kernel module beside it, and supported three generations of DisplayLink hardware including the Dell Universal Dock D6000. The dispute is trending because it pits patent enforcement against an AI-assisted, independently written open-source project.
How it unfolded
- Jun 17, 2026Mike Lothian's first version of Vino, an unfinished Rust driver written with help from Claude Code, reached the kernel mailing list.
- early Jul 2026Lothian emailed a Synaptics employee for guidance and mentioned his Rust rewrite of EVDI.
- about two weeks laterA different Synaptics employee replied that the Rust rewrite of EVDI was not a concern; the concern was the DisplayLink protocol and codec, which Synaptics believes its patents cover.
- Aug 17, 2026A cease-and-desist letter told Lothian to stop development and withdraw submissions to maintainers and hosting sites, with signed confirmation due by August 28; an appendix listed over 125 patents without saying which applied.
- Aug 26, 2026Lothian posted a working version 3 of Vino.
- Aug 27, 2026Lothian asked Synaptics which patent claims they had in mind.
- Oct 2026Synaptics sent claim charts mapping one claim from each of two patents, GB2484736 and GB2485613, to his source code.
- Oct 5, 2026A letter said Synaptics would seek $25,000 for the cost of preparing the charts if Lothian missed an October 11 deadline, rising by at least $25,000 each week.
- Oct 6, 2026Lothian offered to pause public work on the encoding code the charts point to if Synaptics paused the deadline and weekly charge, and asked about licensing that code for non-commercial use.
- Oct 11, 2026Vino was removed from public repositories after Synaptics' final deadline; all kernel mailing list submissions were withdrawn and Lothian provided written confirmation of compliance.
- Oct 18, 2026Synaptics set this as a final deadline and refused to grant a patent license or promise not to sue.
- Nov 2026The Vino GitHub repository has been taken offline and the dispute remains unresolved.
Key terms
- cease-and-desist
- A letter warning a party to stop an allegedly unlawful activity or face legal action.
- clean-room
- A method of copying a design by reverse engineering and recreating it independently, without infringing the original's copyright.
- Open Invention Network
- A patent-licensing company that grants royalty-free licenses to members who agree not to assert patents against Linux.
Source: Wikipedia
Who’s saying what
- Synaptics
- Synaptics says its concern is the DisplayLink protocol and codec, which it believes its patents cover, and that clean-room or independently written code can still infringe a patent.
- Developer
- Lothian disputes the infringement allegations, questions the validity of the patents, and says he remains open to discussing a resolution.
- Synaptics
- Synaptics' legal counsel encouraged Lothian to publicize the dispute, saying the company welcomed publicity about protecting its intellectual property, and said its DisplayLink patents are not covered by the Open Invention Network agreement.
Still unverified
No court ruling has established that Lothian's driver infringes Synaptics' patents, and the dispute remains unresolved; Synaptics has not made a public statement so far.