The project started as an independently developed ZLUDA, meant for Intel GPUs. AMD started funding development of the project, expanding its scope to also work on AMD GPUs, with the condition that if AMD abandons it, the code would become open source. This happened a few months ago, but now for some reason AMD backtracked and pulled the open-source code for reasons we don't know. AMD is usually pretty good with this stuff though, so I'm interested to find out what their motives are.

[–] vikingtons@lemmy.world 19 points 3 months ago* (last edited 3 months ago)

I'm familiar with the timeline of events, it's just that this post title is intentionally obscure. As for why, it could be due to a recent enforcement by NVIDIA of a specific part in their EULA

Nvidia has banned running CUDA-based software on other hardware platforms using translation layers in its licensing terms listed online since 2021, but the warning previously wasn't included in the documentation placed on a host system during the installation process. This language has been added to the EULA that's included when installing CUDA 11.6 and newer versions.

The restriction appears to be designed to prevent initiatives like ZLUDA, which both Intel and AMD have recently participated, and, perhaps more critically, some Chinese GPU makers from utilizing CUDA code with translation layers.

My guess is that either AMD were directly contacted or preemptively closed off a legal loophole.

E: I was wondering where I recognised this username from

[–] j4k3@lemmy.world 2 points 3 months ago* (last edited 3 months ago) (1 children)

Probably, AMD was only doing open source because Nvidia wasn't. Now that it is no longer as advantageous since Nvidia is open sourcing (still no nvcc !!!), it is less advantageous. It's typical capitalism conservative terminal brain rotting cancer. They don't do the right thing unless it is profitable to do so. There is no big picture or ethics; just criminals and quarterly reports.

[–] vikingtons@lemmy.world 13 points 3 months ago (1 children)

...or it was found to violate CUDA's EULA and taken down as a precaution https://www.tomshardware.com/pc-components/gpus/nvidia-bans-using-translation-layers-for-cuda-software-to-run-on-other-chips-new-restriction-apparently-targets-zluda-and-some-chinese-gpu-makers

[–] hellofriend@lemmy.world 1 points 3 months ago (1 children)

What's stopping Windows from banning WINE if this is the case?

[–] vikingtons@lemmy.world 1 points 3 months ago* (last edited 3 months ago)

I suppose if zluda interpreting native cuda code on other IHV platforms is "illegal", whereas HIP can legally be used to translate CUDA to ROCm at runtime, I would equate WINE to HIP, as it translates Windows API calls to POSIX for linux and Unix systems.

I'm not sure Microsoft have a leg to stand on with a move like this given their legal troubles in the past around becoming a monopoly. Maybe they don't see as much threat given the low share of linux and unix (including mac) desktops

There's still a bit of friction around actually leveraging WINE on non-Windows systems, with Proton being a relatively recent outlier as it offers you a mostly plug and play experience via steam, lutris and others.

For nvidia, zluda can allow other IHVs with significantly cheaper DC solutions to undercut them with no friction whatsoever.