From: Jakob Bornecrantz ja...@vmware.com
Make sure we null the display private, make sure we catch and
handle vblank failing to init and don't call vblank_cleanup if
we haven't initialized the display system.
Signed-off-by: Jakob Bornecrantz ja...@vmware.com
Signed-off-by: Thomas Hellstrom
From: Jakob Bornecrantz ja...@vmware.com
Signed-off-by: Jakob Bornecrantz ja...@vmware.com
Signed-off-by: Thomas Hellstrom thellst...@vmware.com
---
drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c |4 +---
drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c |5 ++---
2 files changed, 3 insertions(+), 6
From: Jakob Bornecrantz ja...@vmware.com
This fixes kernel panics when running the vbltest from the drm repo. We
can't just skip initializing the vblank system since it sets up certain
state for us, see: vmwgfx: Enable use of the vblank system.
Signed-off-by: Jakob Bornecrantz ja...@vmware.com
A couple of vmwgfx fixes on top of drm-next / drm-core-next.
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats,
