That is a big deal. RadeonSI has always had official support but for some reason AMD has been ignoring RADV in favor of their own stuff. Glad to see they're shifting to mesa for literally everything other than compute.

[–] vikingtons@lemmy.world 2 points 2 weeks ago (2 children)

As far as I'm aware, the RadeonSI driver was built internally, whilst RADV was an external effort.

The focus was on AMDVLK as it's similar in design to the XGL windows vulkan driver

[–] woelkchen@lemmy.world 2 points 4 days ago

RADV was an external effort.

Not only external but a fork of Intel's Vulkan driver. That's why Intel's copyright is mentioned in many file headers.

[–] Scoopta@programming.dev 1 points 2 weeks ago (1 children)

The windows vulkan driver is called XGL? That's not confusing lol

[–] vikingtons@lemmy.world 2 points 2 weeks ago (1 children)

Yup, derived from a point in time where Vulkan was seen as a direct successor to OpenGL.

I suppose credit where due, AMD did kind of put an end to mantle, and give that over to the Khronos group to later become Vulkan. XGL as the UMD reference may predate the name Vulkan altogether.

[–] Scoopta@programming.dev 1 points 2 weeks ago (1 children)

Yeah, at one point vulkan was called glNext so I guess it isn't that wild. Although I'm surprised they would have started development on a driver before any spec was fully agreed on. Unless they just reworked their mantle driver to become their vulkan driver?

[–] vikingtons@lemmy.world 1 points 2 weeks ago

I wouldn't be surprised if something like that was the case. Could have been that the successive work was negotiated with khronos & lunarg before the final name was chosen.

load more comments (6 replies)