Thanks for the (many) answers about the closed/open AMD drivers. The message I get then is that the proprietary drivers from AMD have an awful support from the company on Linux (at least compared with the very good support from NVidia).
Best regards, Guillermo On Fri, Jun 23, 2017 at 8:25 AM, Chris Siebenmann <[email protected]> wrote: >> On 22/06/2017 22:26, Germano Massullo wrote: >> > Forget using OpenCL without proprietary drivers, but there is a way >> > to use them without having to install it permanently: if you use a >> > Radeon RX card you can simply unpack the proprietary OpenCL driver >> > somewhere and let darktable use it. >> >> Honest question: what is the sense of doing this? If one is using the >> open source drive on "moral grounds", taking the OpenCL blob from >> it and using it when convenient doesn't make it any less closed. I >> confess that I don't know the status of the proprietary drivers for >> AMD, are they fundamentally worse than the open ones? > > If I were to do this (without being in the situation that I had to, eg > the current situation for Fedora), it would be so that I could apply my > distribution's kernel security updates without having to worry that my > card's (closed-source) driver wouldn't work with the new kernel and I'd > be left stranded in text mode (or not be able to apply the kernel update). > > (As I've experienced repeatedly with VMWare's kernel modules, kernel > modules supplied by companies are often not updated immediately to work > on new kernels. In the case of VMWare, there is a community that usually > works out patches reasonably soon, and running VMWare at all isn't > crucial to my work machine.) > > - cks ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
