this post was submitted on 07 Aug 2024
280 points (98.3% liked)

Technology

59569 readers
3825 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

cross-posted from: https://lemm.ee/post/38967838

Back in February of this year you may recall the interesting news that was announced on Phoronix that AMD Quietly Funded A Drop-In CUDA Implementation Built On ROCm: It's Now Open-Source. That open-source ZLUDA code for AMD GPUs has been available since AMD quit funding the developer earlier this year. But now the code has been retracted. It's not from NVIDIA legal challenges but rather AMD reversing course on allowing it to be open-source.

As explained in that article earlier in the year, AMD had quietly funded the ZLUDA developer Andrzej Janik to bring his CUDA-compatible implementation to AMD GPUs and atop the ROCm software stack. ZLUDA start off originally as an open-source CUDA implementation for Intel graphics built atop the Level Zero (hence the ZLUDA name) software stack. While working on ZLUDA, he got it working out rather nicely and various CUDA applications running seamlessly on AMD GPUs as shown and benchmarked in my prior article. But then AMD decided to quit funding the project.

The agreement was reportedly that if/when the contract ended, the ZLUDA code could be open-sourced. That's what happened back in February. But now that code has been retracted from the official public GitHub repository. It's not from legal threats from NVIDIA as one might imagine given its working to support CUDA on non-NVIDIA hardware, but rather from AMD itself.

Janik also noted in his announcement that he had a NVIDIA GameWorks implementation working on AMD GPUs but sadly that code will now never be open-sourced.

Andrzej Janik notes he wants to "rebuild ZLUDA" moving forward and is working on project funding. What wasn't clear from his message whether this means a new ZLUDA focused on the original Intel GPU plans or a new clean sheet design for AMD GPUs. When I asked Janik about it, he's still exploring options.

It will be very interesting to see where ZLUDA goes from here but disappointing that the prior open-source code has been retracted. The GitHub repository is at vosen/ZLUDA while we are eager to see its future direction.

you are viewing a single comment's thread
view the rest of the comments
[–] yu_cosmic@sh.itjust.works 44 points 3 months ago (9 children)

ZLUDA being 6 months open source before it was taken down gives me hope that the project might probably be forked into something else or in the same path as originally intended

[–] bruhduh@lemmy.world 8 points 3 months ago (7 children)
[–] mikwee@thebrainbin.org 4 points 3 months ago (6 children)

Wasn’t that built by some teenagers who abandoned it?

[–] EddoWagt@feddit.nl 4 points 3 months ago (1 children)

Probably, but it runs pretty well and is at least still available

[–] NinjaCheetah@sh.itjust.works 5 points 3 months ago (1 children)

Ryujinx is also freely available and doesn’t have the weird past that Yuzu did, and also wasn’t forced to shut down.

I’m honestly not sure why everyone is holding on to Yuzu so strongly when Ryujinx has been a better option for a while now.

[–] EddoWagt@feddit.nl 1 points 3 months ago (1 children)

Yuzu used to run better so I just kinda stuck to it, gotta try ryujinx out

[–] PolarisFx@lemmy.dbzer0.com 1 points 3 months ago

Ive always had issues with RyujinX, yuzu just worked.

load more comments (4 replies)
load more comments (4 replies)
load more comments (5 replies)