Re: Zoran Linux driver 64-bit support

Hi.

On Mon, Jun 13, 2011 at 1:48 AM, Bernhard Praschinger
<[email protected]> wrote:
>>>>> I don't know of any other tool to record from a zoran based car. A
>>>>> patch
>>>>> for lavrec would be really great.
>>>>
>>>> Ok, I'm currently hacking something together just to make it capture
>>>> with a mostly fixed set of parameters. Trying to translate the existing
>>>> lavrec data structures to V4L2 syscalls isn't that easy, because there
>>>> is no one-to-one correspondence for the whole decimation settings and
>>>> many parameters for input and norm selection also look quite different.
>>>
>>> Maybe Ronald can give you any hints for that task.
>>
>> With the attached version of liblavrec I already managed to capture
>> hardware-encoded MJPEG video, using the V4L2 interface only, on 2.6.38
>> with my patch and 64-bits. It's still a lot of work, because I had to
>> disable signal auto-detection as well as the whole software encoding and
>> it doesn't properly support any decimation.
>
> I did test your version of liblavrec. And it works.
> The video is recorded properly.
>
> I still have problems recording the audio stream but that might be related
> to the built in soundcard. I was not able to record with arecord either. I
> need to dig there a to find out how to choose the proper input recording
> seems to work. But I don't get any sound.
>
> Is the current version of driver and liblavrec supposed to output the videos
> to the screen with mplayer, and be able to record at the same time ?
>
>> It seems that there is also a problem with signal detection in the
>> driver with the V4L2 interface, because it always had the NO SIGNAL flag
>> set, no matter if the attached source actually produced any output or
>> not. The color detection seemed to work though, because the bit toggled
>> sometimes when I used an entirely grey picture for testing.

The v4l1 used several MJPEG-specific extensions that we came up with
ourselves, which is why it used the card's features so well. I have
tried to map everything to standardized v4l2 calls long time ago, but
may have missed details. I think anyone interested in this should
basically assume that some extensions may not be mapped at all, and
may need work in the driver.

It shouldn't be hard, the code is in there, it worked for v4l1, it
just needs proper v4l2-API-mapping.

Ronald

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev