summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorvanfanel <redwindwanderer@gmail.com>2022-09-07 16:34:17 +0100
committerPekka Paalanen <pq@iki.fi>2022-09-23 11:05:34 +0000
commit3240ccc69d1488003c1cfc36d23750145d4f13f7 (patch)
tree58fca76285101db713c23d1c63b2d06b106ecce1 /man
parent995d080cb9608d0715c1773a9da011f7a5740da3 (diff)
downloadweston-3240ccc69d1488003c1cfc36d23750145d4f13f7.tar.gz
Don't change the max_bpc connector prop if mode=current.
As things are, even when mode=current is specified on the .ini file, a full modeset is needed (and done), which causes a very noticeable screen blinking. That is because setting the max_bpc on a connector needs full modesetting. The idea here is that if mode=current on the .ini, no modesetting should be done, so the current max_bpc is programmed into the connector. But if a custom max-bpc=... is specified, that will be used instead, even if mode=current on the .ini Fixes: https://gitlab.freedesktop.org/wayland/weston/-/issues/660 Signed-off-by: vanfanel <redwindwanderer@gmail.com>
Diffstat (limited to 'man')
-rw-r--r--man/weston-drm.man2
1 files changed, 1 insertions, 1 deletions
diff --git a/man/weston-drm.man b/man/weston-drm.man
index eaaf311c..383715d3 100644
--- a/man/weston-drm.man
+++ b/man/weston-drm.man
@@ -172,7 +172,7 @@ silenty clamped to the hardware driver supported range. This artificially
limits the driver chosen link bits-per-channel which may be useful for working
around sink hardware (e.g. monitor) limitations. The default is 16 which is
practically unlimited. If you need to work around hardware issues, try a lower
-value like 8.
+value like 8. A value of 0 means that the current max bpc will be reprogrammed.
.SS Section remote-output
.TP