Closed burt111 closed 5 years ago
I have no idea how the VC 6 works, it's probably completely different. My guess is no.
For what I hear its not much diferent than vc4... and its vulkan capable on the hardware. There is no more mesa development for now (not really active at least, just minor fixes).
Got some info on this: it does seem to be closer in spec to VC4 but adds features on top of VC5 so likely everything you have been missing, sounds like they did it "right" for what I can imagine would be good (not best) case senerio.
All the features needed for opengl es 3.2 and vulkan 1.1
Thought it might encourage you :-) Ref: https://www.raspberrypi.org/forums/viewtopic.php?p=1492907&sid=60a7c5feeb6c773f6db9e15b39049d2b#p1492907
Should we ever have a working Vulkan driver for VC6 in mesa, I think it would be easier to "migrate" necessary VC4 code to mesa. That said - I think we are still years away ;)
This is on pi4 ...
pi@raspberrypi:~/src/mesa-/rpi-vk-driver $ ./depthTex supported extensions: VK_KHR_get_display_properties2 VK_KHR_get_physical_device_properties2 VK_KHR_get_surface_capabilities2 VK_KHR_surface VK_KHR_xcb_surface VK_KHR_xlib_surface VK_KHR_display VK_EXT_direct_mode_display VK_EXT_acquire_xlib_display VK_EXT_display_surface_counter VK_EXT_debug_report VK_KHR_external_memory_capabilities VK_EXT_debug_utils created vulkan instance physical device with vulkan support found physical device supports version 1.1.102 segmentation error
pi@raspberrypi:~/src/mesa-/rpi-vk-driver $ ./CPAtest
CPA Debug Print pa->buf 0xb84058 pa->nextFreeBlock 0xb84068 Linear walk: 0xb84058: (nil), 0xb84068: 0xb84078, 0xb84078: 0xb84088, 0xb84088: 0xb84098, 0xb84098: 0xb840a8, 0xb840a8: 0xb840b8, 0xb840b8: 0xb840c8, 0xb840c8: (nil), Linked List walk: 0xb84068: 0xb84078, 0xb84078: 0xb84088, 0xb84088: 0xb84098, 0xb84098: 0xb840a8, 0xb840a8: 0xb840b8, 0xb840b8: 0xb840c8, 0xb840c8: (nil),
mem 0xb84058
CPA Debug Print pa->buf 0xb840e0 pa->nextFreeBlock 0xb84110 Linear walk: 0xb840e0: (nil), 0xb840f0: (nil), 0xb84100: (nil), 0xb84110: 0xb84120, 0xb84120: 0xb84130, 0xb84130: 0xb84140, 0xb84140: 0xb84150, 0xb84150: (nil), Linked List walk: 0xb84110: 0xb84120, 0xb84120: 0xb84130, 0xb84130: 0xb84140, 0xb84140: 0xb84150, 0xb84150: (nil),
mem 0xb840e0
CPA Debug Print pa->buf 0xb84168 pa->nextFreeBlock (nil) Linear walk: 0xb84168: (nil), 0xb84178: (nil), 0xb84188: (nil), 0xb84198: (nil), 0xb841a8: (nil), 0xb841b8: (nil), 0xb841c8: (nil), 0xb841d8: (nil), Linked List walk:
mem 0xb84168
CPA Debug Print pa->buf 0xb841f0 pa->nextFreeBlock 0xb841f0 Linear walk: 0xb841f0: 0xb84200, 0xb84200: 0xb84210, 0xb84210: 0xb84220, 0xb84220: 0xb84230, 0xb84230: 0xb84240, 0xb84240: 0xb84250, 0xb84250: 0xb84260, 0xb84260: (nil), Linked List walk: 0xb841f0: 0xb84200, 0xb84200: 0xb84210, 0xb84210: 0xb84220, 0xb84220: 0xb84230, 0xb84230: 0xb84240, 0xb84240: 0xb84250, 0xb84250: 0xb84260, 0xb84260: (nil),
mem (nil)
this driver only supports the Videocore IV GPU, so only RPi 0, 1, 2, 3 are supported. Give it a go there and let me know how that went.
Official Raspberry Pi 4 Vulkan driver is in development by the consulting firm Igalia with a recent status update.
Previous MESA efforts for VC4 Vulkan support can be found in some vc4/v3d WIP branches by Eric Anholt.
See Phoronix for good media coverage (this is how I became aware of the project in the first place)!
Just wondering if this would still work on the pi with videocore vi or is it incompatible