The AI-Assisted Linux Driver for DisplayLink Gets Legal Notice
Before we dive into the matter, you first have to understand what DisplayLink is. It is a proprietary graphics transport technology that lets computers connect to one or more external displays over USB, using docks or adapters built around DisplayLink chips.
It works by compressing display data on the host computer and sending it to a chip in the connected device. The chip then decodes it for output to monitors through interfaces such as HDMI or DisplayPort.
On Linux, this support can rub some people the wrong way due to its closed-source nature. That is where Mike Lothian’s (FireBurn) Vino comes in as an open alternative.
Unfortunately, Synaptics owns DisplayLink and has sent Mike cease-and-desist letters alleging that he infringed its DisplayLink patents with his project.
What’s Vino?
Vino is a driver that lets the Linux kernel talk to DisplayLink docks directly. It is meant to replace DisplayLink’s closed-source software and the open source EVDI kernel module that sits beside it.
Mike wrote it with help from Claude Code, and the first version reached the kernel mailing list in June, unfinished. He had faced a communication issue between the dock and the driver and asked other developers for help.
In early July (courtesy of LWN.net), he emailed a Synaptics employee for guidance and mentioned his Rust rewrite of EVDI. About two weeks later, a different employee replied.
That reply said his Rust rewrite of EVDI was not a thing of concern. Rather, the concern was the DisplayLink protocol and codec, which Synaptics believes are covered by its patents. Lawyers get involved
A cease-and-desist letter followed on August 17. It told Mike to stop development and withdraw anything he had submitted to maintainers and hosting sites, with a signed confirmation due by August 28.
An appendix listed over 125 patents without saying which applied. Mike posted a working version 3 of Vino on August 26 and asked Synaptics the next day which claims they had in mind.
The answer came in October as claim charts. They map one claim from each of two patents, GB2484736 and GB2485613, to his source code.
The October 5 letter said Synaptics would seek $25,000 for the cost of preparing those charts if Mike missed an October 11 deadline, with the figure rising by at least $25,000 each week.
Mike replied on October 6 (message 8) with an offer to pause public work on the encoding code the charts point to if Synaptics paused the deadline and the weekly charge. He also asked about licensing that code for non-commercial use.
On October 7, Synaptics said it would grant no patent license or promise not to sue and set October 18 as a final deadline.
What I can see so far is a very aggressive patent infringement witch hunt against a lone open source developer who was quite open to communication.
Synaptics took about three weeks to answer his request for specifics, then followed with a potentially life-ruining $25,000 demand that compounds weekly.
Clean room design quirks
Mike describes Vino as a clean-room driver and says he reverse engineered it from captured USB traffic and vendor programs.
If you didn’t know, in a clean-room recreation, one party studies the original implementation, then writes a description, and a separate party builds the new code from that description alone.
It is meant to act as a defense against copyright claims because it shows nothing was copied. Synaptics’ July reply argues that clean-room or independently written code can still infringe a patent.
The timing
Vino also lands in a busy stretch for AI-assisted reverse engineering, from smart TV cleanups to office suite clones. Legal pressure has reached other AI-built projects too.
Mike has already taken down the Vino repository in response to the demands, and Synaptics has not made a public statement so far.
Only time will tell what happens to the work, and I hope someone forked it before it went offline, as that would give others a good starting point to build on.
Comments
Fuck software patents.
Period.
That truly sucks.
Not in the least bit because displaylink is used in many docks, all of which are barely usable in Linux because the driver support is non existent. If anything, this could BOOST their sales.
Secondly, I really feel like that AI stamp was just added to the title for clickbait. It didn’t matter in the slightest for the issue at hand: Company threatens to ruin developer for fixing their own shit.
Exactly, the real issue is that they claim that people aren’t allowed to make clean room implementations of software that works with their hardware.
I could be wrong here, but in the article it says that they are alleging that the implementation violates patents not copyright, as far as I understand, patents prohibit fully independent implementations and even fully indepent designs that happen to come to same mechanisms independently as those in the patent, that’s the purpose of patents, now of course I completely disagree with their insane premise altogether, but they are different and distinct from copyright and give far more overreaching power to the holder than copyright
This is a really interesting story. “Clean room” implementations might clear copyright, but copyright and patents are two different things. Apparently, the developer is challenging the scope of the patents as what they cover is common domain (they just tweak out how some of it works) (https://tech.yahoo.com/ai/claude/articles/synaptics-sends-cease-desist-order-110000800.html).
DisplayLink have always been touchy about their IP and the lack of open source drivers is the main reason I don’t consider their hardware anymore. I guess they want to stop it getting merged so they don’t end up in a patent battle with OIN.
Sorry what’s OIN?
Open Innovation Network is a patent pool to protect open source projects from patent trolls. It’s basically mutually assured destruction if the pool has any patents covering products you sell.
This is an incredibly bad idea on his part. Patents and copyright are not the same thing. It doesn’t matter at all if he genuinely reverse engineered it, if it violates their patent they have every right to sue him, and they’ll win. Claiming it’s a witch hunt also doesn’t matter. The court is not sympathetic to lone devs violating patents.
It used to be we could protect software with both copyrights and patents, because it was really hard to duplicate a large project. Now, with AI able to shit out a somewhat working implementation in a few days, we only have patents.
And software patents are a terrible idea, that should never exist.
They are certainly abused, but without them, there’s literally no protection from a big company stealing an entrepreneur’s idea and undercutting them. (Like what Facebook did to Snapchat.)
They should be reformed, but I think providing protections to inventors is not inherently a bad idea.
I am speaking as an inventor who has been issued a software patent, so take what you will from that. I’m happy that my idea can’t just be stolen by Google or Microsoft. (Or some slop slinger, for that matter.)
The problem here (similar to media codecs) is patents on interop, where if someone uses patents in a product or service, that pushes the patents onto not just people trying to directly compete, but also onto anyone trying to interoperate with that product or service, through no fault of their own. Thus abusing patents to block interoperability.
In reality, patents and copyright almost never protect the “little guy,” and are exclusively to the benefit of large corporations. You don’t have functionally unlimited resources to throw at the legal system; They do.
It is an idea that sounds reasonable on its face, but falls apart badly when you consider the realities of enforcement.
Sign in to comment. Sign in