News for hackers. Stuff that matters.
Re:Regarding EGLStreams Support in KWin by josteink on Thursday February 21, 2019 @05:02AM (#19215788)
> They were the first to provide actually usable GPU drivers on Linux.

Indeed. They raised the bar for Linux graphics. Maybe 10-20 years ago?

And then later ATI/AMD came along. And now their driver, the only driver, is open-source.

That is, they publish not only a driver, but more importantly the driver source. As is now true for pretty much all drivers for all HW Linux supports.

The bar has clearly been raised again. And now Nvidia is the only one lagging.

I don’t see anything unreasonable about asking them to contribute at the same level as everyone else.

Imagine how Linux would look today if all vendors got a free pass with doing things “their way” like Nvidia does. I doubt it would be functional at all.

I’m not going to cut Nvidia any slack today over what they did back in the days where everyone agreed M$ was evil and Google could do no wrong. It was a loooong time ago.

Re:Regarding EGLStreams Support in KWin by clhodapp on Thursday February 21, 2019 @05:14AM (#19215824)
Unless you have a really old OS version, you actually don't get your driver from AMD, you get it as a part of your Linux kernel: most Linux drivers aren't managed as standalone open source software projects, they are simply merged into the kernel itself.
Re:Regarding EGLStreams Support in KWin by pritambaral on Thursday February 21, 2019 @07:07AM (#19216229)
> you actually don't get your driver from AMD, you get it as a part of your Linux kernel

Thankfully.

However, the open source driver that is now part of the Linux kernel did indeed come from AMD, and could not have come from anywhere else.

Your parent said AMD publishes the sources to its (only) driver. That they happen to publish it with the Linux kernel wrapped around it, through kernel.org, is also true, but not incompatible with the claim that they publish it.

Re:Regarding EGLStreams Support in KWin by lmm on Thursday February 21, 2019 @07:54AM (#19216483)
> And then later ATI/AMD came along. And now their driver, the only driver, is open-source.

Open-source is great but is their driver remotely competitive in terms of actual usability/quality? As a desktop user I find ATI/AMD is still nowhere near the bar set by NVidia. I believe open-source generally results in better-quality software, but that hasn't actually come to fruition in the ATI/AMD drivers IME.

Re:Regarding EGLStreams Support in KWin by craftyguy on Thursday February 21, 2019 @10:30AM (#19217492)
> is their driver remotely competitive in terms of actual usability/quality?

A resounding 'yes'. You must not be using their open source driver, or are using a very old one in your 'comparison' with nvidia's linux driver?

Re:Regarding EGLStreams Support in KWin by lmm on Thursday February 21, 2019 @10:43AM (#19217586)
I tried it twice a few years ago. The first time I tried it it just had no support at all for the card (apparently too new); the second time it "worked" but felt pretty flaky, things like locking up much of the time if you tried to switch between X and console. Maybe it's better now - my experiences were bad enough that I swore off AMD for a while. (This was well after the point when their open-source drivers were established and people on HN were telling me they were good, though)
Re:Regarding EGLStreams Support in KWin by vetinari on Thursday February 21, 2019 @11:00AM (#19217700)
I have Vega 64 in my desktop, since the non-blower designs became available, and I had no problem with the amdgpu+mesa driver.

It is nice to have it work out of the box.

Re:Regarding EGLStreams Support in KWin by Fnoord on Friday February 22, 2019 @12:25PM (#19227112)
It is common knowledge that the AMD FOSS drivers nowadays work quite well. Spending a couple of minutes on Phoronix can verify that (they regularly report on such news). You even got multiple drivers to pick from (2 FOSS, 1 proprietary).
Re:Regarding EGLStreams Support in KWin by gmueckl on Thursday February 21, 2019 @11:50AM (#19218166)
How much do you stress the GL implementation? See, I write rendering code fairly regularly and I need drivers that don't keel over in use cases that aren't covered by desktop compositing and the occasional properly ported AAA game title. What I have seen from AMD so far did not encourage me to even try and buy one of their cards.
Re:Regarding EGLStreams Support in KWin by craftyguy on Thursday February 21, 2019 @11:32PM (#19223148)
> How much do you stress the GL implementation?

Quite a bit, I guess? I play a number of games, but no idea if they are "properly ported".

Re:Regarding EGLStreams Support in KWin by gmueckl on Sunday February 24, 2019 @05:18PM (#19240993)
Properly ported simply means a renderer using OpenGL or Vulkan directly with the exact same feature set as the Windows version. Cutting corners in the port of the renderer counts against that.

I do research into rendering algorithms and that sometimes involves straying from the trodden paths. This means that I always get sceptical when I need to use a feature that is a bit more obscure. With nVidia, I rarely encountered bugs in the driver.

I know for a fact that the Mesa software renderer sometimes lies about what it really supports amd does something different and completely inappropriate under the hood instead. A good example is that Mesa claimed to support floating point textures even if the support was not compiled to avoid patent licensing issues. Instead it would use 8 bit per channel internally, which totally broke some algorithms. I had to find out the hard way because the values I read back were suddenly horribly quantized.

What I want to say with these anecdotes is that "being able to render games so that they are playable" just shows that the driver quality is passable. A great driver needs to get a ton of additional things right that are not commonly used for games.

Re:Regarding EGLStreams Support in KWin by pjmlp on Thursday February 21, 2019 @01:36PM (#19219301)
Except that anyone using older AMD cards on laptops is pretty much alone, using a driver that only offers partial support for hardware features, unless we go back using legacy distros as means to use fxglr.

So much for open source driver.