[PATCH] drm/vgem: drop DRIVER_PRIME (v2)

Dave Airlie airlied at gmail.com
Mon May 25 23:18:24 PDT 2015

On 22 May 2015 at 02:54, Thomas Hellstrom <thellstrom at vmware.com> wrote:
> On 05/21/2015 06:07 PM, Daniel Vetter wrote:
>> On Thu, May 21, 2015 at 11:58:30AM -0400, Rob Clark wrote:
>>> For actual sharing of buffers with other drivers (ie. actual hardware)
>>> we'll need to pimp things out a bit better to deal w/ caching, multiple
>>> memory domains, etc.  See thread:
>>>   https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_archives_dri-2Ddevel_2015-2DMay_083160.html&d=AwIDAw&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=vpukPkBtpoNQp2IUKuFviOmPNYWVKmen3Jeeu55zmEA&m=5PY5xMHJsYyknpy_IWAegxqACOaf4x60CKosyG0oxCw&s=ciVeRE10840cewxQSgbJ_4YfCH6tU8A1o58k0tHgkD8&e=
>>> But for the llvmpipe use-case this isn't a problem.  Nor do we really
>>> need prime/dri3 (dri2 is sufficient).  So until the other issues are
>>> sorted lets remove DRIVER_PRIME.
>>> v2: also drop the dead code
>>> Signed-off-by: Rob Clark <robdclark at gmail.com>
>> Yeah I'm ok with this too, but it pretty much means vgem is a thing for
>> llvmpipe only. And then abusing dumb buffers is imo ok too, since I don't
>> care too much what kind of horrors drivers pull of internally.
>> Acked-by: Daniel Vetter <daniel.vetter at ffwll.ch>
> Well in the end, I'm happy whatever way as long as the root problem is
> solved.
> Acked-by: Thomas Hellstrom <thellstrom at vmware.com>

I've applied this, mainly because controversy is bad, so new APIs
should never have any, please try and sort out a decent interface on
the list,


More information about the dri-devel mailing list