Petri Latvala <petri.latv...@intel.com> writes: > On Wed, Nov 14, 2018 at 02:28:32PM -0800, Eric Anholt wrote: >> These are basic non-rendering tests of the UABI. >> >> Signed-off-by: Eric Anholt <e...@anholt.net> >> --- >> lib/igt_v3d.c | 4 -- >> tests/Makefile.am | 2 + >> tests/Makefile.sources | 6 +++ >> tests/meson.build | 3 ++ >> tests/v3d_ci/README | 26 +++++++++++++ >> tests/v3d_ci/v3d.testlist | 6 +++ >> tests/v3d_get_bo_offset.c | 78 ++++++++++++++++++++++++++++++++++++++ >> tests/v3d_get_param.c | 80 +++++++++++++++++++++++++++++++++++++++ >> tests/v3d_mmap.c | 55 +++++++++++++++++++++++++++ > > > Do you need a separate directory for v3d or can you use the vc4 > directory for v3d as well? Renamed to 'broadcom-ci' maybe?
Do we really need to introduce the vendor name separate from the driver name? I guess intel_ci makes some sense if it's used by Intel's CI, but these are just the test lists for anyone that happens to use igt for this driver.
signature.asc
Description: PGP signature
_______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
