dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Jason Ekstrand <jason@jlekstrand.net>
Cc: Chad Versace <chadversary@chromium.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Vulkan WSI+VK_KHR_display for KMS/DRM?
Date: Tue, 04 Apr 2017 08:40:06 -0700	[thread overview]
Message-ID: <86a87wgp0p.fsf@hiro.keithp.com> (raw)
In-Reply-To: <CAOFGe94DtfmkugO2TocjhRe+dREa67mFgavsaVQc_TBqvB5CEw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 590 bytes --]

Jason Ekstrand <jason@jlekstrand.net> writes:

> Interesting question.  To my knowledge, no one has actually implemented the
> Vulkan WSI direct-to-display extensions.  (I tried to prevent them from
> getting released with 1.0 but failed.)  I believe the correct answer is to
> use the external memory dma-buf stuff that chad and I have been using and
> talk directly to KMS.

Sounds good, and minimizes the amount of code I have to write too :-)

> I see no good reason to have a large abstraction in
> the middle.

Other than 'it's a standard', neither do I.

-- 
-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

  reply	other threads:[~2017-04-04 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01  4:11 Vulkan WSI+VK_KHR_display for KMS/DRM? "Keith Packard"
2017-04-03 19:44 ` Chad Versace
2017-04-03 19:56   ` Keith Packard
2017-04-04 14:45     ` Jason Ekstrand
2017-04-04 15:40       ` Keith Packard [this message]
2017-04-10 19:29         ` Chad Versace
2017-04-10 19:32           ` Jason Ekstrand
2017-04-11 15:05             ` James Jones
2017-04-11  2:57       ` Michel Dänzer

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=86a87wgp0p.fsf@hiro.keithp.com \
    --to=keithp@keithp.com \
    --cc=chadversary@chromium.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox