From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Dave Airlie <airlied@gmail.com>
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Jason Ekstrand" <jason@jlekstrand.net>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm: turn syncobj timeline support off by default
Date: Tue, 16 Apr 2019 10:51:12 +0100 [thread overview]
Message-ID: <bb5105dc-9238-e20c-a68b-e571d873c540@intel.com> (raw)
In-Reply-To: <CAPM=9tx6XtjjfCFv2fJ4L7B2SxFRRzOz_mnu7hB+DsnGy0_QxA@mail.gmail.com>
On 15/04/2019 21:23, Dave Airlie wrote:
> On Tue, 16 Apr 2019 at 06:05, Lionel Landwerlin
> <lionel.g.landwerlin@intel.com> wrote:
>> On 15/04/2019 20:52, Dave Airlie wrote:
>>> On Tue, 16 Apr 2019 at 05:48, Lionel Landwerlin
>>> <lionel.g.landwerlin@intel.com> wrote:
>>>> Unfortunately userspace users of this API cannot be publicly disclosed
>>>> yet so disable this stuff by default until all is revealed.
>>> This begs the question how userspace is meant to know we support these?
>>>
>>> Is there a CAP for it? if not why not?
>>>
>>> Dave.
>>>
>> This comes with a submission path, so in i915 I've added a CAP.
>>
>> AMD seems to have a versioned interface.
> I think we would do like we did for syncobjs, you have a generic cap
> that the driver controls.
>
> The versioned interface won't be useful if we decide to backport a fix for this.
>
> Dave.
Okay, but then it's not a global setting anymore :)
Which is what was suggested on IRC.
I'm fine with it regardless :)
-Lionel
>
>>
>> -Lionel
>>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-16 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 19:48 [PATCH] drm: turn syncobj timeline support off by default Lionel Landwerlin
2019-04-15 19:52 ` Dave Airlie
2019-04-15 20:05 ` Lionel Landwerlin
2019-04-15 20:23 ` Dave Airlie
2019-04-16 9:51 ` Lionel Landwerlin [this message]
2019-04-16 10:40 ` Daniel Vetter
2019-04-16 7:43 ` Daniel Vetter
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=bb5105dc-9238-e20c-a68b-e571d873c540@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=airlied@gmail.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason@jlekstrand.net \
/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.