Earlier quoted context omitted.
Probably not. Clean room RE is serious business, projects like Dolphin have to carefully vet contributors to remain legal.
Everyone says this, and then exactly zero cases are cited in support of or against this creative legal theory known as "clean room RE." No statute defines "clean room RE" and there's basically no relevant litigation establishing case law.
Building a Linux GPU Driver for the M4 Mac Mini in One Month
171–180 of 293 posts
Re: Building a Linux GPU Driver for the M4 Mac Mini in One Month
#172Earlier quoted context omitted.
> If an LLM reproduces copyrighted material (which is very hard to verify) then the lawsuit from the copyright owner can still sink even robustly funded projects. Do you have many examples of this actually happening that you could share? I really don't see how this issue is going to be feasible for courtrooms to deal with in a world where big tech are bragging about large percentages of all their code being produced…
In the 90s aircraft manufacturers basically stopped whole segments of the market (anything smaller than a piston twin) due to litigation. I wouldn't be horribly surprised to find we spend the next 10 years fighting about this stuff in court.
LLMs have been firing out a lot of code for a year or 2 now at least, so I would have thought we'd start seeing some court cases by now?
Re: Building a Linux GPU Driver for the M4 Mac Mini in One Month
#173Earlier quoted context omitted.
> If an LLM reproduces copyrighted material (which is very hard to verify) then the lawsuit from the copyright owner can still sink even robustly funded projects. Do you have many examples of this actually happening that you could share? I really don't see how this issue is going to be feasible for courtrooms to deal with in a world where big tech are bragging about large percentages of all their code being produced…
Why wouldn't it be feasible for Apple, with an unlimited war chest, to go after Asahi? I am not saying they will, but it is certainly possible for them.
Business and code production would grind to a halt whilst basically every big tech company shares it's entire codebase with every other tech company for discovery. It's basically MAD.
And if it was feasible, given we've had a couple of years of all the big tech companies heavily using LLMs, there should be some notable court cases by now, surely?
Re: Building a Linux GPU Driver for the M4 Mac Mini in One Month
#174Earlier quoted context omitted.
Everyone says this, and then exactly zero cases are cited in support of or against this creative legal theory known as "clean room RE." No statute defines "clean room RE" and there's basically no relevant litigation establishing case law.
Who volunteers to be the shmuck that fights Nintendo's lawyers in court? Who's funding the defense against Apple? It's safest to err on the side of plausible deniability, any proximity to OEM software increases liability if things go wrong.
Re: Building a Linux GPU Driver for the M4 Mac Mini in One Month
#175Earlier quoted context omitted.
In the 90s aircraft manufacturers basically stopped whole segments of the market (anything smaller than a piston twin) due to litigation. I wouldn't be horribly surprised to find we spend the next 10 years fighting about this stuff in court.
I'm fully aware of lots of times powerful companies have used the courts to protect their business. My point is basically all of the powerful companies are elbow deep in LLMs to the extent of some sort of mutually assured destruction if they were to start court cases like this. LLMs have been firing out a lot of code for a year or 2 now at least, so I would have thought we'd start seeing some court cases by now?
Re: Building a Linux GPU Driver for the M4 Mac Mini in One Month
#176Earlier quoted context omitted.
Why wouldn't it be feasible for Apple, with an unlimited war chest, to go after Asahi? I am not saying they will, but it is certainly possible for them.
Because if it's feasible for any company with a war chest to start a court case about a competitor maybe having a matching line of code to theirs via an LLM, then basically every single company with a warchest would be at war with eachother, because they're all using LLMs. Business and code production would grind to a halt whilst basically every big tech company shares it's entire codebase with every other tech compa…
Re: Building a Linux GPU Driver for the M4 Mac Mini in One Month
#177Author, do TouchID next.
Fyi,there's a comment on the Omarchy-M annoucement [0] referencing Touch ID > Dj is writing the GPU drivers, and got Touch ID working by talking directly to the Secure Enclave [0] https://omarchy.org/news/2026/09/introducing-omarchy-m/
It's also interesting to see all this work seems adjacent to Asahi's own.
Re: Building a Linux GPU Driver for the M4 Mac Mini in One Month
#178Earlier quoted context omitted.
> upstream projects anyways so any distro can just work This may never end up working like that, considering how complicated installation is, comparatively speaking, and how macOS is still pretty much required to be installed.
You can make the Linux installation on Apple Sillicon Macs pretty painless nowadays. One terminal command on macOS, reboot to Linux, run one script - voila.
Re: Building a Linux GPU Driver for the M4 Mac Mini in One Month
#179Earlier quoted context omitted.
No judge I’ve ever met gave a damn how much a party spent on legal resources. With rare exceptions, they care a great deal about achieving justice, and often bend over backwards to help indigent parties avoid prejudicing themselves. Keep in mind that there are no indigent parties in this debate; both major IP rights holders and the frontier AI companies are well capitalized. (I worked in a federal district court for…
The problem is that money buys lawyers, and you need those to get justice. If the other side spends more, you are likely to lose.
Re: Building a Linux GPU Driver for the M4 Mac Mini in One Month
#180I am not by any means a copyright lawyer, so can anyone enlighten me on if it is a good idea for upstream projects to accept such kind of code from an ex-Apple employee, especially since Apple is currently suing OpenAI.
Great observation, two things: - During my time at Apple I never saw any of the macOS source code, at all, even for userspace components. I had not even heard of things like SPTM. - I have not worked there since June 2025 I don't believe that there's any risk due to my former Apple employment. As another example, WINE does not ban all former Microsoft employees, they just ban anyone who has ever looked at the Windows…
It's an interesting example given that Wine considers deriving code from traces of original components (like hypervisor traces) tainted and also bans LLM contributions for legal considerations: https://gitlab.winehq.org/wine/wine/-/wikis/Clean-Room-Guide...