Synaptics Blocks DisplayLink Driver for Linux with Patent Claims

⚡ The gist in 5 seconds

• Lawyers for Synaptics (which has owned DisplayLink since 2022) sent the author of the open-source Vino driver claims of patent infringement and demanded he stop the "unauthorized implementation" of DisplayLink technology.
• The case involves a Dell USB 3 dock with a DisplayLink chip: the official DisplayLink Manager for Linux ships only as a binary, only for x86, via an APT repository for Ubuntu.
• The only open part is the EVDI module inside that package, but Linux users still don't have parity with Windows and macOS.

🔍 What happened

Mike Lotian bought a Dell dock with a DisplayLink chip and was unhappy with how it worked under Linux: the official driver kept crashing. He decided to write his own — in Rust, with the help of a Claude subscription — and on June 17 sent the first RFC patch set for the Vino driver (DRM/KMS) to the dri-devel mailing list. The reply came not from engineers but from Synaptics' lawyers: patent infringement claims, a demand to stop the unauthorized implementation of DisplayLink technology, and threats of costly litigation.

Here's how the mechanics work. DisplayLink Manager (DLM) for Linux is a proprietary x86 binary that the company distributes via an APT repository for Ubuntu. Inside it sits the open out-of-tree kernel module EVDI (Extensible Virtual Display Interface): it's compatible with Linux DRM, and screens can be configured with ordinary xrandr or the GNOME and KDE Plasma panels. The video and audio are handled by the closed DL3 technology — it compresses multiple channels (USB, DisplayLink video, audio) into a single stream over USB 3 and decompresses it at the output. It was DL3's control plane where Lotian hit a wall: on June 17 he opened an issue in the EVDI repository on GitHub describing his reverse engineering — there was no response. On dri-devel, he was only advised to rewrite the driver using Rust KMS bindings (advice from Danilo Krummrich), but no one helped with the specific problem. On July 20, after Lotian wrote to Lukasz Spintyk of Synaptics, Michal Lukaszek replied: DisplayLink is not an open standard, and the protocol, codec, and other technologies are proprietary property of Synaptics. The entire correspondence from July 5 to October 7 has been compiled into a PDF that Lotian published himself. It also includes the story of bugs he found in EVDI and a pull request that sat unreviewed for months.

🧠 Our take

Our assessment: this story isn't about a single patent — it's about reverse engineering getting cheaper. A person with an LLM subscription and persistence took a couple of weeks to get a working prototype of something that used to require a whole team. For a vendor, that's an uncomfortable shift: closed protocols used to be protected by their complexity, and now only by lawyers. Hence the speed of the reaction: no engineering response was written, but a letter from the legal department arrived promptly.

What this changes for people. Owners of DisplayLink docks on Linux are stuck with an x86 binary and no proper support. On ARM machines there is no official DLM at all — that follows directly from the x86-only build. The parity with Windows and macOS that LWN writes about remains out of reach, and it's now unclear who would want to repeat Lotian's path knowing how it ended.

Who wins and who loses. Synaptics is defending a licensing business — legally, most likely, from a strong position: the protocol is closed, and the patent claims come from the rights holder. But tactically it looks weak. In our experience, hardware vendors who respond to an engineer with a lawyer lose exactly the users who were willing to fix their product for free. Buyers lose too: the dock works worse than it could, and there's no one officially able to fix it.

⚠️ What we don't know

The article contains no patent numbers, no full quotes from Synaptics' lawyers, and no data on how many letters were sent or what exactly was threatened. The entire correspondence was compiled by one side — Lotian — and published by him. We know the company's position only from a single reply dated July 20 plus LWN's retelling. Readers can check for themselves whether the patents are registered in the author's jurisdiction — the article doesn't cover this. Also, the LWN piece itself is distributed via a subscriber link, so the primary source isn't available to everyone.

Prediction: Vino won't land in mainline within the quarter: either Lotian will shelve the work, or we'll see a targeted permission from Synaptics for EVDI changes — but not for DL3.

Disclaimer: not officially confirmed, single source, correspondence published by only one side.

Source: LWN.net