A developer reverse-engineered the open-source DisplayLink driver Vino (with Claude's assistance), received a cease-and-desist letter from Synaptics' lawyers demanding code destruction and weekly damages, sparking a dispute over patent boundaries.Author and source: AIBase
A hobbyist’s personal project has been pushed to the brink by a cease-and-desist letter from a chip giant. Synaptics recently sent a cease-and-desist letter to Lothian, an open-source enthusiast who developed the "Vino" driver, demanding he halt, remove, and destroy this Linux driver that provides open-source support for DisplayLink devices—while he was writing the code, he even enlisted Claude AI as assistance.
Who did the open-source alternative, reverse-engineered, upset?
DisplayLink technology connects external monitors to computers via USB. Although Synaptics provides Linux support, it requires bundled proprietary, closed-source components. Lothian’s Vino took an independent reverse-engineering approach, leveraging Claude to assist development and successfully running on the Dell D6000 dock, with the goal of getting the成果 integrated into the Linux kernel. This directly triggered Synaptics’ sensitivities: legal head Andrew Betman explicitly stated that publicly revealing the implementation would enable competitors to reverse-engineer its proprietary technology and erode its competitive advantage.
Patent club, priced weekly
Synaptics accuses Vino of infringing two UK patents (GB2484736, GB2485613), demanding not only the removal of code, documentation, and materials submitted to kernel maintainers, but also threatening to seek $25,000 in damages if corrections are not made within a specified deadline, with an additional $25,000 added every seven days thereafter. Lothian counters that he is merely an individual contributor and has not infringed, challenging the validity of the patents—arguing that some of the technology was already publicly disclosed prior to filing. The Vino repository has since been made private, while the correspondence and responses have been posted to the Linux kernel mailing list, becoming a public matter under scrutiny by the open-source community.
