-
Notifications
You must be signed in to change notification settings - Fork 103
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
platforms/atomic-kms: Make DisplaySink associated with exactly one KM…
…SOutput. This is a different behaviour to `gbm-kms`. On `gbm-kms`, when outputs have an overlapping view of the logical space they are grouped together so that they share a single *physical* framebuffer. When the overlap is great (such as a complete clone), this should result in lower GPU memory usage (as we need only a single set of framebuffers for all clones) at the cost of tying the refresh rates of each clone together. (And some bugs, like #3641). When the overlap is *not* great, this potential memory saving goes away (and may indeed result in *higher* GPU memory usage - if outputs have different sizes, we may now need to have a bunch of unused pixels, as the FB can only be rectangular). For Atomic KMS, instead, we give each output its own physical framebuffer, regardless of whether it overlaps.
- Loading branch information
Showing
3 changed files
with
75 additions
and
133 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters