From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keith Packard <keithp@keithp.com>
Subject: Re: Vulkan WSI+VK_KHR_display for KMS/DRM?
Date: Mon, 03 Apr 2017 12:56:55 -0700
Message-ID: <86pogtgt88.fsf@hiro.keithp.com>
References: <86o9wgkbr1.fsf@hiro.keithp.com>
 <20170403194455.GA58999@chadversary.pdx.corp.google.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1118797580=="
Return-path: <dri-devel-bounces@lists.freedesktop.org>
Received: from elaine.keithp.com (home.keithp.com [63.227.221.253])
 by gabe.freedesktop.org (Postfix) with ESMTP id 5D75C6E04E
 for <dri-devel@lists.freedesktop.org>; Mon,  3 Apr 2017 19:56:57 +0000 (UTC)
In-Reply-To: <20170403194455.GA58999@chadversary.pdx.corp.google.com>
List-Unsubscribe: <https://lists.freedesktop.org/mailman/options/dri-devel>,
 <mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <https://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <https://lists.freedesktop.org/mailman/listinfo/dri-devel>,
 <mailto:dri-devel-request@lists.freedesktop.org?subject=subscribe>
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel" <dri-devel-bounces@lists.freedesktop.org>
To: Chad Versace <chadversary@chromium.org>
Cc: Jason Ekstrand <jason@jlekstrand.net>, dri-devel <dri-devel@lists.freedesktop.org>
List-Id: dri-devel@lists.freedesktop.org

--===============1118797580==
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Chad Versace <chadversary@chromium.org> writes:

> The real path forward should be implemented on top of
> VK_KHX_external_memory. If you want to start experimenting now with
> Vulkan+KMS, you may want to look at
> VK_EXTERNAL_MEMORY_HANDLE_OPAQUE_FD_KHX.

It seems like the Vulkan spec for WSI with devices has a bunch of what I
would need to implement in a standard fashion; I guess I'm unclear
whether I should go down the route of wrapping all of DRM/KMS in a WSI
layer, or use some of this lower-level stuff directly from the
application instead?

=2D-=20
=2Dkeith

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAljiqQcACgkQ2yIaaQAA
ABGOkBAAqmnFFkKO+CxYH05WxSKyaHNYc18bHDvvdlVX7X+KchiUttXhxeAf3fo2
HcWpVUjtFgt+2K2RaOe/+ysRifjWyYnTUr3447hY7H8VFd7e8JMIuK6oI3P62p4a
Dl0xAZ1qi9XLmc3qvxaZelboEZvAQ71hTaMqc5x0F26PBlKHa9XZhavEmG3EZIqr
D41hjRXB2qat2AXcpWmtEBxjdK41elF7CHHlWvmfV6wenflMXP5Q4Pykvs3sZcbF
SgtAjxlrGSX1o0FNf79GtYhmTkAhtlNCajVN6aEHWVukQVZWuDORK5akqkgbStcw
Ssv0GwIRdGA17Yg+zB2W43QUU8tYM+vjDCyb6xrkgKcVnQB6nABilVLGnWj2/GDT
TjIeRy/TI2EAlO6TVuBHQmi9kD+CaNFqaIidi7oFD0ueCLSI1v+96qKjpLZDM9Ij
1v9tB/ecN5iM321/bjFCbDotPgIf1v084pbwNwQKdZ6GEzX9VNqH8IWxNIBBpCTO
xTLJtBdotehJYqL48cgN3wls7zq6QLsOxilRqi/Xw90E8C6jSX1sATTSdOAS3duQ
PsQXRxFKS0Um60oD6gvO3gyRV01k4IjOwCM/HAzxmRetc/i6K/iidgzk13NlrPcX
QzxqYAYfWj/jTbCKf44TYDsIelxcV6GPP3Idmxv49InFe4YAU58=
=Lfid
-----END PGP SIGNATURE-----
--=-=-=--

--===============1118797580==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==

--===============1118797580==--