- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was thinking with vulkan samples and found that there was a compile option for linux to enable direct to display extension. I have an intel GPU on my linux box and it results that it cannot find the extension.
doing some digging tonight I found that nVIdia released a driver in May 2017 that supports it...
This is the extension name in vulkan headers...
https://github.com/ARM-software/vulkan-sdk/blob/master/include/vulkan/vulkan.h#L3379
Vulkan samples referencing said extension...
https://github.com/SaschaWillems/Vulkan/blob/master/base/vulkanexamplebase.cpp#L35 ; (
https://github.com/SaschaWillems/Vulkan/blob/master/base/VulkanSwapChain.hpp#L514 ;
Please Add support for vulkan direct to display? I have a framework already that works as a window driver that doesn't require X... it can work with just framebuffer, but would really like to leverage 3D and accelerated 2D output which OpenGL Never was able to support.
was just testing on my router which is able to run Vulkan samples through wayland, my next attempt was going to be on my Intel NUC; but realized it had intel chip too... so I started digging to see if it was just a driver issue, and have only found reference to nVidia supporting said mode.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Noone reads these?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For questions and issues with the Mesa driver, your best options are:
- File a bug in Mesa's public bug tracker: https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa . In the component field, select Drivers/DRI./i965.
- Send a message to Mesa's development mailing list http://lists.freedesktop.org/mailman/listinfo/mesa-dev .
- Most of the Intel Mesa developers are on IRC in irc://irc.freenode.net/#intel-gfx or irc://irc.freenode.net/#dri-devel. People there are very helpful.
I suggest that you open a Bugzilla ticket with the information in this post. The team will probably then ask you a lot of clarifying questions (OS? gpu pci id? Mesa version? etc etc).
Also, it's often helpful to directly contact the owner of the Mesa package for your Linux distribution. Sometimes the package owner is very familiar with frequent bugs that are specific to that distribution. On RPM based distros, such as Fedora, you can find the packager by examining the package's changelog with this command: `rpm -q --changelog mesa-libGL`. On Debian based distros, such as Ubuntu, I think the apt-cache command gives you the needed info.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for the additional avenues to pursue this :)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page