From: "Keith Packard" <keithp@keithp.com>
To: Jason Ekstrand <jason@jlekstrand.net>
Cc: ML mesa-dev <mesa-dev@lists.freedesktop.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/7] vulkan: Add KHR_display extension to anv and radv using DRM
Date: Mon, 12 Mar 2018 16:02:23 -0700 [thread overview]
Message-ID: <87po483nk0.fsf@keithp.com> (raw)
In-Reply-To: <CAOFGe96bFpcAJsW7ACMx=3Ei-_gB74GFza=J1cNBysOLTPTPTg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]
Jason Ekstrand <jason@jlekstrand.net> writes:
> On Fri, Feb 23, 2018 at 3:43 PM, Keith Packard <keithp@keithp.com> wrote:
>
> Once we're sure that's what we want, create an MR against the spec that
> just adds enough to the XML to reserve your extension number. That will
> get merged almost immediately. Then make a second one with the actual
> extension text and we'll iterate on that either in Khronos gitlab or, if
> you prefer, you can send it as a patch to mesa-dev and then make a Khrons
> MR once it's baked.
I just wrote up the full extension description for both extensions I
need (the one for passing a KMS fd to the driver, and the second to get
the GPU timestamp for doing GOOGLE_display_timing):
https://github.com/keith-packard/Vulkan-Docs
> See also my comments about GEM handle ownership.
Yeah, I think I've got that all cleaned up now -- the code no longer
shares the same file for rendering and display.
--
-keith
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-03-12 23:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 4:45 [PATCH 0/7] vulkan: Add direct display extensions Keith Packard
2018-02-10 4:45 ` [PATCH 1/7] vulkan: Add KHR_display extension to anv and radv using DRM Keith Packard
2018-02-12 15:27 ` Eric Engestrom
2018-02-12 22:16 ` Keith Packard
2018-02-12 16:18 ` [Mesa-dev] " Emil Velikov
2018-02-12 23:12 ` Keith Packard
2018-02-14 1:10 ` Jason Ekstrand
2018-02-15 17:46 ` Keith Packard
2018-02-23 23:00 ` Jason Ekstrand
2018-02-23 23:43 ` Keith Packard
2018-02-24 0:51 ` Jason Ekstrand
2018-03-12 23:02 ` Keith Packard [this message]
2018-03-29 6:59 ` Mao, David
2018-03-29 15:05 ` Keith Packard
2018-02-10 4:45 ` [PATCH 2/7] vulkan: Add EXT_direct_mode_display Keith Packard
2018-02-10 4:45 ` [PATCH 3/7] vulkan: Add EXT_acquire_xlib_display Keith Packard
2018-02-13 0:16 ` Dylan Baker
2018-02-10 4:45 ` [PATCH 4/7] vulkan: Add VK_EXT_display_surface_counter [v4] Keith Packard
2018-02-10 4:45 ` [PATCH 5/7] vulkan: add VK_EXT_display_control [v4] Keith Packard
2018-02-10 4:45 ` [PATCH 6/7] vulkan: Add new VK_MESA_query_timestamp extension Keith Packard
2018-02-13 0:20 ` Dylan Baker
2018-02-13 10:49 ` [Mesa-dev] " Lionel Landwerlin
2018-02-13 21:11 ` Keith Packard
2018-02-10 4:45 ` [PATCH 7/7] vulkan: Add VK_GOOGLE_display_timing extension (x11 and display backends) Keith Packard
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=87po483nk0.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason@jlekstrand.net \
--cc=mesa-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox