"Zhou, David(ChunMing)" <david1.z...@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.
signature.asc
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
