On 21/03/2019 19:04, Eric Anholt wrote:
I've just put up a new repo that I'm hoping to use to enable automatic
shader-db results for various drivers on Gitlab CI merge requests (and
maybe with some more work, delete the simulator backends of vc4 and v3d).
https://gitlab.freedesktop.org/anholt/drm-shim
I've copied a bit of Mesa stuff out for convenience, but that ends up
actually being most of the code in the repo since it's not really that
much work. Alternatively, I have a branch of most of it, inside of
Mesa, if we wanted to just add it in as one of the tools.
Does anyone have any strong feelings about where it should go?
mesa/mesa, mesa/drm-shim, or anholt/drm-shim?
I've been thinking about writing a validation layer for commands
submitted by anv/i965/iris.
Because it would need to decode the stream and parse it, genxml is kind
of needed, so obviously mesa/mesa would be easier.
-Lionel
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
