Originally posted by varikonniemi
View Post
Announcement
Collapse
No announcement yet.
AMD Developers Begin Making Open-Source FreeSync/AdaptiveSync Plans
Collapse
X
-
Originally posted by varikonniemi View PostAt this pace it seems i will be getting a vega2 instead of vega. I won't go with them as long as there is no proper driver support. And open source driver support is main reason to go with AMD over Nvidia.
- Likes 6
Comment
-
Originally posted by varikonniemi View PostAt this pace it seems i will be getting a vega2 instead of vega. I won't go with them as long as there is no proper driver support. And open source driver support is main reason to go with AMD over Nvidia.
I get a feeling that somebody is complaining for the sake of complaining, not because there's something to actually complain about.Last edited by L_A_G; 17 October 2017, 09:38 AM.
- Likes 4
Comment
-
Originally posted by Azpegath View PostWhen the support lands in the open driver, I'll get a 4K, wide screen, FreeSync screen.
Freesync works best if the upper refresh rate limit is at least 2.5 times higher than the lower limit. This pretty much excludes 60hz monitors (and thus current 4k displays, because they tend to be only up to 60hz so far).
Why 2.5 times higher you ask? Because that's the minimum requirement for Low Framerate Compensation ( https://www.amd.com/Documents/freesync-lfc.pdf ).
This means you will want a 1440p display with at least 90hz.
I'm sure 4k displays with similar refresh rates will come eventually.
- Likes 2
Comment
-
Originally posted by kravemir View PostMight be true. But, AMD have had prepared opensource driver at the release of Vega. They did mistake by trying to do HAL, which is unacceptable for kernel drivers. It seems, they are working hard to fix it, and deliver proper opensource drivers. And, I really like that.
Additional work was required to define and implement with a solution that could bypass the HAL sufficiently to be acceptable for Linux, but that work had to be done while still being able to maintain a HAL for all of the other OSes/platforms. If you want to look for something to call a "mistake", it would not being sufficiently clear in early emails that we understood additional work would be required before we could go upstream.Last edited by bridgman; 17 October 2017, 10:28 AM.Test signature
- Likes 9
Comment
-
Originally posted by Brisse View Post
Just a little something to be aware of:
Freesync works best if the upper refresh rate limit is at least 2.5 times higher than the lower limit. This pretty much excludes 60hz monitors (and thus current 4k displays, because they tend to be only up to 60hz so far).
Why 2.5 times higher you ask? Because that's the minimum requirement for Low Framerate Compensation ( https://www.amd.com/Documents/freesync-lfc.pdf ).
This means you will want a 1440p display with at least 90hz.
I'm sure 4k displays with similar refresh rates will come eventually.
Unfortunately, they do not support freesync, yet.
Comment
-
Originally posted by bridgman View Post
Just to be clear, the HAL was not a "mistake", it was a core part of what DAL/DC is supposed to deliver (a cross-OS / cross-platform package of very HW-specific code).
Additional work was required to define and implement with a solution that could bypass the HAL sufficiently to be acceptable for Linux, but that work had to be done while still being able to maintain a HAL for all of the other OSes/platforms. If you want to look for something to call a "mistake", it would not being sufficiently clear in early emails that we understood additional work would be required before we could go upstream.
Vega drivers depend on AMDGPU DC (DAL), therefore this mistake affected Vega too.
Comment
Comment