You have to open it separately before any possibility to upstream.
This seems just following normal praxis.
If any, the problem it’s just it took them so long, but that’s it.
It will be interesting to see what airlied & co will think of the new driver now.
Maybe it can be fused with radv, maybe just some cherry-picking will happen, maybe they’ll go full DC refitting and rebase over that.
Thats what i think will happen. Adrenalin has no chance to be in Mesa, because its not a mesa project. And there is no chance for a fusion(-ha!) because adrenalin is also part of the Windows Radeon drivers and so it cant pull in Mesa dependencies.
Maybe at some point (Vulkan2.0?) When a bigger rewrite is about to happen, the AMD guys have the manpower and the Radv guys will just say “meh - lets switch to adrenalin”. But for now I dont think there will be a change in the situation.
No… Thats the great thing about LLVM, they could just get there patches in place with an official release before an official release of the supported hardware, or software that uses this. Google has a whole architecture for a google processor in LLVM upstreamed.
That AMD-LLVM code could already be reviewed and integrated + updated so that they could just go for “here, all the code is opensourced and you can actually build and use it”. Yet again we have to wait for something and thats something AMD needs to change.
That’s exactly what happened with DC too, just for the records.
Then, I’m still pretty skeptical they’ll do something like that, because it’s similarly a huge undertaking, and I haven’t really the most of… confidence, in their GL team.
Still benefits of a very neat integration are there, and so is technical possibility to do so.
P.S. reviewing that still takes time/manpower and doesn’t contradict my point.
You can assume they put all their available effort (which is not unreasonable) and wonder if whatever the upstreaming, it could have been worth some other months or delay, just for “presentation”.
I don’t think so.
EDIT: dittoed in the words of none else of Saint Bridgman
Manjaro is the first distribution that had HDMI audio pretty much working out the box after grabbing the 4.15 kernel, good job.
I do however have an issue and if power saving puts the monitor to sleep there is no way to wake the screen up. It happened after I installed a couple days ago and the only choice I had was a hard system reset (via holding the power button).
My system is the Dell Inspiron 5675 and I usually build my own systems but warranty was the driving force.
Sound over HDMI was the big one for me. It is easy enough for me to turn off the monitor if I need to and I don’t want to risk anyhting with my sound.
I messed with OpenSuse Tumbleweed before doing a Manjaro install. Sound was a no go but the monitor going into standby did work. I just thought I would bring awareness to the issue although it is not a big deal for me.
While this is a known issue, are you sure thats only the display that stays asleep, and not the whole system that freezes? did you have tried to ssh to the system? Because it could be something else, something thats fixable for you.