Re: [libav-devel] [PATCH 03/13] x86_64: int32_to_float_fmul_scalar sign extend integer length

2015-12-21 Thread James Almer
On 12/9/2015 6:54 PM, Janne Grunau wrote: > --- > libavcodec/x86/fmtconvert.asm | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/libavcodec/x86/fmtconvert.asm b/libavcodec/x86/fmtconvert.asm > index 727daa9..b9a78a5 100644 > --- a/libavcodec/x86/fmtconvert.asm > +++

Re: [libav-devel] [PATCH 1/5] lavu: add a framework for handling hwaccel frames

2015-12-21 Thread Rémi Denis-Courmont
Le 2015-12-20 21:59, Anton Khirnov a écrit : diff --git a/libavutil/hwframe.h b/libavutil/hwframe.h new file mode 100644 index 000..3e33aa5 --- /dev/null +++ b/libavutil/hwframe.h @@ -0,0 +1,97 @@ +/* + * This file is part of Libav. + * + * Libav is free software; you can redistribute it

Re: [libav-devel] [RFC] hwaccel frame handling framework

2015-12-21 Thread Luca Barbato
On 21/12/15 16:32, Anton Khirnov wrote: > One specific point on which I could use some opinions is the specific > API for accessing the data. Conceptually, I can think of the following > possible operations: > 1 copy from hw to ram (conceivably also from hw to hw, but I doubt it > ever really

Re: [libav-devel] [RFC] hwaccel frame handling framework

2015-12-21 Thread Anton Khirnov
One specific point on which I could use some opinions is the specific API for accessing the data. Conceptually, I can think of the following possible operations: 1 copy from hw to ram (conceivably also from hw to hw, but I doubt it ever really makes sense?) 2 copy from ram to hw 3 map hw to ram

Re: [libav-devel] [PATCH 2/5] hwframe: add a VDPAU implementation

2015-12-21 Thread Rémi Denis-Courmont
Le 2015-12-20 21:59, Anton Khirnov a écrit : diff --git a/libavutil/hwframe_vdpau.c b/libavutil/hwframe_vdpau.c new file mode 100644 index 000..3cbea4e3 --- /dev/null +++ b/libavutil/hwframe_vdpau.c @@ -0,0 +1,264 @@ +/* + * This file is part of Libav. + * + * Libav is free software; you can