author | Rob Clark <rob@ti.com> | |
Sun, 14 Oct 2012 21:55:32 +0000 (16:55 -0500) | ||
committer | Rob Clark <rob@ti.com> | |
Sun, 14 Oct 2012 21:56:53 +0000 (16:56 -0500) | ||
commit | e81acf51013d5d4245417c46ee6b4055c26f1a91 | |
tree | f87fe5b7dbe27d857aaeac2a6eeebab49dbab8e3 | tree | snapshot (tar.xz tar.gz zip) |
parent | 844d75e5a0b3b8f3466a24256955e886275fb298 | commit | diff |
initialize width/height fields in drmModeCrtc
If we have valid timings, we can at least set width/height to
*something*, which is I think at least less confusing than always
seeing width/height of zero. At least modeprint and modetest
seem to expect width/height to mean something.
Signed-off-by: Rob Clark <rob@ti.com>
If we have valid timings, we can at least set width/height to
*something*, which is I think at least less confusing than always
seeing width/height of zero. At least modeprint and modetest
seem to expect width/height to mean something.
Signed-off-by: Rob Clark <rob@ti.com>
xf86drmMode.c | diff | blob | history |