61–70 of 154 posts
Earlier quoted context omitted.
[flagged]
> have him fix it to his liking Like when he strolled into Twitter, acted like he knew better than everyone, delivered nothing and then left. There is far more to achieving things in large companies than simply having great technical skills.
Earlier quoted context omitted.
NVidia is making boatloads of money because their driver works and they have a software library called CUDA that accelerates neural networks. Nobody expects AMD to match them, but George thought they could at least write a GPU driver. If AMD can get that driver out, then George could provide a competitor to CUDA (for neutral networks only). They'd both make boatloads of money. However, AMD was less capable than expec…
Slight mistake in your description: CUDA is an out of date API that was replaced by Khronos's own official compute APIs. Khronos is a standards consortium that Nvidia is a founding member of. Although the marketing department at Nvidia still pushes for greenfield CUDA codebases, no new code should be written in it, and they should opt for open source international standards only. Khronos APIs are implemented by over…
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…
>I'm cheering him on, even though his complaints were a little melodramatic. I've really soured on him when he literally went "I'm going to fix twitter search, hire me elon" and then went to public saying "Hey, want an internship? Fix it, and then MIT license your code(so he could use it lol), and maybe we can talk - oh btw I have no real authority to give anyone an internship." He might be a brilliant programmer and…
Earlier quoted context omitted.
Genuine question for you then, why are you investing your time reversing their firmware if it sounds like you think they're failing/will fail? Why not just "adopt" the golden child/golden standard NVIDIA now for your usecase, reverse that (if needed) and move on? Genuinely curious what you gain from trying to make AMD work/investing in AMD on your end here. Is it that you see a value proposition through the "muck" of…
This is my weekend hobby, I'm learning about GPUs. Besides, I'd like to see competition to NVIDIA. From a business side, tiny corp is selling boxes with both AMD and NVIDIA, we'll let the user choose how much they value money vs pain.
[0] iree.dev
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…
>I'm cheering him on, even though his complaints were a little melodramatic. I've really soured on him when he literally went "I'm going to fix twitter search, hire me elon" and then went to public saying "Hey, want an internship? Fix it, and then MIT license your code(so he could use it lol), and maybe we can talk - oh btw I have no real authority to give anyone an internship." He might be a brilliant programmer and…
His work for jailbreaking/actually being able to own the devices we pay for back in the iPhone+PS3 days was and is still inspiring, but I think being so smart and encountering so much bullshit in his life kind of led him to the 'rockstar coder I know better than you regardless of domain' personality, and that leaves him both a bit grating and underquipped to drive consensus. He's still a great wrench to throw into the bullshit machine though, and the guy is smarter and more accomplished with computers than I'm ever likely to be.
Earlier quoted context omitted.
> More concretely, what they open sourced calls closed source functions that run on the GPU which is where all the bugs are, and causes all the crashes. In particular, what they did was open source the drivers but not the firmware , and then when the firmware has bugs nobody outside the company can fix it because it's not open source.
Yes, that's a problem, but it's also a bit of an unfair dunk. After all, your CPU almost certainly runs firmware with all the same issues. Not to mention all other GPUs from all other vendors. Despite all of the noise-making, I don't think anybody has really convincingly made the case that the firmware quality is the main issue here, as opposed to the quality of the rest of the stack.
CPUs don't really have firmware in the same sense. CPUs expose basic primitives (machine instructions). Modern CPUs will translate them to micro-ops in microcode instead of executing them directly, but the mapping is relatively simple and bugs are correspondingly uncommon.
The GPU firmware is doing something complicated, and therefore buggy, but you're required to use their complicated buggy closed source code because it also doesn't directly expose simpler primitives you could use to build your own alternative to it.
> Despite all of the noise-making, I don't think anybody has really convincingly made the case that the firmware quality is the main issue here, as opposed to the quality of the rest of the stack.
The rest of the stack should be an abstraction layer that makes programmers not have to care what kind of hardware is under them, the same as they generally don't have to care if their CPU is from AMD or Samsung. But then you need the code to translate from that abstraction to the hardware, and that code needs to work. Which can either be accomplished by the vendor providing working code, or by the vendor providing sufficient documentation and source code for someone else to write working code. Providing neither of these is not effective.
What AMD should be doing at this point is both. Open source the existing firmware so that people who are trying to use their hardware right now have the ability to fix any problems they encounter themselves, while the company uses the money they now have to address their existing technical debt, which nobody reasonably expects to happen overnight. But will happen faster when it's not only the company but also the users working on solving the problem.
I used to be an AMD diehard fan. Bought their processors and GPUs for close to 20 years until I simply couldn't take it anymore - 5 years ago I started buying NVIDIA GPUs with Intel CPUs and honestly never looked back. Sure I pay more, but it's worth paying more for reliability and software support. Anything else and I'm losing money out of ideology to give to a business that doesn't have its act together.
I used to be an AMD diehard fan. Bought their processors and GPUs for close to 20 years until I simply couldn't take it anymore - 5 years ago I started buying NVIDIA GPUs with Intel CPUs and honestly never looked back. Sure I pay more, but it's worth paying more for reliability and software support. Anything else and I'm losing money out of ideology to give to a business that doesn't have its act together.
It's always intriguing to see other people's takes. I'm in nearly the complete opposite boat: in recent years I've switched to AMD and it feels like all of my hardware problems have gone away.
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…
It was particularly hard to listen to himself admit that he basically became unpaid QA for AMD. Like, dude, you’re making the same junior mistake people writing apps for the App Store make. It’s not your platform.
It's also worth noting that tinygrad is bypassing as many layers of AMD's software platform as they can get away with (MIOpen, ROCm, and even the userspace GPU driver).