Announcement

Collapse
No announcement yet.

Zink's OpenGL Over Vulkan Implementation Aiming For Mesa 19.3 Integration

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • microcode
    replied
    Originally posted by boxie View Post

    Then you have device specific work around and optimisations that the underlying drivers may not be able to do
    Like I said, if the underlying device has some performance-critical behaviour that a GL driver should use, then that should be exposed through Vulkan extensions anyway.

    Leave a comment:


  • boxie
    replied
    Originally posted by microcode View Post

    I do wonder a bit about that. It seems like if there are characteristics that affect performance in that way, they should be exposed by Vulkan API extensions at least.
    Then you have device specific work around and optimisations that the underlying drivers may not be able to do

    Leave a comment:


  • microcode
    replied
    Originally posted by boxie View Post

    pretty sure that if you want to get the best performance you will still want to go with a dedicated driver.
    I do wonder a bit about that. It seems like if there are characteristics that affect performance in that way, they should be exposed by Vulkan API extensions at least.

    Leave a comment:


  • boxie
    replied
    Originally posted by microcode View Post
    Very cool, I hope to see the market for custom GL drivers to dry up quickly.
    pretty sure that if you want to get the best performance you will still want to go with a dedicated driver.

    Leave a comment:


  • boxie
    replied
    I am looking forward to the Benchmark/Perf Improve cycle for Zink - I know the first cut is going to have some rough edges performance wise but going forward it is going to be pretty cool!

    it *should* make device bringup a little easier (with only needing to do a vulkan driver instead of opengl+vulkan driver to get a working environment), but I am not a driver developer so I could also be full of shite

    Leave a comment:


  • microcode
    replied
    Very cool, I hope to see the market for custom GL drivers to dry up quickly.

    Leave a comment:


  • murraytony
    replied
    Vulkan is really turning out to be a boon.

    Leave a comment:


  • Meteorhead
    replied
    Originally posted by asdfgh View Post

    It doesn't work with proprietary nv stuff.
    I think the main focus of Mesa projects are to be self-contained so that they work well together. Nouveau might be a more reasonable target. Don't know if it has any Vulkan capabilities or not.

    If only clvk/clspv would make it into mesa, RADV could drive Vulkan/OpenGL/OpenCL/SYCL and all their interop layers.

    Leave a comment:


  • asdfgh
    replied
    Originally posted by uid313 View Post
    This means that if a device driver implements support for Vulkan, then it also gets support for OpenGL for free?
    Nope, at least now. See https://twitter.com/oscarbg81/status...08754886647808. It doesn't work with proprietary nv stuff.

    Leave a comment:


  • uid313
    replied
    This means that if a device driver implements support for Vulkan, then it also gets support for OpenGL for free?

    Leave a comment:

Working...
X