From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Kuninori Morimoto <morimoto.kuninori@renesas.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] Add interlace support to sh_mobile_ceu_camera.c
Date: Mon, 12 Jul 2010 09:08:49 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1007120900430.7130@axis700.grange> (raw)
In-Reply-To: <uvdtrmtin.wl%morimoto.kuninori@renesas.com>
Hello Morimoto-san
I've got a question to you, regarding your interlaced support
implementation for the CEU: do I understand it right, that the kind of
support you actually have implemented is, that if an interlaced format is
now requested from the CEU, it will interpret incoming data as interlaced
and deinterlace it internally? If this is really the case, then, I think,
it is a wrong way to implement this functionality. If a user requests
interlaced data, it means, (s)he wants it interlaced in memory. Whereas
deinterlacing should happen transparently - if the user requested
progressive data and your source provides interlaced, you can decide to
deinterlace it internally. Or am I misunderstanding your implementation?
Regardless of theoretical correctness - does your patch still work? Have
you been able back then to get CEU to deinterlace data, and when have you
last tested it?
Thanks
Guennadi
---
Guennadi Liakhovetski
next prev parent reply other threads:[~2010-07-12 7:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 0:02 [PATCH] Add interlace support to sh_mobile_ceu_camera.c Kuninori Morimoto
2008-12-12 7:17 ` morimoto.kuninori
2010-07-12 7:08 ` Guennadi Liakhovetski [this message]
2010-07-13 1:16 ` Kuninori Morimoto
2010-07-13 14:35 ` Guennadi Liakhovetski
2010-07-14 0:12 ` Kuninori Morimoto
2010-07-14 2:35 ` hermann pitton
2010-07-14 5:18 ` Kuninori Morimoto
2010-07-15 2:48 ` hermann pitton
2010-07-15 5:37 ` Kuninori Morimoto
2010-07-16 3:25 ` hermann pitton
-- strict thread matches above, loose matches on Subject: below --
2008-12-16 1:41 Kuninori Morimoto
2008-12-16 2:04 ` morimoto.kuninori
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=Pine.LNX.4.64.1007120900430.7130@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=linux-media@vger.kernel.org \
--cc=morimoto.kuninori@renesas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox