Vino, the Rust DisplayLink Driver, Went Dark After Synaptics Cited Two UK Patents

The open-source Vino driver for DisplayLink DL3 docks is no longer publicly available after Synaptics sent its developer a cease-and-desist notice citing two UK patents, according to a summary of the correspondence published by braindetox.kr. That summary says Phoronix reported the repository's disappearance on Nov. 4. The Phoronix page returned an access error when fetched, so the repository status rests on that secondhand account.

Synaptics, which owns DisplayLink, has not published a statement in any source reviewed here.

What the Vino patch series was

The second revision of the series was posted to the Linux kernel mailing list by Mike Lothian on July 2. It adds an in-kernel Rust DRM driver called drm/vino for DisplayLink DL3 docks, meant to replace the out-of-tree EVDI module and the DisplayLinkManager userspace daemon. The cover letter gives the Dell D6000 (USB ID 17e9:6006) as its example and counts 14 files and 6,341 lines.

It was a request for comment, not a merge candidate. In the cover letter's own words, "the dock never engages its content-protection channel for vino, so no pixels flow yet."

Open item in the v2 cover letter	State
Display output	None; content protection never engages
Colour codec	Covers only 64x16-aligned geometry; other modes fall back to run-length encoding
Second monitor	Only head 0's EDID is read
Build	Needs a separate KMS mode-object layer that is not merged

The author's read is that the dock's firmware blocks the host from reaching the gate, and a hardware USB analyser is the next step. The cover letter also says the codec's entropy grammar was reverse-engineered and describes a "clean-room HDCP 2.2 AKE/LC/SKE handshake." It does not state a licence.

What the letters and the reply say

According to braindetox.kr, the mailing-list attachments include a cease-and-desist notice and a follow-up notice, and name two patents: GB2484736 and GB2485613. The summary says the letter's PDF was not opened, so neither patent's claims were read. This article did not read them either.

The same summary describes a reply dated Oct. 14. In it, the developer says they are an individual hobbyist without a lawyer, do not accept that they infringe either patent, and reserve all rights. They cite UK IPO search reports dated Feb. 22, 2011 and March 22, 2011, and the RFB/VNC specification from January 1998, as prior art.

The developer also says both sides are licensees of the Open Invention Network and asks which provision Synaptics relies on to exclude DisplayLink's patents. The reply closes by saying the developer remains open to a resolution if given a specific proposal.

What Hacker News argued about

The Phoronix story reached 232 points and 105 comments on Hacker News. A commenter, LoganDark, quoted the letter as saying "We demand your immediate cessation of your infringing activities." The quotation comes from the commenter and was not checked against the PDF.

Several commenters said clean-room work is a copyright defence and does not answer a patent claim. Another, kmeisthax, argued that using an LLM weakens a clean-room claim because models are trained on so much code. The mailing-list cover letter does not say whether AI tools were used, so that argument is aimed at a fact nobody in these sources has confirmed.

Another commenter, jeremyjh, said that even a dismissed claim can cost "thousands, if not tens of thousands" in legal fees.

What Linux users have today

Synaptics still ships its proprietary DisplayLink driver, which is the supported route for current docks. The Vino work was an attempt to replace it with something that could go upstream, and the mailing-list record shows it had not reached that point technically even before the letters.

Vino is written in Rust, a language whose pointer rules matter to anyone writing kernel drivers. The Git project is separately drafting a vote on its policy toward AI-looking patches, so the AI question raised on Hacker News is one maintainers are already debating.

No court filing has been reported. The next visible event would be a reply from Synaptics on the mailing list or a restored repository, and neither has a date.