[Intel-gfx] [PATCH i-g-t 4/4] igt/v3d_*: Add new tests for the V3D UABI.
eric at anholt.net
Tue Nov 27 20:46:23 UTC 2018
Petri Latvala <petri.latvala at intel.com> writes:
> On Mon, Nov 26, 2018 at 12:46:46PM -0800, Eric Anholt wrote:
>> Petri Latvala <petri.latvala at 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 <eric at 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.
> Fair enough, I was assuming there's an active CI somewhere that used
> both at the same time.
> Acked-by: Petri Latvala <petri.latvala at intel.com>
Thanks for taking a look at these and acking them!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 832 bytes
Desc: not available
More information about the Intel-gfx