Originally posted by xeekei
View Post
Announcement
Collapse
No announcement yet.
The Slides Announcing The New "AMDGPU" Kernel Driver
Collapse
X
-
Originally posted by oleid View PostI think this was one reason for AMD to go the open source way. The foundation supports Wayland and Ubuntu will probably provide patches.
Comment
-
Originally posted by MartinN View PostSo 'dungeon', do you have an alternative to capitalism? I'd like to hear it.
Originally posted by agd5f View PostI don't see why this is any more of an advantage to the closed source driver than it is to the open source driver. Both driver stacks will now have more developers working on the shared components. More developers working on modesetting, memory management, power management, etc.
Comment
-
It seems that there will be better cooperation between the closed and open source Linux driver teams, how will it benefit open source? (excluding shared code parts)
Will it help in releasing document faster in the future?
Will it help with magic numbers and with understanding HW better/faster in the future?
Will you cooperate closer about other things as well and not only the shared code?
Will i with amdgpu be able to use open source for everything and use the blob for only one game in the same x session? (switch userspace in active session)
Comment
-
Originally posted by dungeon View PostWe all know at some point there will be not equality like that, one must prevail and i guess AMD will want that to be blob...Test signature
Comment
-
Originally posted by Nille_kungen View PostIt seems that there will be better cooperation between the closed and open source Linux driver teams, how will it benefit open source? (excluding shared code parts)
Originally posted by Nille_kungen View PostWill it help in releasing document faster in the future?
Originally posted by Nille_kungen View PostWill it help with magic numbers and with understanding HW better/faster in the future?
Originally posted by Nille_kungen View PostWill you cooperate closer about other things as well and not only the shared code?
Originally posted by Nille_kungen View PostWill i with amdgpu be able to use open source for everything and use the blob for only one game in the same x session? (switch userspace in active session)Test signature
Comment
-
Originally posted by bridgman View PostYep, we're moving components over to open source and putting more resources on open source components because we want the blob to be better...
Is that depends who asking?
Comment
-
Originally posted by dungeon View PostLet say at some point we all need some performance workaround in kernel MM sharable part which is needed for both, but works best on blob GL while being just good enough for mesa... and we also know it can be workarounded differently to play the best for mesa but not for blob... what will you choose there?
Is that depends who asking?
You seem to be asking about a case where there's a design tradeoff between open and closed source drivers, but since the user-kernel interface will be the same I don't see that coming up very often. If you're talking about defaults or tuning values for heuristics I imagine we would just make them configurable and configure differently depending on which stack was installed.
Even there the differences tend to be more a function of usage scenarios than driver stacks, eg some workstation users want a single app to be able to consume all the resources in the system for optimal performance and see that as a Must Have, while for most systems that is considered a Bad Thing since it can cause problems for other apps.Test signature
Comment
-
@bridgman Thanks for the answer.
I myself think this sounds like a good thing and i hope it turns out to be better for both drivers.
I think AMD gets better Linux support both open and closed source in small steps all the time and i see this as next step.
I remember when there was no working AMD driver at all and now we have real good open source drivers and a blob for the things Radeon can't handle yet.
Comment
-
Everyone seems to keep asking the same question, but ignoring my response. Let's try this again: Having a shared components benefits both drivers since there will be more developers working on those components. We will now have a number of formerly closed source developers working on new open source components in additional to the open source developers. It doesn't matter what userspace graphics stack is running when you light up the displays or set up the power management hardware. Having more developers to help write and maintain and debug that code helps everyone.
Comment
Comment