drm/fb: fix FBIOGET/PUT_VSCREENINFO pixel clock handling

When the framebuffer driver does not publish detailed timing information
for the current video mode, the correct value for the pixclock field is
zero, not -1.

Since pixclock is actually unsigned, the value -1 would be interpreted
as 4294967295 picoseconds (i.e., about 4 milliseconds) by
register_framebuffer() and userspace programs.

This patch allows X.org's fbdev driver to work.

Signed-off-by: Clemens Ladisch <[email protected]>
Tested-by: Paulius Zaleckas <[email protected]>
Cc: [email protected]
Signed-off-by: Dave Airlie <[email protected]>

0 files changed, 0 insertions, 0 deletions