From: "Janusz Uzycki" <janusz.uzycki@elproma.com.pl>
To: "Guennadi Liakhovetski" <g.liakhovetski@gmx.de>
Cc: <linux-media@vger.kernel.org>
Subject: SH7724, VOU, PAL mode
Date: Mon, 4 Jun 2012 19:32:05 +0200 [thread overview]
Message-ID: <CEA83F28AF7C47E7B83AE1DBFFBC8514@laptop2> (raw)
In-Reply-To: Pine.LNX.4.64.1102081427500.1393@axis700.grange
Hi Guennadi.
I am trying to force to proper work CS4954 encoder with sh4.
I want to use sh4 VOU in PAL mode (kernel 3.2.7). Do you have any experience
with AK881x and PAL?
If I set PAL mode (v4l2-ctl -s) VOUCR::MD is still configured for NTSC. I
noticed that VOU is limited to NTSC resolution: "Maximum destination image
size: 720 x 240 per field". And indeed I had to change my encoder settings
to NTSC-M CCIR601 timing 720x480 (PAL synch freq. only) for synced (stable)
color video picture of BAR generated by the encoder (not VOU). On the other
hand VOUDSR register has bit-limit 1024x512 (enough for PAL 768x576
interlaced).
Another method for stable PAL picture (but 768x576) is change both VOUCR::MD
to PAL output mode and set the encoder to PAL mode. Then the green picture
has a bound about 480 line I think.
Unfortunately I can't still manage to work video data from VOU to the
encoder - green picture only. Do you have any test program for video v4l2
output? Does the idea fb->v4l2 output
http://www.spinics.net/lists/linux-fbdev/msg01102.html is alive?
best regards
Janusz Uzycki
ELPROMA
next prev parent reply other threads:[~2012-06-04 17:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1E539FC23CF84B8A91428720570395E0@laptop2>
[not found] ` <Pine.LNX.4.64.1101241720001.17567@axis700.grange>
[not found] ` <AD14536027B946D6B4504D4F43E352A5@laptop2>
[not found] ` <Pine.LNX.4.64.1101262045550.3989@axis700.grange>
2011-01-27 16:21 ` SoC Camera driver and TV decoder Janusz Uzycki
[not found] ` <F95361ABAE1D4A70A10790A798004482@laptop2>
2011-01-27 17:10 ` Guennadi Liakhovetski
2011-01-27 18:15 ` Janusz Uzycki
2011-02-01 13:17 ` Janusz Uzycki
2011-02-01 13:21 ` Guennadi Liakhovetski
2011-02-01 14:29 ` Janusz Uzycki
2011-02-01 14:32 ` Guennadi Liakhovetski
[not found] ` <2F2263A44E0F466F898DD3E2F1D19F12@laptop2>
[not found] ` <Pine.LNX.4.64.1102081427500.1393@axis700.grange>
2012-06-04 17:32 ` Janusz Uzycki [this message]
2012-06-05 15:47 ` SH7724, VOU, PAL mode Guennadi Liakhovetski
2012-06-05 22:37 ` Janusz Uzycki
2012-06-06 14:22 ` Guennadi Liakhovetski
2012-06-06 17:39 ` Janusz Uzycki
2012-06-08 8:43 ` Guennadi Liakhovetski
2012-06-06 1:56 ` Laurent Pinchart
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=CEA83F28AF7C47E7B83AE1DBFFBC8514@laptop2 \
--to=janusz.uzycki@elproma.com.pl \
--cc=g.liakhovetski@gmx.de \
--cc=linux-media@vger.kernel.org \
/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