7 ms·
Yep. And AMD just doesn't care - literally: "For the most part, because—in the case of Nvidia—they don't appear to care that much about VR. And in the case of
by nl 10y ago
Yep.
And AMD just doesn't care - literally:
"For the most part, because—in the case of Nvidia—they don't appear to care that much about VR. And in the case of the dollars spent on R&D, they seem to be very happy doing stuff in the car industry, and long may that continue—good luck to them. We're spending our dollars in the areas we're focused on."[1]
Everytime someone complains about how little OpenCL is used, I just think of that quote. I'm happy to use products from a company that cares about what I do.
(And yes, good OpenCL implementations would be great too. But the world won't wait for AMD on this).
[1] http://arstechnica.co.uk/gadgets/2016/04/amd-focusing-on-vr-mid-range-polaris/ http://arstechnica.co.uk/gadgets/2016/04/amd-focusing-on-vr-...
- shmerl 10y agoAMD cares to contribute to Mesa. Nvidia? Not really.
- lmm 10y agoNVidia have their own high-quality OpenGL implementation. Isn't that better?
- robert_foss 10y agoNo. It is strictly worse. NVidia not only has no interest in having a Mesa driver, but would prefer if they didn't have to compete with Mesa at all.
- cosarara97 10y agoBetter for whom? The nvidia driver doesn't have proper wayland support, can't work with gallium nine, can't be included in the kernel, and has issues with v-sync.
- shmerl 10y agoIndeed. While radeonsi continues to march forward, Nvidia doesn't rush to address the above. My next card is going to be Vega.
- emp_zealoth 10y agoYet AMD cards under linux are complete misery Driver support going away after a few years, random issues, etc Every single nVidia card I used under linux just worked TM (ofc I'm not "pure" because I really couldn't care less about open vs closed drivers)
- erichocean 10y ago> good OpenCL implementations would be great too Now that Vulkan is out, that's far less important than it used to be.
- shrewduser 10y agoi wasn't even aware vulkan obviated openCL...
- wlesieutre 10y agoI don't know a ton about the subject, but there's some coverage of it in this overview: https://www.khronos.org/assets/uploads/developers/library/overview/2015_vulkan_v1_Overview.pdf https://www.khronos.org/assets/uploads/developers/library/ov...
- shmerl 10y agoThey overlap to some degree. Vulkan allows access to compute queues of the GPU (in addition to graphics ones).
- pjmlp 10y agoOpenGL already does that via compute shaders and it hasn't helped.
- shmerl 10y agoHasn't helped what exactly? OpenGL can't provide proper parallelized access to all the queues, so having compute shaders there isn't that useful.
- pjmlp 10y agoTo gain adoption. NVidia doesn't care about OpenCL. Google doesn't care, and pushes Renderscript instead. Apple doesn't care, it created OpenCL, but since Khronos doesn't dance their music, they rather push Metal Compute Shaders. Microsoft has C++AMP and DX Compute. Additionally CUDA was designed to be targeted by multiple languages, while OpenCL had to wait for OpenCL 2.0 for it to happen. Also the graphical debuggers for OpenCL could get some love. I know which GPU makers I will keep giving my money to.
- rasz_pl 10y agoAMD management is dysfunctional (think late Commodore). They are perfectly ready to throw away $300m on a shot in the dark (seamicro) but are unwilling to hire actual developers to support their current hardware (gpu drivers still single threaded).
- whazor 10y agoThey invest into efficiency. So they will be second in VR. But provide more battery and therefore more game time.
- EugeneOZ 10y agoAnd you can use their VR device as a warm winter hat.
- peller 10y agoI won't argue with you over some of the things AMD has decided to prioritize, but for what it's worth, they are at least working on supporting CUDA compilation for their GPUs. http://www.anandtech.com/show/9792/amd-sc15-boltzmann-initiative-announced-c-and-cuda-compilers-for-amd-gpus http://www.anandtech.com/show/9792/amd-sc15-boltzmann-initia...
- bryanlarsen 10y agoAnd today AMD announced public availability of CUDA: http://www.anandtech.com/show/10831/amd-sc16-rocm-13-released-boltzmann-realized http://www.anandtech.com/show/10831/amd-sc16-rocm-13-release...
- Notre1 10y agoIt seems like their focus is more on the mainstream (~$200) cards than the high-end. They did get their chips in both the major consoles, so maybe that focus on squeezing costs out if the mid-range is working out.
- dogma1138 10y agoIf AMD cared about VR it would have implemented viewport multi casting which NVIDIA has supported since Kepler. VR performance on AMD card is abysmal, GTX 1060 beats a fury x once you count time warped and reprojected frames.
- bryanlarsen 10y agoIt's silly for AMD to say that nVidia doesn't care about VR. By the same token AMD obviously cares about HPC, even when they say they're "all in" on VR in some press release. They're both big companies that put lots of effort & money into many things simultaneously. Not to mention that today is the day that AMD announced public availability of CUDA for their platform. http://www.anandtech.com/show/10831/amd-sc16-rocm-13-released-boltzmann-realized http://www.anandtech.com/show/10831/amd-sc16-rocm-13-release...
- gcr 10y agoHPC? NVidia is completely destroying AMD on the deep learning front. The most popular deep learning frameworks use CUDA and do not have stable OpenCL support out of the box.
- bryanlarsen 10y agoAnd today AMD announced support for CUDA and hinted that they were deprecating OpenCL (by releasing OpenCL 1.2+ rather than concentrating on 2.0).
- gcp 10y agoWhat? AMD's drivers have had OpenCL 2.0 support for a long time. At least on Windows.
- gcp 10y agoThe most popular deep learning frameworks use CUDA and do not have stable OpenCL support out of the box. It's worse than that. The popular frameworks use cuDNN, which is a hand (assembler) optimized library for common operations. AMD does not have any equivalent. Even if you have OpenCL support you'll get nowhere the performance.
- gcr 10y agoMost libraries have fallbacks for cuDNN-less operation. Torch, for example, requires you to import a CUDNN library if you want to use it. Caffe requires you to uncomment a line in a makefile if you want to use it.