7 ms·
For what it's worth, AMD is also incredibly proprietary. The drivers being open source really helps with compatibility and your kernel, but you're still interac
by parker_mountain 3y ago
For what it's worth, AMD is also incredibly proprietary. The drivers being open source really helps with compatibility and your kernel, but you're still interacting with a massive computer running it's own OS with its own trusted code solution. And that computer also has DMA to your computer.
I would consider their open efforts to be "not serious" for anyone but the consumer space - games, desktop users, maybe even professional text editors. If you're using the GPUs for "professional" applications in a one-off scenario, even AMD falls short.
I'm honestly not sure what the moral of this story is.
- wmf 3y agoThe moral is that PSP FUD has nothing to do with AMD's lack of success in AI.
- beebeepka 3y agoAre they "incredibly proprietary" compared to the competition? Clearly they aren't. Nvidia offers blobs in both consumer and professional markets. Even going to the extent of gimping performance hardware through drivers on more than one occasion. That said, I think AMD isn't really competing with Nvidia. Sure, their R&D budget is smallish but it feels like they're somewhat fine with the current status quo.
- paulmd 3y ago> Nvidia offers blobs in both consumer and professional markets So does AMD. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu https://git.kernel.org/pub/scm/linux/kernel/git/firmware/lin... And while they have an open version of the userland, it's also missing features compared to the proprietary one, etc. Besides, in the end it truly hardly matters whether the firmware is loaded at runtime or lives in updateable flash. It's still not "your PC" in the Stallman sense either way, it's been tivoized regardless of whether firmware is injected at runtime or during assembly. You cannot load unsigned firmware on AMD anymore either, firmware signing started with Vega (iirc) and checksums now cover almost all of the card configuration similar to NVIDIA. Firmware is also the only way to get proper HDMI support... which is why AMD still does not support HDMI 2.1 on linux. HDMI Forum will not license the spec openly and implementations must contain blobs or omit those features. https://gitlab.freedesktop.org/drm/amd/-/issues/1417 https://gitlab.freedesktop.org/drm/amd/-/issues/1417
- beebeepka 3y agoHey, I am not white knighting for AMD here. For all we know, they could only have been pursuing open standards because they've been forced to, as the underdog. Can we really assign blame to them specifically for not fighting the hdmi forum on our behalf?
- amunicio 3y ago> I'm honestly not sure what the moral of this story is. That people will go with what is easier and works? That open source and open standards don't win by default? That it takes a lot of persistence and effort.
- delfinom 3y ago>own OS with its own trusted code solution AMD is working on moving to things like the open source form of AGESA. They plan to start deploying openSIL by 2026.
- throwawaymaths 3y agoThe moral of the story is that Nvidia invested a lot more in low level software developers for their GPU solutions and AMD did not, and it shows. "Open source" by itself is not a magic dust you can sprinkle on your projfcts that will make your software work well.
- newjersey 3y agoI personally don't have any insider information but just wanted to add what your saying fits with the meta on the gaming community side where commentators are frustrated that nVidia has so much hubris that they think they can just sell essentially last generation level technology without the step up (I think it was 3xxx vs 4xxx or something like that where you'd expect the 4060Ti to be at least as good as 3070Ti) and just trying to make up for it in "software". It probably takes a lot of confidence in your software developers to make this kind of decisions.
- gary_0 3y agoA company that goes open source might get the icing for free, but they still have to bake the cake themselves.
- williamDafoe 3y agoAMD's focus was always on pure compute power at a good price. And they always beat NVidia at that game. AMD cards always had the highest hash rate per dollar in crypto mining. AMD has 100% of the console market and the fastest iGPUs by 2x over Intel. NVidia decided to use gimmicks to sell their cards including texture compression, lighting tricks, improved antique video encoders, motion smoothing, bad proprietary variable refresh rate, ray tracing, cuda and now machine learning features. Nvidia is fortunate that machine learning has taken off. That is masking AMD winning market share from weak overpriced NVidia 3D products!
- dotnet00 3y agoCalling features which are integral to all modern games and most of which also got adopted by other vendors 'gimmicks' is kind of ridiculous.
- m463 3y agoIsn't this sort of how specialized hardware kind of works? At some point, hardware (necessarily?) evolves to become optimized to do one thing, and then you have to just treat the driver as an API to the hardware. Even "simple" things like keyboards and mice are now small computers that run their own code, moreso more complex devices like sound cards and hard drives. And since graphics card performance seems to be the bottleneck in a lot of computing, it has become super specialized and you just hand off a high-level chunk of data and it does magic in parallel with fast memory and spits it out the hdmi cable.
- AnotherGoodName 3y agoFor the keyboard/mouse now being small computers that's been true since the 1970s. Almost all keyboards for a period of about 30 years had an 8048 or 8051 CPU. It's how they serialized the keystrokes. From the model M keyboard through to everything up till the USB era.
- kevin_thibedeau 3y agoIn the 70s it would be more common to have an MSI part that ran matrix scanning and spit out parallel bus ASCII. UCs were still spendy.
- JonChesterfield 3y agoWhat OS do you mean? The closest thing I can think of is the embedded CPU that gets called CP in the ISA docs, which mostly schedules work onto the compute units. That has firmware which is probably annoying to disassemble, but it's hard to imagine it doing anything particularly interesting.