staging: unisys: visorinput: remove need for 'depends on FB'
authorTim Sell <Timothy.Sell@unisys.com>
Wed, 31 Jan 2018 16:41:12 +0000 (11:41 -0500)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 16 Feb 2018 14:42:22 +0000 (15:42 +0100)
commit385a9cb3471c79289a1ee90dd2c381405d3615d9
treec0932157a8d364109000fe9033b265a742574d65
parent17eb0b29c2604f09b346e8de695dc81b84afd1bd
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>
drivers/staging/unisys/visorinput/Kconfig
drivers/staging/unisys/visorinput/visorinput.c