AMD Confirms Vulkan Driver For Linux, But To Start Off As Closed-Source 47
An anonymous reader writes: AMD has finally revealed some basic details concerning their support of Vulkan on Linux. AMD has a Vulkan driver but it will begin its life as closed-source, reports Phoronix. In time the AMD Vulkan driver will transition to being open-source. This Vulkan driver is built to interface with their new AMDGPU kernel DRM driver that's part of their long talked about AMD open-source strategy for Linux. This closed-then-open Vulkan driver will be competing with Valve's Intel Vulkan driver that will be open from day one.
Re:Why? (Score:4, Informative)
Re: (Score:1)
But they definitely love having people develop free drivers for them so they dont have to pay for it while releasing as little as possible information to do it.
Re: (Score:2, Insightful)
Most of it turned into Vulkan in the first place so...yes?
I would guess their assorted contracts with console makers is the reason for closed source issues more than some AMD desire to keep code secret for ??? and profit. Mantle supports XBox and PS4, I doubt it does that without a whole lot of proprietary(and therefore licensed) information about their platforms.
is it better to give us a functional binary blob that still has licensed code or make us wait for it to be completely removed and tested?
Re: (Score:2)
No doubt, AMD loves to tout open this and that but keeps their stuff closed as long as possible. example, AMD said mantle was gonna be open source for since day one, did THEY ever release the source for it before killing development for it?
AMD has failed to execute in a number of areas, I don't think this is any more of a "planned failure" than the rest. In particular you have to produce what you want to release first, then get it through legal so it's not surprising that an abandoned project hasn't open sourced any code. Their problem is that Intel is becoming usable for casual gaming - it has 20% market share on Steam now, they're open source too and unlike AMD they've got a war chest to fight on every front at once. Sure, Intel doesn't hav
Re: (Score:2)
?No doubt, AMD loves to tout open this and that but keeps their stuff closed as long as possible. example, AMD said mantle was gonna be open source for since day one, did THEY ever release the source for it before killing development for it?
AMD has failed to execute in a number of areas, I don't think this is any more of a "planned failure" than the rest.
It's not about that. It's more that if you were planning for AMD to actually release the stuff they said they would release, you're making unrealistic plans.
Re: (Score:2)
It's not about that. It's more that if you were planning for AMD to actually release the stuff they said they would release, you're making unrealistic plans.
That has been obvious for quite some time, yes. And though you can use marketing BS to bridge a few gaps in your product line-up and string users along to wait a while, every once in a while you must deliver and cash in the sales. If not the users will understand that they're just chasing the pot of gold at the end of the rainbow and buy a product that's on the shelf and delivers today. You saw it most clearly on the FX line that AMD never officially killed, fans were waiting and hoping in vain only to slow
Re: (Score:1)
AMD said mantle was gonna be open source for since day one, did THEY ever release the source for it before killing development for it?
No they didn't, in fact "Open Source" is not even applicable to Mantle. They said it would be an open specification, however instead of creating yet another standard they decided to offer it as the basis for glNext (now Vulkan) for which the specification will be open, just like OpenGL.
Re: (Score:3)
Probably more accurately, they are building the driver to work first, then they need to do a legal assessment to see what code (if any) has restrictions on it.
Hard to do that before it has taken shape and starts working.
Re: (Score:3, Insightful)
> To keep the competition in the dark?
I would doubt it would give the competition any real advantage - given that the it's written specfically for AMD hardware and the competition already have working drivers that are doing the same thing as AMD's drivers.
More, likely it's to hide stuff that might be infringing on patients, contain plagarised code, or gaming benchmarks.
Score 5: Stupid (Score:5, Funny)
Re: (Score:3, Funny)
Re: (Score:2)
Well, you have to stick to a certain standard transliteration, otherwise it only will end up like this [wikimedia.org].
This will likely never be fully OSS (Score:4, Interesting)
Re: (Score:1, Troll)
AMD is like capitalism, its terrible, but not as terrible as the alternatives.
DRM (disambiguation) (Score:3)
Is it closed source because the Direct Rendering Manager driver has to enforce Digital Restrictions Management in order for things like Netflix to work?
Re: (Score:2)
Is it closed source because the Direct Rendering Manager driver has to enforce Digital Restrictions Management in order for things like Netflix to work?
In Soviet Russia, Netflix watches YOU!
AMD is killing themselves (Score:1)
There is no reason to keep this closed source. Their developers are obviously morons (proven by the last 20+ years of idiocy). Maybe try actually embracing a new form of software? Seeing as how it shouldn't matter to a hardware company. I mean there are developers chomping at the bit to create badass software for you products. Yet you shun them? WTF?!
Fucking hell, how many times do you want to shoot yourself in the foot? I hate to see AMD die because there is no other competition to Intel but God Damn they
Re: (Score:1)
NO U (Score:1)