Re: [Mesa-dev] [PATCH] intel: decoder: unify MI_BB_START field naming

2018-08-28 Thread Lionel Landwerlin
Yes, I think so. You asked on another commit too, both are related and this depends on other commits from Jason. Here is a list in order of cherry picking : commit f430a37fa75f534c3a114b0ec546fa14f05f5da1 Author: Lionel Landwerlin Date:   Tue Aug 14 11:22:12 2018 +0100     intel: decoder:

Re: [Mesa-dev] [PATCH] intel: decoder: unify MI_BB_START field naming

2018-08-27 Thread Andres Gomez
Lionel, should we also include this in the stable queues ? On Tue, 2018-08-14 at 11:26 +0100, Lionel Landwerlin wrote: > The batch decoder looks for a field with a particular name to decide > whether an MI_BB_START leads into a second batch buffer level. Because > the names are different between

Re: [Mesa-dev] [PATCH] intel: decoder: unify MI_BB_START field naming

2018-08-15 Thread Jason Ekstrand
I think I have a similar patch laying around in my 2nd level batch buffer branch. :) Reviewed-by: Jason Ekstrand On Tue, Aug 14, 2018 at 5:26 AM Lionel Landwerlin < lionel.g.landwer...@intel.com> wrote: > The batch decoder looks for a field with a particular name to decide > whether an

[Mesa-dev] [PATCH] intel: decoder: unify MI_BB_START field naming

2018-08-14 Thread Lionel Landwerlin
The batch decoder looks for a field with a particular name to decide whether an MI_BB_START leads into a second batch buffer level. Because the names are different between Gen7.5/8 and the newer generation we fail that test and keep on reading (invalid) instructions. Signed-off-by: Lionel