diff options
| author | Thomas Hellstrom <thellstrom@vmware.com> | 2016-02-11 09:40:55 +0100 |
|---|---|---|
| committer | Thomas Hellstrom <thellstrom@vmware.com> | 2016-05-30 13:59:42 +0200 |
| commit | 5036e9d11a899d831b1471f64132eefcf459b222 (patch) | |
| tree | 851a4fdae200ee5ca46ab15fe7ddb1e5ce259c21 /vmwgfx | |
| parent | 57d4499cc252bd1c3362a569ca7fd99ba6b645ed (diff) | |
vmware/vmwgfx: Don't require screen objects to run
Using the vmwgfx ldu backend works just as fine except that we're limited
to implicit layout placement.
With this test on, we may end up in the odd situation that the vmwgfx kernel
module and the vwmare legacy Xorg driver are enabled simultaneously, and that
is an unsupported configuration. It will also break resolutionKMS which will
be enabled based on vmwgfx version but should be disabled since the legacy
Xorg driver runs...
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
Diffstat (limited to 'vmwgfx')
| -rw-r--r-- | vmwgfx/vmwgfx_driver.c | 12 |
1 files changed, 0 insertions, 12 deletions
diff --git a/vmwgfx/vmwgfx_driver.c b/vmwgfx/vmwgfx_driver.c index 693b5ef..b9ee1db 100644 --- a/vmwgfx/vmwgfx_driver.c +++ b/vmwgfx/vmwgfx_driver.c @@ -554,18 +554,6 @@ drv_pre_init(ScrnInfoPtr pScrn, int flags) ms->check_fb_size = (vmwgfx_max_fb_size(ms->fd, &ms->max_fb_size) == 0); - if (vmwgfx_get_param(ms->fd, DRM_VMW_PARAM_HW_CAPS, &cap) != 0) { - xf86DrvMsg(pScrn->scrnIndex, X_ERROR, "Failed to detect device " - "screen object capability.\n"); - goto out_depth; - } - - if ((cap & SVGA_CAP_SCREEN_OBJECT_2) == 0) { - xf86DrvMsg(pScrn->scrnIndex, X_ERROR, "Device is not screen object " - "capable.\n"); - goto out_depth; - } - switch (pScrn->depth) { case 15: case 16: |