All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: "Zhou, David(ChunMing)" <David1.Zhou@amd.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Mesa Dev <mesa-dev@lists.freedesktop.org>
Cc: "Jérôme Glisse" <jglisse@redhat.com>,
	"Jian, Dimple" <Dimple.Jian@amd.com>,
	"Ben Skeggs" <skeggs@redhat.com>,
	"Kuehling, Felix" <Felix.Kuehling@amd.com>,
	"Karol Herbst" <karolherbst@gmail.com>,
	"He, Jacob" <Jacob.He@amd.com>, "Sean Paul" <sean@poorly.run>,
	"Kenneth Graunke" <kenneth@whitecape.org>,
	"Daniel Vetter" <daniel.vetter@intel.com>,
	"Jin, Jian-Rong" <Jian-Rong.Jin@amd.com>
Subject: Re:[PATCH] gpu/docs: Clarify what userspace means for gl
Date: Wed, 24 Apr 2019 12:22:25 -0700	[thread overview]
Message-ID: <87zhofryxa.fsf@anholt.net> (raw)
In-Reply-To: <y43gqbci309xg9w6crog6em4kgicyh-vy2sqa-wo1neg-1ur9c7-pntgn6ulsicfgqvlq1kofqji-5kexatr29g4m5haisq-gx1i81-3rx6azh3q705d5pqn-doosx0m4a2n9pbuaqn8l56t7-sydjlu.1556114668390@email.android.com>


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

"Zhou, David(ChunMing)" <David1.Zhou@amd.com> writes:

> Will linux be only mesa-linux? I thought linux is an  open linux.
> Which will impact our opengl/amdvlk(MIT open source), not sure Rocm:
> 1. how to deal with one uapi that opengl/amdvlk needs but mesa dont need? reject?
> 2. one hw feature that opengl/amdvlk developers work on that but no mesa
> developers work on, cannot upstream as well?

I believe these questions are already covered by

"+Other userspace is only admissible if exposing a given feature through OpenGL
or
+OpenGL ES would result in a technically unsound design, incomplete driver or
+an implementation which isn't useful in real world usage."

If OpenGL needs the interface, then you need a Mesa implementation.
It's time for you to work with the community to build that or get it
built.  Or, in AMD's case, work with the Mesa developers that you
already employ.

If OpenGL doesn't need it, but Vulkan needs it, then we don't have a
clear policy in place, and this patch doesn't change that.  I would
personally say that AMDVLK doesn't qualify given that as far as I know
there is not open review of proposed patches to the project as they're
being developed.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-04-24 19:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 13:46 [PATCH] gpu/docs: Clarify what userspace means for gl Daniel Vetter
2019-04-24 14:24 ` Zhou, David(ChunMing)
2019-04-24 14:28   ` [PATCH] " Daniel Vetter
2019-04-24 14:36     ` Daniel Vetter
2019-04-24 14:57       ` Chunming Zhou
2019-04-24 19:22   ` Eric Anholt [this message]
2019-04-25  3:28     ` zhoucm1
2019-04-25  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=87zhofryxa.fsf@anholt.net \
    --to=eric@anholt.net \
    --cc=David1.Zhou@amd.com \
    --cc=Dimple.Jian@amd.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=Jacob.He@amd.com \
    --cc=Jian-Rong.Jin@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jglisse@redhat.com \
    --cc=karolherbst@gmail.com \
    --cc=kenneth@whitecape.org \
    --cc=mesa-dev@lists.freedesktop.org \
    --cc=sean@poorly.run \
    --cc=skeggs@redhat.com \
    /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.