Originally posted by Alejandro Nova
View Post
Announcement
Collapse
No announcement yet.
AMD Is Exploring A Very Interesting, More-Open Linux Driver Strategy
Collapse
X
-
-
Originally posted by xeekei View PostYeah, tearing vs stuttering, the "choose your poison" of the modern graphics experience. I hope Gsync takes off, and won't be Nvidia exclusive, to fix that one.
Originally posted by Vim_User View PostSou you mean once the switch to the radeon kernel module is made the "free" developer time does not have to be put into working on the radeon module for release-day support of new hardware and implementing missing features that fglrx supports, but radeon not? Still the same question, where would they magically get that time from if they don't even have the time for proper changelogs?
Comment
-
Originally posted by Vim_User View PostSou you mean once the switch to the radeon kernel module is made the "free" developer time does not have to be put into working on the radeon module for release-day support of new hardware and implementing missing features that fglrx supports, but radeon not? Still the same question, where would they magically get that time from if they don't even have the time for proper changelogs?Test signature
Comment
-
Originally posted by Vim_User View PostSou you mean once the switch to the radeon kernel module is made the "free" developer time does not have to be put into working on the radeon module for release-day support of new hardware and implementing missing features that fglrx supports, but radeon not? Still the same question, where would they magically get that time from if they don't even have the time for proper changelogs?
The only real answer seems to be... let's wait and see...
Comment
-
Originally posted by bridgman View PostMaybe I don't understand your question, but isn't having all our kernel driver developers (from open and closed source teams) working on one kernel driver rather than two totally different ones likely to improve things ?
Comment
-
Originally posted by bridgman View PostMaybe I don't understand your question, but isn't having all our kernel driver developers (from open and closed source teams) working on one kernel driver rather than two totally different ones likely to improve things ?
To me I see this move as essentially giving up on the full open source driver. I don't necessarily think it's a bad move -- I prefer the binary blobs myself -- but it seems that many here who are beaming smiles aren't quite picking up on this subtle reality.
Comment
-
Originally posted by johnc View PostDoesn't that mean that the 100% open source driver (the current Radeon) will die from lost resources?
To me I see this move as essentially giving up on the full open source driver. I don't necessarily think it's a bad move -- I prefer the binary blobs myself -- but it seems that many here who are beaming smiles aren't quite picking up on this subtle reality.Test signature
Comment
-
Originally posted by bridgman View PostI don't understand the logic you're using -- you're basically saying "if I have M developers working on one kernel driver, and N developers working on another kernel driver, P developers working on the open source userspace stack and Q developers working on the closed source userspace stack, if both M and N work on the same kernel driver then P will go away ?
Comment
-
Originally posted by johnc View PostIt wasn't really clear (or obvious): is it AMD's intention to make P go away (internally) and just provide a single driver option?
Comment
-
Exactly... well, I guess it depends on what you mean by "working". P and Q are development teams working on the userspace bits and they would *keep* working on their respective userspace bits, but those userspace bits would work on a common kernel driver. M and N are the kernel driver development teams.
The plan doesn't work without a good open source userspace stack.Last edited by bridgman; 23 March 2014, 08:54 PM.Test signature
Comment
Comment