From: Daniel Stone <daniel@fooishbar.org>
To: "Christian König" <deathsimple@vodafone.de>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm: Add DRM_CAP_PRIME_SCANOUT.
Date: Tue, 4 Apr 2017 12:32:49 +0100 [thread overview]
Message-ID: <CAPj87rNu_Ku=ZVOugnO_YnzjhjuYyNqSmQm_zJYrsbp0JL83pg@mail.gmail.com> (raw)
In-Reply-To: <8401a897-53b3-d072-1482-b066b302be3e@vodafone.de>
Hi,
On 4 April 2017 at 12:15, Christian König <deathsimple@vodafone.de> wrote:
> Am 04.04.2017 um 12:43 schrieb Daniel Stone:
>> Yeah, the ABI is that AddFB2 should fail hard on something which can
>> never be used as a framebuffer. The fact it didn't is a bug rather
>> than a behavioural change per se ...
>
> I agree on that, but the problem Christopher tries to solve looks a bit
> different from my perspective.
>
> He wants to know if a driver can scan out from a foreign BO or if he needs
> to copy the content.
>
> The problem I see with this patch is that the kernel doesn't look like the
> right place for this decision to make.
Any number of constraints exist there: 'can I use any completely
arbitrary dmabuf from anywhere?' doesn't express the full range. AddFB
can fail for other totally legitimate reasons, so to me it makes the
most sense to centralise the checks there.
Cheers,
Daniel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-04 11:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 8:13 [PATCH] Tell userspace if scanning out of an imported PRIME buffer is safe raof
2017-04-04 8:13 ` [PATCH 1/2] drm: Add DRM_CAP_PRIME_SCANOUT raof
2017-04-04 8:31 ` Daniel Vetter
2017-04-04 10:11 ` Daniel Stone
2017-04-04 10:27 ` Christopher James Halse Rogers
2017-04-04 10:43 ` Lucas Stach
2017-04-04 11:53 ` Daniel Vetter
2017-04-05 0:20 ` Christopher James Halse Rogers
2017-04-05 6:27 ` Daniel Vetter
2017-04-05 6:52 ` Christopher James Halse Rogers
2017-04-05 8:15 ` Lucas Stach
2017-04-05 9:59 ` Daniel Vetter
2017-04-05 10:14 ` Lucas Stach
2017-04-05 11:13 ` Christopher James Halse Rogers
2017-04-05 11:21 ` Christian König
2017-04-10 8:52 ` Michel Dänzer
2017-04-10 9:03 ` Christian König
2017-04-10 14:10 ` Alex Deucher
2017-04-06 7:47 ` Christopher James Halse Rogers
2017-04-10 8:51 ` Michel Dänzer
2017-04-17 5:05 ` Christopher James Halse Rogers
2017-04-17 6:41 ` Michel Dänzer
2017-04-04 10:43 ` Daniel Stone
2017-04-04 11:15 ` Christian König
2017-04-04 11:32 ` Daniel Stone [this message]
2017-04-04 11:43 ` Christian König
2017-04-04 8:13 ` [PATCH 2/2] drm/i915: support DRIVER_PRIME_SCANOUT raof
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='CAPj87rNu_Ku=ZVOugnO_YnzjhjuYyNqSmQm_zJYrsbp0JL83pg@mail.gmail.com' \
--to=daniel@fooishbar.org \
--cc=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.