public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aleksandr V. Piskunov" <aleksandr.v.piskunov@gmail.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: "Aleksandr V. Piskunov" <aleksandr.v.piskunov@gmail.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-media@vger.kernel.org
Subject: Re: xc2028 sound carrier detection
Date: Sat, 26 Sep 2009 00:03:42 +0300	[thread overview]
Message-ID: <20090925210342.GA14181@moon> (raw)
In-Reply-To: <829197380909231427n1fa9374djf01d06f7c1a682c1@mail.gmail.com>

On Wed, Sep 23, 2009 at 05:27:56PM -0400, Devin Heitmueller wrote:
> On Wed, Sep 23, 2009 at 3:28 PM, Aleksandr V. Piskunov
> <aleksandr.v.piskunov@gmail.com> wrote:
> > Mmm, tested that tuner under windows, it autodetects all 3 sound carrier sub-
> > standards instantly: PAL-BG, PAL-DK, PAL-I.
> >
> > In order to test, I connected ancient Panasonic VCR that has a built-in tuner
> > and can output video to RF-OUT on fixed frequency using PAL standard. Sound
> > carrier frequency can be choosen using hardware switch BG, DK or I.
> >
> > So under windows: tuner produces clear audio in BG, DK and I, hardware switch
> > can be toggled on fly, audio never stops, only a few miliseconds of static on
> > switch.
> >
> > Under linux: audio only works if driver is set to use specific audio carrier
> > sub-standard AND same is selected on PVR. (not to mention extremely unreliable
> > PAL-DK detection by cx25843, only works 50% of times, but thats another issue)
> >
> > Either a more generic firmware exists can be uploaded on xc2028.. or several
> > can be uploaded at once. Any xc2028 gurus out there?
> 
> It's possible that perhaps the Windows driver is relying on the
> cx25843 standard detection and then using that to load the appropriate
> firmware on the 3028.
> 
> I can confirm though Mauro's assertion that the 3028 does use
> different firmware depending on the selected audio standard.  You
> might want to try to get a capture of the device under Windows and see
> what firmware gets loaded.

Ok, done a little research, here are results:

1) Best suitable xc2028 firmware for PAL audio is the one that gets chosen 
for PAL-I, to be more precise its
"Firmware 69, type: SCODE FW  MONO HAS IF (0x60008000), IF = 6.00 MHz"
With this firmware loaded, tuner seems to pass everything from +5.5 MHz to
+6.5Mhz straight to cx25843, resulting automatic detection of BG, I and DK audio.
Instant detection on source change, instant playback, same as under windows.
Would be great if more people would try "v4l2-ctl -s pal-i" and give feedback,
especially for stereo sources.

2) Extremely unreliable detection of DK was caused by cx25843 trying to guess
if 6.5MHz carrier is system DK or system L, special register was set to autodetection
which failed half of the times. Will send a patch in a separate mail.

      reply	other threads:[~2009-09-25 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 22:37 xc2028 sound carrier detection Aleksandr V. Piskunov
     [not found] ` <20090921215238.2e189d60@pedra.chehab.org>
2009-09-23 19:28   ` Aleksandr V. Piskunov
2009-09-23 21:27     ` Devin Heitmueller
2009-09-25 21:03       ` Aleksandr V. Piskunov [this message]

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=20090925210342.GA14181@moon \
    --to=aleksandr.v.piskunov@gmail.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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