Quoting Mika Kuoppala (2017-08-10 12:13:14)
> Chris Wilson writes:
>
> > In the initial selftest, we didn't care what the engine->id was, just
> > that it could uniquely identify it. Later though, we started tracking in
> > the fixed size arrays around the drm_i915_private and so we now require
>
Chris Wilson writes:
> In the initial selftest, we didn't care what the engine->id was, just
> that it could uniquely identify it. Later though, we started tracking in
> the fixed size arrays around the drm_i915_private and so we now require
> it to be appropriate. This becomes an issue when usin
In the initial selftest, we didn't care what the engine->id was, just
that it could uniquely identify it. Later though, we started tracking in
the fixed size arrays around the drm_i915_private and so we now require
it to be appropriate. This becomes an issue when using the standalone
harness of run
