This is an utterly confusing and self sabotaging system. I had lots of issues with displaylink on a Mac. (Daily crash on the first video call of the day for some reason) Does the support care? No. Can I debug using the logs? No - THEY'RE ENCRYPTED! And now they're fighting for customers to not be able to use the hardware.
Save yourself time and money - avoid DisplayLink.
At least part of the effort was posted in mailing list though https://lwn.net/Articles/1078474/ - I hope the recent repository has been mirrored too.
> That "Vino" driver for DisplayLink driver was a clean-room reverse-engineered DisplayLink driver that was developed in part by AI and written in Rust.
It is my strongly-held opinion that, regardless of what you think about AI in general, reverse engineering projects ought to stay as far away as possible from LLM code gen as possible. They are a very easy and straightforward way for a copyright owner to claim access to their code, since basically ALL code was trained on. Unless you have hard evidence the particular bit of code you want to RE was not in the training set, you should not use an LLM to reverse-engineer or rewrite it.
This is not a moral argument; as much as I hate AI companies playing fast and loose with other people's work, the underlying arguments that make RE legal work much better if you do not look at the source code. And while US judges are straining to keep AI training fair use, that does not make the AI a copyright laundering device. A copyright owner can absolutely reach through a fair use to get to you. Think of it like if you downloaded 10 different YouTube video essays on the same movie and attempted to stitch them together into a normal copy of the underlying movie. Obviously, your use has a different (and worse) legal status than the reviews do.
[delayed]
I hope someone has archived the repository so it can be hosted somewhere where those ridiculous Western copyright and patent laws don't apply.
This is an utterly confusing and self sabotaging system. I had lots of issues with displaylink on a Mac. (Daily crash on the first video call of the day for some reason) Does the support care? No. Can I debug using the logs? No - THEY'RE ENCRYPTED! And now they're fighting for customers to not be able to use the hardware.
Save yourself time and money - avoid DisplayLink.
At least part of the effort was posted in mailing list though https://lwn.net/Articles/1078474/ - I hope the recent repository has been mirrored too.
There's also https://github.com/durhamaustin9/DisplayLink-Drivers-Reconst... you may want to preserve locally.
> That "Vino" driver for DisplayLink driver was a clean-room reverse-engineered DisplayLink driver that was developed in part by AI and written in Rust.
It is my strongly-held opinion that, regardless of what you think about AI in general, reverse engineering projects ought to stay as far away as possible from LLM code gen as possible. They are a very easy and straightforward way for a copyright owner to claim access to their code, since basically ALL code was trained on. Unless you have hard evidence the particular bit of code you want to RE was not in the training set, you should not use an LLM to reverse-engineer or rewrite it.
This is not a moral argument; as much as I hate AI companies playing fast and loose with other people's work, the underlying arguments that make RE legal work much better if you do not look at the source code. And while US judges are straining to keep AI training fair use, that does not make the AI a copyright laundering device. A copyright owner can absolutely reach through a fair use to get to you. Think of it like if you downloaded 10 different YouTube video essays on the same movie and attempted to stitch them together into a normal copy of the underlying movie. Obviously, your use has a different (and worse) legal status than the reviews do.
Also, fuck Synaptics.