kernel/drivers/gpu/drm/vmwgfx/Makefile, branch linux-4.1.y

drm/vmwgfx: Fix compat shader namespace

2014-07-04T10:12:09Z

Contrary to the host-backed shader interface that has a per-context name-space for shaders, the compat shader namespace was per client (or rather, per file). Fix this so that the compat shader namespace is per context, and at the same time, make command buffer managed context resource management generic. Signed-off-by: Thomas Hellstrom Reviewed-by: Jakob Bornecrantz

drm/vmwgfx: Add guest-backed shaders

2014-01-17T06:52:27Z

Signed-off-by: Thomas Hellstrom Reviewed-by: Brian Paul Reviewed-by: Zack Rusin

drm/vmwgfx: Add MOB management

2014-01-17T06:52:19Z

Implement MOB setup, binding and unbinding, but don't hook up to TTM yet. Signed-off-by: Thomas Hellstrom Reviewed-by: Brian Paul Reviewed-by: Zack Rusin

drm/vmwgfx: Hook up the prime ioctls

2013-11-18T12:11:53Z

Also provide a completely dumb dma-buf ops implementation. Once we have other virtual dma-buf aware devices, we need to provide something better. Signed-off-by: Thomas Hellstrom Reviewed-by: Jakob Bornecrantz

drm/vmwgfx: Break out surface and context management to separate files

2012-11-20T21:47:08Z

Add a resource-private header for common resource definitions Signed-off-by: Thomas Hellstrom Reviewed-by: Brian Paul Reviewed-by: Dmitry Torokhov Signed-off-by: Dave Airlie

vmwgfx: Add screen object support

2011-10-05T09:17:14Z

Signed-off-by: Jakob Bornecrantz Signed-off-by: Thomas Hellstrom Signed-off-by: Dave Airlie

vmwgfx: Add dmabuf helper functions for pinning

2011-10-05T09:17:13Z

Signed-off-by: Jakob Bornecrantz Signed-off-by: Thomas Hellstrom Signed-off-by: Dave Airlie

vmwgfx: Implement fence objects

2011-09-06T10:51:11Z

Will be needed for queries and drm event-driven throttling. As a benefit, they help avoid stale user-space fence handles. Signed-off-by: Thomas Hellstrom Reviewed-by: Jakob Bornecrantz Signed-off-by: Dave Airlie

vmwgfx: Fix confusion caused by using "fence" in various places

2011-09-06T10:48:40Z

This is needed before we introduce the fence objects. Otherwise this will be even more confusing. The plan is to use the following: seqno: A 32-bit sequence number that may be passed in the fifo. marker: Objects, carrying a seqno, that track fifo submission time. They are used for fifo lag based throttling. fence objects: Kernel space objects, possibly accessible from user-space and carrying a 32-bit seqno together with signaled status. Signed-off-by: Thomas Hellstrom Reviewed-by: Jakob Bornecrantz Signed-off-by: Dave Airlie

vmwgfx: Implement a proper GMR eviction mechanism

2010-10-27T01:07:46Z

Use Ben's new range manager hooks to implement a manager for GMRs that manages ids rather than ranges. This means we can use the standard TTM code for binding, unbinding and eviction. Signed-off-by: Thomas Hellstrom Signed-off-by: Dave Airlie