You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
Frequency of occurance. Command line output. Stack trace.
The attached Vulkan application runs on a Raspberry Pi 4, although the Pi4 uses a completely different Vulkan driver.
I was hoping to run it on a 3B+ using rpi-vk-driver, however when vkCreateShaderModule() is called, rpi-vk-driver returns VK_ERROR_OUT_OF_HOST_MEMORY.
Further inspection reveals that VK_ERROR_OUT_OF_HOST_MEMORY is returned because the shader magic for the shader does not add up, as seen here: https://github.com/Yours3lf/rpi-vk-driver/blob/master/driver/shader.c#L25
These same SPIR-V shaders run fine on a Raspberry Pi 4 (v3dv) as well as on mesa's RADV and NVIDIA's proprietary drivers for GTX graphics cards, so I suspect there is a driver issue.
Is there anything that can be done about this?
To Reproduce
Steps to reproduce the behavior:
Extract the attached zip file to some directory- the executable "micro0" and "data" should be in the same directory.
In a terminal, cd to the directory containing "micro0" and "data", then run micro0: ./micro0
The program will error and close due to vkCreateShaderModule() failing, and if you add a printf() statement to the if(magic != 0x14E45250) if statement block in the driver, you will find the driver is returning VK_ERROR_OUT_OF_HOST_MEMORY due to bad shader magic.
Expected behavior
At the very least, vkCreateShaderModule() should complete successfully, because I know these are good/valid SPIR-V shaders.
Given vkCreateShaderModule() completes successfully, the program should probably run fine then-
there could be other non-driver issues running this application on the 3B+ that I have not discovered yet, but probably not since it runs fine on the Pi4 and other Vulkan drivers.
Device information (please complete the following information):
Device info (eg. Raspberry Pi 3 Model A+)
OS information (cat /proc/version, lsb_release -a)
Kernel module information: lsmod
Driver version (git commit ID or release info)
Tested on a Raspberry Pi 3B+ running Raspbian.
Driver version: git-c95f714
This driver does not support SPIR-V, you need to use assembly, please see the numerous examples :)
If you feel like that, feel free to add SPIR-V support, I'd gladly merge it.
Describe the bug
A clear and concise description of what the bug is.
Frequency of occurance. Command line output. Stack trace.
The attached Vulkan application runs on a Raspberry Pi 4, although the Pi4 uses a completely different Vulkan driver.
I was hoping to run it on a 3B+ using rpi-vk-driver, however when vkCreateShaderModule() is called, rpi-vk-driver returns VK_ERROR_OUT_OF_HOST_MEMORY.
Further inspection reveals that VK_ERROR_OUT_OF_HOST_MEMORY is returned because the shader magic for the shader does not add up, as seen here: https://github.com/Yours3lf/rpi-vk-driver/blob/master/driver/shader.c#L25
These same SPIR-V shaders run fine on a Raspberry Pi 4 (v3dv) as well as on mesa's RADV and NVIDIA's proprietary drivers for GTX graphics cards, so I suspect there is a driver issue.
Is there anything that can be done about this?
To Reproduce
Steps to reproduce the behavior:
./micro0
if(magic != 0x14E45250)
if statement block in the driver, you will find the driver is returning VK_ERROR_OUT_OF_HOST_MEMORY due to bad shader magic.Expected behavior
At the very least, vkCreateShaderModule() should complete successfully, because I know these are good/valid SPIR-V shaders.
Given vkCreateShaderModule() completes successfully, the program should probably run fine then-
there could be other non-driver issues running this application on the 3B+ that I have not discovered yet, but probably not since it runs fine on the Pi4 and other Vulkan drivers.
Device information (please complete the following information):
Tested on a Raspberry Pi 3B+ running Raspbian.
Driver version: git-c95f714
micro0.zip
The text was updated successfully, but these errors were encountered: