From: Steve Longerbeam <slongerbeam@gmail.com>
To: Jean-Michel Hautbois <jean-michel.hautbois@vodalys.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Robert Schwebel <r.schwebel@pengutronix.de>,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: i.MX6 Video combiner
Date: Wed, 25 Feb 2015 13:44:10 -0800 [thread overview]
Message-ID: <54EE422A.8050408@gmail.com> (raw)
In-Reply-To: <CAL8zT=jNnHp-ngX01Se8cc+LUtRmr4+-NwVbFAY4hZpuKuB4Rg@mail.gmail.com>
On 02/25/2015 11:40 AM, Jean-Michel Hautbois wrote:
> Hi Steve,
>
> 2015-02-25 18:54 GMT+01:00 Steve Longerbeam <slongerbeam@gmail.com>:
>> On 02/25/2015 09:37 AM, Steve Longerbeam wrote:
>>> On 02/25/2015 02:57 AM, Jean-Michel Hautbois wrote:
>>>> Hi all,
>>>>
>>>> I read in the i.MX6 TRM that it can do combining or deinterlacing with VDIC.
>>>> Has it been tested by anyone ?
>>>> Could it be a driver, which would allow to do some simple compositing
>>>> of souces ?
>>>>
>>>> Thanks,
>>>> JM
>>> I've added VDIC support (deinterlace with motion compensation) to the
>>> capture driver, it's in the my media tree clone:
>>>
>>> git@github.com:slongerbeam/mediatree.git, mx6-media-staging
>> it is activated if user sets the motion compensation control to
>> 1 (low motion), 2 (medium motion), or 3 (high motion), for
>> example:
>>
>> # v4l2-ctl --set-ctrl=motion_compensation=2
> Thx for the tip :).
> And in fact, it is "only" deinterlacing, not combining two planes with
> background as specified in the TRM (or did I miss something ?).
Hi JM, yes it is deinterlace only, the combiner in the VDIC is not
being used.
Steve
next prev parent reply other threads:[~2015-02-25 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 10:57 i.MX6 Video combiner Jean-Michel Hautbois
2015-02-25 17:37 ` Steve Longerbeam
2015-02-25 17:54 ` Steve Longerbeam
2015-02-25 19:40 ` Jean-Michel Hautbois
2015-02-25 21:44 ` Steve Longerbeam [this message]
2015-02-25 21:48 ` Jean-Michel Hautbois
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=54EE422A.8050408@gmail.com \
--to=slongerbeam@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=jean-michel.hautbois@vodalys.com \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=r.schwebel@pengutronix.de \
/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.