Originally posted by indepe
View Post
Announcement
Collapse
No announcement yet.
RADV Starts Off Another Exciting Week Of Development
Collapse
X
-
-
Originally posted by bridgman View PostWith that gone, all that's left is the HW-specific code which is arguably the hardest part to maintain since every new generation needs new (or at least different) code. There is some ability to share code with Mesa GL (mostly the compiler) but I don't think writing the driver is as easy as you suggest.
Hopefully at some point AMD will open source its driver so that both can learn from each other, if not join in some way.
Leave a comment:
-
Not sure I agree. This is a similar situation to Gallium3D - yes the driver is smaller and simpler but the part that's gone is the common code. That is hard to write the first time and does need some ongoing optimization, but to a large extent it is reuseable across multiple GPUs and vendors.
The shareable, re-useable common code goes into the game engine or app, but most of the HW-specific code does not. The only exception there is that high level synchronization mechanisms get replaced with lower level ones, typically again requiring HW specific work.
With that gone, all that's left is the HW-specific code which is arguably the hardest part to maintain since every new generation needs new (or at least different) code. There is some ability to share code with Mesa GL (mostly the compiler) but I don't think writing the driver is as easy as you suggest.Last edited by bridgman; 01 February 2017, 12:56 PM.
Leave a comment:
-
Ah great, thanks for answering!
I must not have paid enough attention in that case.
Good to know it's still worked on anyway
Leave a comment:
-
I do answer, but if I don't have information I can release there isn't much I can say. That's not the same as not answering.
What I can say is same as before, (a) work is proceeding on it and (b) we are discussing options for dealing with radv vs our implementation.Last edited by bridgman; 31 January 2017, 10:48 AM.
- Likes 3
Leave a comment:
-
bridgman why do you never answer anything related to open sourcing the Vulkan driver or adopting RADV?
I may very well be worrying for nothing, but I get the feeling AMD dropped any plan to do open source work on Vulkan (can't see the reason though, so I'm confused right now)
Leave a comment:
-
Originally posted by shmerl View Post
And if not details, may be some rough ETA for completing this tedious process?
Leave a comment:
-
Originally posted by Qaridariumbest example for this they write to you about a AMDGPU-pro bug and you write back they should write a AMDGPU/Radeon bug-report because the time-pipe process of bug-fixing in the closed driver is "2-4 month" at minimum. and people are really confused by this ... the open driver do have bug-fix pipe timeline of maybe 1-2 days. I had such bug's and bugrepots and bugfixes in the past.
Please don't use quotation marks ("2-4 month") to suggest I said something that I did not. As always, feel free to quote what I actually say though, as long as it is not taken out of context.
For example, quoting me saying "yes" but implying it was my response to a different question would not be acceptableLast edited by bridgman; 30 January 2017, 03:58 PM.
Leave a comment:
Leave a comment: