Originally posted by bridgman
View Post
Announcement
Collapse
No announcement yet.
AMD's Vulkan Driver Will Only Work With The AMDGPU Kernel Driver
Collapse
X
-
The bottom line will eventually be out of box vulkan support. You need in tree drivers for that. Which effectively means your only option is for amdpu to support all GCN cards. Work with the kernel developers. Don't let retarded political policies harm AMD. Bridman you are the man that can protect AMD from that harm, but you posts in this thread are chalk full of excuses. Come on. man!
You guys must have known, or intuited that this would happen at least a year ago. What have you done to avoid or prevent it until now? Allowing political injustice is exactly the same thing as sabotage or incompetence. I personally don't have a problem with rebranding. But in this case if what you are saying ends up being what happens, and the fact that you've known about this for so long already means that those people that bought those cards were wronged by you.Last edited by duby229; 23 January 2016, 11:44 AM.
Comment
-
Did you actually read anything I wrote ?
First, there are a few different ways to achieve the goal you described, with the most obvious ones being (a) Vulkan over libdrm-radeon using radeon kernel driver, (b) Vulkan over libdrm-amdgpu using radeon kernel driver, (c) Vulkan over libdrm-amdgpu using amdgpu kernel driver... not just option (c) as you suggest.
We will probably end up going with (c) but (b) lets us get there more quickly because we don't need to wait for new userspace to dribble out through distros onto user systems, so we have been exploring both options.
Second, you think you are reacting to what we have actually been doing for the last year, but in fact you are just reacting to an article Michael wrote. Big difference.
Originally posted by duby229 View PostBut in this case if what you are saying ends up being what happens, and the fact that you've known about this for so long already means that those people that bought those cards were wronged by you.Last edited by bridgman; 23 January 2016, 01:00 PM.Test signature
- Likes 1
Comment
-
Or you can simply add support for SI in the amdgpu kernel driver and make it so that it can be disabled by a kernel config option, then disable radeon *by default* and put out a notice for distributions that they need to enable radeon and disable SI support in amdgpu as long as they do not ship libdrm+mesa with the new support.
Or you can provide an installer for the user space drivers like intel does: https://01.org/linuxgraphics/downloa...er-linux-1.2.1
Comment
-
Originally posted by bridgman View PostDid you actually read anything I wrote ?
First, there are a few different ways to achieve the goal you described, with the most obvious ones being (a) Vulkan over libdrm-radeon using radeon kernel driver, (b) Vulkan over libdrm-amdgpu using radeon kernel driver, (c) Vulkan over libdrm-amdgpu using amdgpu kernel driver... not just option (c) as you suggest.
We will probably end up going with (c) but (b) lets us get there more quickly because we don't need to wait for new userspace to dribble out through distros onto user systems, so we have been exploring both options.
Second, you think you are reacting to what we have actually been doing for the last year, but in fact you are just reacting to an article Michael wrote. Big difference.
m saying ?
Yes, I'm responding to an article, but you must have known or intuited that this would be a problem a long time ago. You have and have had knowledge that I don't have. Of course I responded to an article. Your policy of trying to keep everything to yourself till the last second right before it backfires on you is part of that problem.
Comment
-
We live a universe that abides fractal dynamics. What happens tends to happen. Outside developers don't tend to contribute to AMD's graphics drivers. AMD is itself responsible for bringing up the OSS drivers for their hardware. They've done a fantastic job at it and have developed top notch drivers for Linux. Expecting that suddenly things will change and AMD doesn't have to support their hardware because Option b: is available is pretty dumb considering that it almost certainly -won't- happen. If AMD is saying that they are relying on Option b:, then we all might as well forget about Vulkan on SI.
EDIT: Like I already said the bottom line is out of box Vulkan support. Options a: and b: aren't going to happen. That leaves only c: and only AMD is in a position to make that happen.Last edited by duby229; 23 January 2016, 02:00 PM.
Comment
-
Originally posted by duby229 View PostYou have lready said a: isn't going to happen, and b: requires contributions outside of AMD. So what does that leave? Pretty obvious huh? And for those of you that knew it already, it must have been obvious for a long time now.
Where do you think you read that ?
Originally posted by duby229 View PostExpecting that suddenly things will change and AMD doesn't have to support their hardware because Option b: is available is pretty dumb considering that it almost certainly -won't- happen. If AMD is saying that they are relying on Option b:, then we all might as well forget about Vulkan on SI.Last edited by bridgman; 23 January 2016, 01:55 PM.Test signature
- Likes 1
Comment
-
Originally posted by haagch View PostOr you can simply add support for SI in the amdgpu kernel driver and make it so that it can be disabled by a kernel config option, then disable radeon *by default* and put out a notice for distributions that they need to enable radeon and disable SI support in amdgpu as long as they do not ship libdrm+mesa with the new support.
Or you can provide an installer for the user space drivers like intel does: https://01.org/linuxgraphics/downloa...er-linux-1.2.1
It's not just a matter of talking to distros, although individual distros still might be good test cases before flipping the switch upstream.
Test signature
- Likes 1
Comment
Comment