All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Hajda <a.hajda@samsung.com>
To: randy <lxr1234@hotmail.com>, Kamil Debski <k.debski@samsung.com>,
	linux-media@vger.kernel.org
Cc: kyungmin.park@samsung.com
Subject: Re: using MFC memory to memery encoder, start stream and queue order problem
Date: Wed, 15 Jan 2014 08:08:53 +0100	[thread overview]
Message-ID: <52D63405.9080604@samsung.com> (raw)
In-Reply-To: <BLU0-SMTP1645A2349311998A104ACB8ADBF0@phx.gbl>

On 01/14/2014 05:50 PM, randy wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 于 2014年01月14日 18:29, Andrzej Hajda 写道:
>> On 01/14/2014 06:17 AM, randy wrote:
>>> Yes, it make encoder work. But sadness ./mfc-encode -m
>>> /dev/video1 -c h264,header_mode=1 -d 1 will still output a zero
>>> demo.out without header-mode or set it to zero will works. What
>>> is the problem?
>> It seems infradead repo is not synchronized with our internal
>> repo. Please apply attached patch.
>>
> No, it has been applied in public repo.
> And my code is in applied version, but it doesn't work.
> Here is the log
> ============================
> mfc codec encoding example application
> Andrzej Hajda <a.hajda@samsung.com>
> Copyright 2012 Samsung Electronics Co., Ltd.
>
> 70.259455868:args.c:parse_args:190: codec: H264
> 70.259635952:args.c:parse_args:187: opt header_mode=1
> mfc.c:mfc_create:85: error: Cannot subscribe EOS event for MFC
This error shows that end-of-stream support is not implemented in the
MFC driver.
> 70.358070659:v4l_dev.c:v4l_enq_buf:226: EOS sent to 3:0, ret=-1
>
Ditto

Are you sure you have used kernel 3.12? Have you compiled the program with
proper kernel-headers?

Regards
Andrzej


  reply	other threads:[~2014-01-15  7:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 11:35 using MFC memory to memery encoder, start stream and queue order problem randy
2014-01-02 12:29 ` Kamil Debski
     [not found]   ` <BLU0-SMTP266BE9BC66B254061740251ADCB0@phx.gbl>
     [not found]     ` <02c801cf07ba$8518f2f0$8f4ad8d0$%debski@samsung.com>
2014-01-02 14:03       ` randy
2014-01-03  8:15       ` randy
2014-01-03  8:15       ` randy
2014-01-03 15:16       ` randy
2014-01-08 14:42         ` Kamil Debski
2014-01-08 15:44           ` randy
     [not found]           ` <52CD725E.5060903@hotmail.com>
2014-01-10  9:15             ` randy
2014-01-10 11:13               ` Andrzej Hajda
2014-01-10 15:23                 ` randy
2014-01-13 10:15                   ` Andrzej Hajda
2014-01-13 11:18                     ` Andrzej Hajda
2014-01-13 15:44                       ` randy
2014-01-13 16:18                         ` Kamil Debski
2014-01-14  5:17                           ` randy
2014-01-14 10:29                             ` Andrzej Hajda
2014-01-14 16:50                               ` randy
2014-01-15  7:08                                 ` Andrzej Hajda [this message]
2014-01-15 15:50                                   ` randy
2014-01-16 12:37                                     ` Andrzej Hajda
2014-01-16 19:30                                       ` randy
2014-01-16 20:10                                       ` randy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52D63405.9080604@samsung.com \
    --to=a.hajda@samsung.com \
    --cc=k.debski@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=lxr1234@hotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.