Re: using MFC memory to memery encoder, start stream and queue order problem

[Andrzej Hajda <a.hajda@samsung.com>]

Hi Randy,

On 01/10/2014 10:15 AM, randy wrote:

<snip>

>> It won't work, if I do that, after step 7, neither OUPUT nor
>> CAPTURE will poll return in my program. but ./mfc-encode -m
>> /dev/video1 -c h264,header_mode=1 work normally,
> I am sorry, I didn't well test it, if I use ./mfc-encode -m
> /dev/video1 -c h264,header_mode=1 -d 1
> then the size of demo.out is zero,
> but ./mfc-encode -d 1 -m /dev/video1 -c h264 will out a 158 bytes files.
> When duration is 2, with header_mode=1, the output file size is 228
> bytes.Without it, the size is 228 too.
> I wonder whether it is the driver's problem, as I see this in dmesg
> [    0.210000] Failed to declare coherent memory for MFC device (0
> bytes at 0x43000000)
> As the driver is not ready to use in 3.13-rc6 as I reported before, I
> still use the 3.5 from manufacturer.

I am the author of mfc-encode application, it was written for the
mainline kernel 3.8 and later, it should be mentioned in the README.txt
- I will update it.
App will not work correctly with earlier kernels, mainly (but not only)
due to lack of end of stream handling in MFC encoder driver.
If you use vendor kernel I suggest to look at the vendor's capture
apps/libs to check how it uses MFC driver.

Regards
Andrzej