linux/drivers/staging/unisys
Tim Sell 385a9cb347 staging: unisys: visorinput: remove need for 'depends on FB'
Previously, we used a hack to determine the max x,y resolution of the
visor virtual mouse: we just looked at the resolution of the
first-registered framebuffer device, using the currently-valid assumption
that in a Unisys s-Par guest environment the video will be provided by an
efifb framebuffer device.

This hack has been removed, by instead determining the default mouse
resolution by looking at fields within the visor mouse channel memory,
mouse.x_res and mouse.y_res.  If these fields are 0, a default resolution
of 1024x768 is assumed.

Signed-off-by: Tim Sell <Timothy.Sell@unisys.com>
Signed-off-by: David Kershner <david.kershner@unisys.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-02-16 15:42:22 +01:00
..
Documentation staging: unisys: Switch to use new generic UUID API 2017-08-22 14:56:03 -07:00
include drivers: visorbus: move driver out of staging 2017-12-08 16:37:50 +01:00
visorhba drivers: visorbus: move driver out of staging 2017-12-08 16:37:50 +01:00
visorinput staging: unisys: visorinput: remove need for 'depends on FB' 2018-02-16 15:42:22 +01:00
visornic drivers: visorbus: move driver out of staging 2017-12-08 16:37:50 +01:00
Kconfig drivers: visorbus: move driver out of staging 2017-12-08 16:37:50 +01:00
MAINTAINERS staging: unisys: Fix incorrect unisys MAINTAINERS pattern 2017-11-02 11:45:57 +01:00
Makefile drivers: visorbus: move driver out of staging 2017-12-08 16:37:50 +01:00
TODO