TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Linux developer Mike Lothian says Synaptics sent him a cease-and-desist letter over Vino, his unfinished attempt to build a driver for DisplayLink docks. Synaptics cited 125 patents but, according to the report, did not identify which patents the project allegedly infringed. The dispute leaves the project’s future and the legal basis for the claims unresolved.
Synaptics has threatened legal action against Linux developer Mike Lothian over Vino, his unfinished independent driver project for DisplayLink hardware, prompting him to stop work for now. The company’s August 17 cease-and-desist letter cited a list of 125 patents, but the report does not say that Synaptics identified specific patents allegedly infringed by Vino.
Lothian began working on Vino after experiencing crashes with the vendor-provided DisplayLink Manager software for Linux on a Dell dock. The new project is a Rust-based driver intended to support the device through Linux’s graphics framework. Lothian posted an incomplete request-for-comments patch series to the kernel’s dri-devel mailing list on June 17, asking for help with communication between the driver and the dock.
He also opened an issue on the EVDI project’s GitHub repository and contacted Synaptics directly. EVDI is an open-source, out-of-tree kernel module distributed alongside DisplayLink Manager; the manager itself is proprietary and, according to the report, available for Linux only as a binary for x86 systems. Lothian said he had also reported bugs in EVDI and submitted a pull request that went unreviewed for several months.
In a July 20 email, Synaptics employee Michal Lukaszek told Lothian that DisplayLink’s protocol and technologies were proprietary and patent-protected. On August 17, Synaptics intellectual-property counsel Andrew Bateman sent a formal notice. It demanded that Lothian stop development of software the company considered infringing, withdraw material submitted or posted to various venues, and identify where it had been published or stored. The report says the letter’s appendix listed patents but did not connect particular claims to particular parts of Vino.
Linux Dock Support Faces a Legal Barrier
The dispute affects users who rely on DisplayLink docks with Linux, particularly when vendor software does not perform reliably or lacks features available on other platforms. An independent implementation could potentially give users another route to use their hardware, but Synaptics’ patent claims have interrupted this effort before the project reached a completed or broadly tested state.
The episode also highlights a distinction relevant to open-source development: writing new code rather than copying proprietary source does not, by itself, settle whether a patent is implicated. That is the position Synaptics communicated to Lothian; the report does not establish that a court or other authority has ruled that Vino infringes any patent. For now, the practical result is that Lothian has halted work, while Linux users remain dependent on the software and support the vendor provides.
Products Worth Considering
DJI Mini 4 Pro Fly More Combo Drone with DJI RC 2
Amazon Kindle Scribe (3rd Generation), 64GB, 11-inch Display, Graphite, with Premium Pen
Jackery Explorer 300 Portable Power Station with 40W Solar Panel
As an affiliate, we earn on qualifying purchases.
From Driver Bugs to Patent Letters
DisplayLink was acquired by Synaptics in 2022. Its DisplayLink Manager software uses the company’s proprietary DL3 technology to combine and compress streams, including video and audio, for transmission over a connection such as USB 3. The vendor distributes its Linux manager as a binary rather than publishing its source code, while EVDI supplies an open-source interface between Linux’s display system and the manager.
After finding the supplied software unreliable on his system, Lothian tried to develop Vino with help from an AI coding assistant. His June mailing-list post described the work as incomplete and asked for help with a technical obstacle involving the dock’s control plane. Developers offered some general guidance, including advice to use Rust KMS bindings, but the report says he did not receive an answer to that specific protocol question from the community or in the EVDI issue.
Synaptics’ initial July message framed its concern as a warning about patent exposure, saying the project appeared to be moving beyond interoperability work. The August letter escalated that warning into formal demands. Lothian’s correspondence with the company from July 5 through October 7 was made available in a PDF, according to the report.
“If you have knowledge of the DisplayLink DL3 control-plane engagement sequence, or ideas for isolating a whole-bus timing/ordering property a per-channel diff cannot see, help would be very welcome.”
— Mike Lothian, in his June 17 request for help
The Patents and Project Status
The available report does not specify which of the 125 listed patents Synaptics believes apply to Vino, which elements of the project it considers covered, or what technical basis supports those allegations. The material provided also does not report a court decision, a filed lawsuit, or an independent legal assessment of infringement. Synaptics’ claims should therefore be understood as allegations made in its correspondence, not as findings established by a court.
The report describes Lothian as having stopped work for now, but does not establish whether the project has been permanently abandoned, whether the parties reached any agreement, or whether Synaptics later changed its position. It also remains unclear whether the company will respond publicly or clarify the patent claims. The account is based on LWN.net’s reporting and correspondence supplied by Lothian; no separate Synaptics response is included in the source material.
Whether Development Resumes
The immediate question is whether Lothian will resume Vino development or comply with the demands in Synaptics’ letter beyond halting work. The report does not provide a deadline or describe a court filing, so no legal hearing or other formal proceeding can be identified as the next milestone from the available information.
Further clarity would require a response from Synaptics on the patents and alleged infringement, or additional information from Lothian about the project’s status. Until then, the reported position is that work has stopped for now and Linux users continue to rely on the existing DisplayLink software and EVDI support.
Key Questions
What is Vino?
Vino is an unfinished Rust-based Linux driver that Mike Lothian began developing for DisplayLink hardware. He posted an early request-for-comments patch series in June and asked developers for help with a dock communication problem.
Why did Synaptics contact Lothian?
Synaptics said Vino appeared to be moving beyond interoperability work and toward implementing technology it believed was covered by its patents. The company later sent a cease-and-desist notice. Those are Synaptics’ allegations; the source material does not report a court ruling that Vino infringes a patent.
Did Synaptics identify the patents it says Vino infringes?
The letter included an appendix listing 125 patents, according to the report, but it did not specify which patents might apply to Vino or identify the project elements at issue.
What does the dispute mean for Linux DisplayLink users?
For now, Lothian has stopped work on Vino, so users should not treat it as a completed alternative driver. Linux users remain dependent on DisplayLink Manager and EVDI and the hardware support available through those projects.
Has the dispute gone to court?
The source material describes a warning email and a cease-and-desist letter, but does not report a lawsuit or court decision. The legal status beyond the company’s demands remains unclear from the available account.
Source: lwn.net
