On 10.03.2014 17:36, Hans Verkuil wrote:
On 03/10/2014 04:29 PM, Antti Palosaari wrote:
Moikka Hans!
On 06.03.2014 01:21, Hans Verkuil wrote:
Antti,
Attached is a patch that fixed all but one v4l2-compliance error:
fail: v4l2-test-controls.cpp(295): returned control value o
On 03/10/2014 04:29 PM, Antti Palosaari wrote:
> Moikka Hans!
>
> On 06.03.2014 01:21, Hans Verkuil wrote:
>> Antti,
>>
>> Attached is a patch that fixed all but one v4l2-compliance error:
>>
>> fail: v4l2-test-controls.cpp(295): returned control value
>> out of range
>>
Moikka Hans!
On 06.03.2014 01:21, Hans Verkuil wrote:
Antti,
Attached is a patch that fixed all but one v4l2-compliance error:
fail: v4l2-test-controls.cpp(295): returned control value out
of range
fail: v4l2-test-controls.cpp(357): invalid control 00a2090c
Moikka Hans!
I will look these issues today. Actually I forget to ran whole
v4l2-compliance after I added these controls... I ran it for basic API
and it failed there too in many places, IIRC mostly those were related
to new tuner types.
regards
Antti
On 06.03.2014 01:21, Hans Verkuil wro
Antti,
Attached is a patch that fixed all but one v4l2-compliance error:
fail: v4l2-test-controls.cpp(295): returned control value out
of range
fail: v4l2-test-controls.cpp(357): invalid control 00a2090c
test VIDIOC_G/S_CTRL: FAIL
fail: v4l