This week's running story is AI's collision with open source. On Monday a kernel maintainer quit reviewing because of the patch flood. On Wednesday, a different kind of blow landed: a company using patent law to kill an open source driver, one that happened to be written with an AI's help.
What Vino was
DisplayLink is Synaptics' proprietary system for pushing video over USB to docks and adapters. On Linux it has always been an uneasy fit: you need the vendor's closed-source software and the open EVDI kernel module beside it, and plenty of users find it flaky. Mike Lothian, who goes by FireBurn, got fed up with the crashes and wrote Vino, a Rust driver that lets the kernel talk to DisplayLink docks directly, replacing both the blob and EVDI. He built it with help from Claude Code. By the end it worked across three generations of docks, according to It's FOSS. In June the first, unfinished version hit the kernel mailing list. Source: https://itsfoss.com/news/synaptics-vino-fiasco/
The timeline reads like a trap
In early July, Lothian did the decent thing and emailed Synaptics about his Rust rewrite of EVDI. Two weeks later an employee replied: the rewrite itself was not a concern. The concern was the DisplayLink protocol and codec, which Synaptics believes its patents cover. On August 17 the cease-and-desist letter arrived: stop development, withdraw everything submitted to maintainers and hosting sites, sign a confirmation by August 28. The appendix listed over 125 patents without saying which ones applied. Lothian shipped a working Vino 3 on August 26 anyway, then asked the obvious question: which claims do you actually mean? October brought the answer, claim charts mapping one claim each from two British patents, GB2484736 and GB2485613, to his source. He has since taken the repository down. Synaptics has made no public statement. Source: https://itsfoss.com/news/synaptics-vino-fiasco/
The AI angle cuts both ways
Vino was AI-assisted, and that is where this story stops being a routine patent fight. The threatening letter came with 125 patents attached, but when forced to be specific, Synaptics pointed to two. That gap is the whole game: the initial blast was not a legal argument, it was a compliance cost, calibrated to be too expensive for one developer to fight, regardless of merit. Now add the fact that the code was written with Claude. If AI tools lower the cost of writing a driver by tenfold, but the cost of defending one stays exactly where it was, the balance of power between hardware vendors and the open source community does not shift the way the hype promised. It's FOSS also notes this lands in a busy stretch for AI-assisted reverse engineering generally, from smart TV cleanups to office suite clones. Vino is the first high-profile test of what happens when that work collides with an entrenched patent holder. The answer so far: the repo comes down. Source: https://emergent.sh/news/synaptics-patent-threat-kills-claude-written
The part Synaptics should think about
There is a respectable argument that a company can defend its patents. There is a much weaker argument for doing it this way. Lothian emailed them before there was even a fight, got told the rewrite was fine, and got lawyered anyway. DisplayLink dock owners on Linux are not a pirate market, they are paying customers whose hardware works badly on an OS the vendor half-supports. A working community driver would have cost Synaptics nothing and bought goodwill it cannot get from a cease-and-desist. Hardware vendors used to learn this the hard way: Nvidia spent years as open source's favourite villain before changing course, while AMD and Intel spent the same years collecting the goodwill Nvidia burned. Synaptics makes chips that go into other people's products, which means it depends on ecosystems it does not control. This is how you lose them.
What happens next
LWN reported yesterday that Synaptics' patent claims have already stopped kernel-side work on DisplayLink drivers, so Vino's takedown is not the end of the story. The likely next act is a clean-room effort, developers who have never seen Vino's code reimplementing the protocol from scratch, which is slow, expensive, and exactly what the claim charts were designed to force. Or the community shrugs and DisplayLink on Linux stays a second-class experience, which quietly pushes dock buyers toward hardware that treats Linux as a first-class citizen. Either way, one developer's inbox and two British patents just decided the answer for a whole product category.