On Tue, Sep 19, 2017 at 2:15 PM, Mark Thompson wrote:
> On 19/09/17 09:51, Hendrik Leppkes wrote:
>> VP9SharedContext needs to be the first member so its properties can be
>> safely accessed from hardware accelerators, without the need to share
>> the full VP9Context.
>> ---
>> libavcodec/vp9dec.
On Tue, Sep 19, 2017 at 2:27 PM, Ronald S. Bultje wrote:
> Hi,
>
> On Tue, Sep 19, 2017 at 4:51 AM, Hendrik Leppkes
> wrote:
>
>> VP9SharedContext needs to be the first member so its properties can be
>> safely accessed from hardware accelerators, without the need to share
>> the full VP9Context.
Hi,
On Tue, Sep 19, 2017 at 4:51 AM, Hendrik Leppkes
wrote:
> VP9SharedContext needs to be the first member so its properties can be
> safely accessed from hardware accelerators, without the need to share
> the full VP9Context.
> ---
> libavcodec/vp9dec.h | 2 +-
> 1 file changed, 1 insertion(+
On 19/09/17 09:51, Hendrik Leppkes wrote:
> VP9SharedContext needs to be the first member so its properties can be
> safely accessed from hardware accelerators, without the need to share
> the full VP9Context.
> ---
> libavcodec/vp9dec.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
VP9SharedContext needs to be the first member so its properties can be
safely accessed from hardware accelerators, without the need to share
the full VP9Context.
---
libavcodec/vp9dec.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/vp9dec.h b/libavcodec/vp9dec.h
in
