Originally posted by sireangelus
View Post
Announcement
Collapse
No announcement yet.
AMD Begins Staging AMDGPU Patches For Linux 4.20/5.0, Including FreeSync Refactoring
Collapse
X
-
Originally posted by sireangelus View Posthonestly, for 5.0, i would stop submitting ANY new code not bugfix/regression related and prompt the developers to pause all current work and use their time only towards that end, before going foward.
- Likes 3
Comment
-
Originally posted by euler271 View Post
"I don't want to be too predictable. The version numbers are meaningless" Linus Torvalds
Then again, that mean there's no real difference between 4.13 and 5.0. So no extra care on bugfix/regression should/has to/will be taken, and that's just ok.
But, for kernel, I would just name it with YEAR.MONTH of release date.
- Likes 1
Comment
-
Originally posted by sireangelus View Postno merge window either. Only bugfixing and regression is allowed.Last edited by pal666; 26 August 2018, 12:53 PM.
Comment
-
Originally posted by ThoreauHD View PostWhy do I get the feeling that they are simply fking with us to keep their proprietary driver in play.
We can't "reach agreement on a cross-vendor solution" by ourselves...Last edited by bridgman; 02 September 2018, 11:54 PM.Test signature
- Likes 1
Comment
-
Originally posted by debianxfce View Postand put AMD freesync patches to the mainline open source software.
The expectation is that freesync will go upstream as a cross-vendor solution.Test signature
- Likes 1
Comment
-
Not sure who originally pushed back on upstreaming as AMD-only code but the focus for the last year has been on finding a cross-vendor solution. I believe the main participants have been Manasi from Intel plus some AMD folks.
My understanding is that kernel code for freesync has been upstream for a while since that is vendor-specific by nature, and that the discussion has been around userspace code - X driver, libdrm and Mesa.Last edited by bridgman; 05 September 2018, 05:16 AM.Test signature
Comment
Comment