Changed the default delay of optimizing display data buffer allocations from 0 to 1 second #93
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Abstract
This is a follow-up for the previous PR (#92) that fixes the garbled screen on Intel Ice Lake platforms.
The community reports that a delay of 1 to 3 seconds is adequate for avoiding the pipe underrun issue on the builtin display without having negative impacts on external displays, and that the default delay of 0 second used in v1.5.4 may lead to both internal and external displays flickering on some laptops.
This PR changes the default delay to 1 second and adds documentation for a hidden device property
dbuf-optimizer-delay
introduced in the previous PR that allows users to specify a custom delay value.Updates
This PR also disabled the following submodules on Ice Lake platforms.
Thank you.
-- FireWolf
Oct 8, 2021