PixelyIon 6b9269b88e Introduce Context semantics to GPU resource locking ... Resources on the GPU can be fairly convoluted and involve overlaps which can lead to the same GPU resources being utilized with different views, we previously utilized fences to lock resources to prevent concurrent access but this was overly harsh as it would block usage of resources till GPU completion of the commands associated with a resource. Fences have now been replaced with locks but locks run into the issue of being per-view and therefore to add a common object for tracking usage the concept of "tags" was introduced to track a single context so locks can be skipped if they're from the same context. This is important to prevent a deadlock when locking a resource which has been already locked from the current context with a different view.		2022-08-06 22:18:42 +05:30
..
libraries	Remove PugiXML submodule	2022-07-26 20:16:24 +05:30
src/main	Introduce Context semantics to GPU resource locking	2022-08-06 22:18:42 +05:30
.gitignore	libNX FS Initalization (v0.3)	2019-10-18 16:22:38 +05:30
build.gradle	Only set hasFragileUserData for signed builds	2022-08-06 22:18:42 +05:30
CMakeLists.txt	Add utilities for reading and installing gpu driver packages	2022-08-06 22:00:19 +05:30
proguard-rules.pro	Add kotlinx.serialization-json dependencies	2022-08-06 22:00:19 +05:30