Blumenkrantz Picks His Next Battle: Mesa's DRI Interfaces

[phoronix]

Phoronix: Blumenkrantz Picks His Next Battle: Mesa's DRI Interfaces

Valve contractor Mike Blumenkrantz has been known for many great Mesa improvements the past several years, especially around Zink for the OpenGL-on-Vulkan implementation within Mesa. Over the past four years he has taken on many great performance optimizations and other significant code undertakings to improve Mesa. Blumenkrantz has picked his latest battle and appears to be around Mesa's Direct Rendering Infrastructure (DRI) interfaces...

https://www.phoronix.com/news/Mesa-DRI-Battle-Blumenkrantz

[jonkoops]

Love Mike's work, he's been doing a lot of amazing cleanup!

[rabcor]

Love Mike's work, he's been doing a lot of amazing cleanup!

Yes, Zink is pretty amazing, it needs more work (still has peformance issues and graphical glitches) but it's really getting there. Once it's really ready, no driver will need opengl support anymore lol.

[Hazel]

We need more Blumenkrantz and less avis.

[timofonic]

What will be if DRI is going to be removed? Just asking, sorry for my ignorance. The article is extremely sparse and full of holes.

[Phoronos]

What will be if DRI is going to be removed? Just asking, sorry for my ignorance. The article is extremely sparse and full of holes.

No, the article is very good. Don't blame it for your lack of knowledge about DRI.

[murraytony]

What will be if DRI is going to be removed? Just asking, sorry for my ignorance. The article is extremely sparse and full of holes.

DRI3 and DRI2 (minus the mostly unused x11 interface that Emma Anholt is trying to remove). In other words, this is trying to remove DRI1, which is just called DRI.

[BsBox]

DRI3 and DRI2 (minus the mostly unused x11 interface that Emma Anholt is trying to remove). In other words, this is trying to remove DRI1, which is just called DRI.

The merge request seems to include DRI2 and DRI3 as well, unless I'm misunderstanding.

[Jumbotron]

Curious that Google feels compelled to use DRI with AMD based Chromebooks at least internally. Why ? Does this dovetail into what was discussed by the creator of Tinybox Neural Net devices to the crappy state of not only AMD drivers and firmware but ROCm as well ? What's going on at AMD and why are multiple vendors using AMD tech being hamstrung like this ?

[Jumbotron]

Slightly off topic but still I think in the wheel house of issues with AMD, it's been confirmed by them that VCN 4 is broken at the hardware level. This was discovered with the new release of OBS as certain encoded video on AMD hardware with VCN 4 adds padding to the top and bottom because it can't conform to standard pixel sizing. It was also confirmed that it will NOT be fixed until VCN 5 arrived....in brand new hardware. The only thing that AMD can do is when presented with say a standard HD sizing regime is to basically keep the black padding to a minimum when the encoder goes outside the normal sizing of say a 1080p sized video.