Originally posted by johnc
View Post
Announcement
Collapse
No announcement yet.
AMD Is Exploring A Very Interesting, More-Open Linux Driver Strategy
Collapse
X
-
-
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 ?
Leave a 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.
Leave a 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.
Leave a 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 ?
Leave a 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...
Leave a 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?
Leave a comment:
-
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?
Leave a comment:
-
Originally posted by Alejandro Nova View Post- Major changes in the driver to be able to use the radeon kernel module, which will take a significant amount of developer time? Resources are scarce, so, we'll maintain only one set of kernel interfaces instead of two, reduce our maintenance burden, and free up developers to even think about Mantle.
Leave a comment:
-
Yeah, 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.
Leave a comment:
Leave a comment: