On Thu, Nov 08, 2018 at 12:57:03PM +0200, andrey simiklit wrote:
> Hello,
>
> Please find my comment below:
>
> On Wed, Nov 7, 2018 at 4:49 PM Toni Lönnberg
> wrote:
>
> > Preliminary work for adding handling of different pipes to gen_decoder.
> > Each
> > instruction needs to have a definition
Hello,
Please find my comment below:
On Wed, Nov 7, 2018 at 4:49 PM Toni Lönnberg
wrote:
> Preliminary work for adding handling of different pipes to gen_decoder.
> Each
> instruction needs to have a definition describing which engine it is meant
> for.
> If left undefined, by default, the inst
Reviewed-by: Lionel Landwerlin
On 07/11/2018 14:49, Toni Lönnberg wrote:
Preliminary work for adding handling of different pipes to gen_decoder. Each
instruction needs to have a definition describing which engine it is meant for.
If left undefined, by default, the instruction is defined for all
Preliminary work for adding handling of different pipes to gen_decoder. Each
instruction needs to have a definition describing which engine it is meant for.
If left undefined, by default, the instruction is defined for all engines.
v2: Changed to use the engine class definitions from UAPI
v3: Cha
