On 08/25/2017 09:03 PM, Paul B Mahol wrote:
Does lavd stuff now depends on lavc?
um yes, v4l2 in/out devices (lavd) do use a common file now present in
lavc (ie: v4l2_fmt.c).
see libavcodec/Makefile:
OBJS-$(CONFIG_V4L2)+= v4l2_fmt.o
OBJS-$(CONFIG_V4L2_M2M)+=
On 8/25/17, Jorge Ramirez wrote:
> On 08/25/2017 02:50 PM, Paul B Mahol wrote:
>> On 8/25/17, Jorge Ramirez-Ortiz wrote:
>>> From: Alexis Ballier
>>>
>>> In preparation to support the integation of the V4L2 API for encoding
>>> and decoding, move v4l2 related files to libavcodec.
>>>
>>> v4l2-co
On 08/25/2017 02:50 PM, Paul B Mahol wrote:
On 8/25/17, Jorge Ramirez-Ortiz wrote:
From: Alexis Ballier
In preparation to support the integation of the V4L2 API for encoding
and decoding, move v4l2 related files to libavcodec.
v4l2-common was renamed to v4l2_fmt for clarity (v4l2-common.h be
On 8/25/17, Jorge Ramirez-Ortiz wrote:
> From: Alexis Ballier
>
> In preparation to support the integation of the V4L2 API for encoding
> and decoding, move v4l2 related files to libavcodec.
>
> v4l2-common was renamed to v4l2_fmt for clarity (v4l2-common.h belongs
> to the V4L2 API)
>
> Signed-o
From: Alexis Ballier
In preparation to support the integation of the V4L2 API for encoding
and decoding, move v4l2 related files to libavcodec.
v4l2-common was renamed to v4l2_fmt for clarity (v4l2-common.h belongs
to the V4L2 API)
Signed-off-by: Alexis Ballier
Reviewed-by: Jorge Ramirez-Ortiz
