From: Thomas Hellstrom <thellstrom@vmware.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Zach Reizner" <zachr@google.com>,
dri-devel@lists.freedesktop.org,
"Stéphane Marchesin" <marcheu@chromium.org>
Subject: Re: [PATCH] drm/vgem: drop DRIVER_PRIME (v2)
Date: Thu, 21 May 2015 18:54:29 +0200 [thread overview]
Message-ID: <555E0DC5.7040402@vmware.com> (raw)
In-Reply-To: <20150521160730.GM15256@phenom.ffwll.local>
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@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@ffwll.ch>
>
>
Well in the end, I'm happy whatever way as long as the root problem is
solved.
Acked-by: Thomas Hellstrom <thellstrom@vmware.com>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-05-21 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 15:58 [PATCH] drm/vgem: drop DRIVER_PRIME (v2) Rob Clark
2015-05-21 16:07 ` Daniel Vetter
2015-05-21 16:10 ` Chris Wilson
2015-05-21 16:29 ` Rob Clark
2015-05-21 16:54 ` Thomas Hellstrom [this message]
2015-05-26 6:18 ` Dave Airlie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=555E0DC5.7040402@vmware.com \
--to=thellstrom@vmware.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=marcheu@chromium.org \
--cc=zachr@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox