Live data from Hacker News

Documentation for the AMD 7900XTX

github.com

1–10 of 154 posts

Re: Documentation for the AMD 7900XTX

#6
post #5

Can anyone explain what this level of documentation allows? Could someone make a CUDA compatible tool with this?

Yeah, HIP and ZLUDA already exist.

Crucially, what the documentation doesn't allow is fixing bugs in the firmware/microcode (all the .bin files).

Re: Documentation for the AMD 7900XTX

#8
So for reference, this geohot is George Hotz who has a company Tiny Corp [0] in the space. Among a long list of things, he had a moment in the spotlight recently for a long rant [1] where he "gave up on AMD" because their drivers sucked more than he expected. The situation is reasonably complex - AMD have some programmers working on ROCm who seemed to be operating at standard fare when that is really not what AMD needs right now (I personally, suspect there is/was a PM in a key position who didn't "get it", although I am not sure what it is either). As far as I know it got the attention of Lisa Su.

I'm cheering him on, even though his complaints were a little melodramatic. My experience is the driver technically supports everything I could possibly want. The problem is if I spend an evening trying to do anything with OpenCL or ROCm the kernel hard-locks and I go to bed early. If the problem inside is what it looks like from the outside (repeating myself, a key manager somewhere just doesn't get the space) they really need some pressure from grumpy customers like George to realign their software development process.

That context might be related to this particular case. I see a suspicious folder called "crash" in this repo.

[0] https://tinygrad.org/

[1] https://www.youtube.com/watch?v=Mr0rWJhv9jU - as I recall he ran the demo suite and it crashed.

Re: Documentation for the AMD 7900XTX

#10
post #8

So for reference, this geohot is George Hotz who has a company Tiny Corp [0] in the space. Among a long list of things, he had a moment in the spotlight recently for a long rant [1] where he "gave up on AMD" because their drivers sucked more than he expected. The situation is reasonably complex - AMD have some programmers working on ROCm who seemed to be operating at standard fare when that is really not what AMD nee…

And follow-up of that video: https://geohot.github.io/blog/jekyll/update/2023/06/07/a-div...
Post reply on HN