4 ms·
Well, it's not all peaches and roses. See, the confusing miasma surrounding USB and its various overloaded capabilities. Or PCIe -- if you want to use ROCm on
by spijdar 6y ago
Well, it's not all peaches and roses.
See, the confusing miasma surrounding USB and its various overloaded capabilities.
Or PCIe -- if you want to use ROCm on AMD GPUs, your PCIe complex needs to support "PCIe atomics", which, uh, none of my computers do. AMD's boards do, though!
That's nitpicking though. I don't think PC's open architecture is really comparable, the truly open bits like PCI are much less "open to interpretation" as RISC-V, while bits like the CPU socket, chipsets, and even the keyboard port were either proprietary or clones of proprietary tech.
- floatboth 6y ago> if you want to use ROCm on AMD GPUs, your PCIe complex needs to support "PCIe atomics" Not anymore, at least for Vega cards: https://github.com/RadeonOpenCompute/ROCm/issues/800#issuecomment-525925928 https://github.com/RadeonOpenCompute/ROCm/issues/800#issueco... > AMD's boards do, though! No board support is required, this is on the SoC ("CPU") side, unless you're trying to connect the GPU via a chipset-side low-bandwidth slot. Intel supports it since Haswell on desktop (and earlier in Xeons apparently), Marvell ThunderX2 and Mellanox BlueField support it, I'm pretty sure Ampere does too.
- spijdar 6y agoYeah, it's the only reason I've thought about upgrading my polaris card up newer. In my case, I tried connecting both via thunderbolt on some skylake/coffeelake laptops and on power9. Neither Intel's TB3 controller nor power9 support the necessary extension. Not really a big deal, but a nitpicky example of how "fragmentation" sometimes hurts.