1
0
mirror of https://github.com/Yours3lf/rpi-vk-driver.git synced 2024-11-29 11:24:14 +01:00
rpi-vk-driver/README.md

65 lines
2.9 KiB
Markdown
Raw Normal View History

2018-08-03 17:06:01 +02:00
# rpi-vk-driver
(not conformant yet, can't use official name or logo)
2018-08-26 15:49:21 +02:00
## Milestones
- [x] clear screen example working
2018-10-14 18:29:57 +02:00
- [x] triangle example working
- [x] shader from assembly, vertices from vertex buffer object, no uniforms, color hardcoded
2019-08-25 20:03:04 +02:00
- [x] uniforms for matrix multiplication and animation
- [x] texture coordinates and texture sampling
- [ ] varyings
2019-07-05 22:19:59 +02:00
- [x] Shader compiler chain
2019-07-05 21:53:50 +02:00
- [x] QPU assembler / disassembler
2019-08-21 23:13:08 +02:00
- [x] Resources
- [x] Descriptor support
- [x] VkSampler support
2019-07-27 22:59:24 +02:00
- [x] Push constant support
2019-07-05 22:19:59 +02:00
- [ ] Multipass rendering
- [ ] VkRenderPass support
- [ ] Subpass support
- [ ] Synchronization
- [ ] vkCmdPipelineBarrier support
- [ ] VkEvent support
- [ ] Indexed draw call support
- [ ] Clear command support
- [ ] Layer support
- [ ] Pipeline cache support
2019-07-05 22:32:33 +02:00
- [ ] Try to pass as much of the VK CTS as possible with existing feature set
2019-07-05 22:19:59 +02:00
2018-11-17 16:57:20 +01:00
## VK CTS progress
2019-02-09 17:20:14 +01:00
- Passed: 7894/67979 (11.6%)
- Failed: 878/67979 (1.3%)
- Not supported: 59206/67979 (87.1%)
- Warnings: 1/67979 (0.0%)
2018-11-17 17:39:13 +01:00
2019-02-09 17:24:29 +01:00
Conformance run is considered passing if all tests finish with allowed result
codes.
Following status
codes are allowed:
- Pass
- NotSupported
- QualityWarning
- CompatibilityWarning
2019-09-04 12:38:12 +02:00
There are about 470.000 conformance tests.
2018-11-17 17:39:13 +01:00
## FAQ
### Will this ever be a fully functional VK driver?
As far as I know the PI is NOT fully VK capable on the hardware level. I can already see that some things will need to be emulated and others won't ever be emulated. The compiler is also a huge unknown at this point as I plan to write one from scratch.
### What performance should you expect?
Performance wise, the Pi is quite capable. The specs and architecture is close to the GPU in the iPhone 4s. The only problem I see is bandwidth as you only have about 7GB/s compared to 12-25GB/s on typical mobile phones. So post processing is a huge no and you'd need to be very careful about the techniques that you use. Eg. you'd need to stay on chip at all times.
2018-11-17 17:39:36 +01:00
CPU performance (eg. number of draw calls) should be enough on the quad-core PIs as you can easily utilise all cores using VK.
2018-11-17 17:39:13 +01:00
### What will be emulated?
- I already plan to emulate a couple of the basics such as copy commands using compute
- Tessellation and geometry shaders won't be considered, it just doesn't make sense
- Sparse resources might be implemented, but I don't think performance would be great
- Compute shaders could also be implemented, though I think I would need to modify the kernel side for that, no LDS or any of the fancy stuff though...
- As far as I know the PI doesn't support occlusion queries (https://github.com/anholt/mesa/wiki/VC4-OpenGL-support)
- Indirect draws are probably out of scope
- I already added support (to be polished) to load shader assembly. This will enable devs to optimise shaders to the last cycle.
- I'll probably add something to indicate towards the developer that things are emulated or not supported at all.