> - Highly recommended: A fully functional drm-shim for each CI job with > a user guide, how to print compiled shaders, etc.
If we go this route, I would like to mandate drm-shim availability for hardware drivers. When I was doing the nir_def work back in 2023, drm-shim was my main way of debugging all the backends. Fortunately I think (almost?) everyone has that these days, and it's really only layered impls that don't/can't. -- In effect we already have such a two tier system informally, it's just not documented anywhere. "Mali support is tier 1 and Apple support is tier 2" in Mesa is a position that should be controversial to nobody. ... The problem is that none of this is formalized so the rules & definitions only exist in people's heads :) So I'm not against anything you've written. But it's not a radical change either, largely just writing some docs!
