From: Antti Palosaari <crope@iki.fi>
To: Hamish Moffatt <hamish@cloud.net.au>, linux-media@vger.kernel.org
Subject: Re: problem with second tuner on Leadtek DTV dongle dual
Date: Sat, 27 Sep 2014 05:02:14 +0300 [thread overview]
Message-ID: <54261AA6.10800@iki.fi> (raw)
In-Reply-To: <54261797.7080509@cloud.net.au>
On 09/27/2014 04:49 AM, Hamish Moffatt wrote:
> On 26/09/14 04:44, Antti Palosaari wrote:
>> Moikka
>> Performance issues are fixed recently (at least I hope so), but it
>> will took some time in order to get fixes in stable. Unfortunately I
>> don't have any IT9135 BX (ver 2 chip) dual device to test like yours...
>>
>> Could you install that kernel tree:
>> http://git.linuxtv.org/cgit.cgi/media_tree.git/log/?h=devel-3.17-rc6
>> and firmwares from there:
>> http://palosaari.fi/linux/v4l-dvb/firmware/IT9135/ITE_3.25.0.0/
>>
>
> OK I have
> http://git.linuxtv.org/cgit.cgi/media_tree.git/log/?h=devel-3.17-rc6
> running now (reporting itself as 3.17-rc5), with the 3.40.1.0 firmware
> from your site.
>
> Both tuners work for all stations, except that the first tuning attempt
> on each tuner simply doesn't lock. Doesn't seem to matter what I tune to.
:/ Sounds like a something is not initialized in a correct order. I
suspect it is it913x tuner driver. But without a hardware, I cannot do
much for it. So let it be.
Good to hear that it works that better, even first tune will fail. It is
though annoying as you will need to close app and then try again. I
suspect it needs "power on - sleep - power on" in order to init all
properly.
>
> [Unplug & replug device]
>
> [11:44AM] hamish@quokka:~ $ tzap -a3 'ABC'
> using '/dev/dvb/adapter3/frontend0' and '/dev/dvb/adapter3/demux0'
> reading channels from file '/home/hamish/.tzap/channels.conf'
> tuning to 226500000 Hz
> video pid 0x0200, audio pid 0x028a
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 07 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 07 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0032 | ber 00000000 | unc 00000000 |
> status 07 | signal ffff | snr 0032 | ber 00000000 | unc 00000000 |
> ^C
> [11:44AM] hamish@quokka:~ $ tzap -a3 'ABC'
> using '/dev/dvb/adapter3/frontend0' and '/dev/dvb/adapter3/demux0'
> reading channels from file '/home/hamish/.tzap/channels.conf'
> tuning to 226500000 Hz
> video pid 0x0200, audio pid 0x028a
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 1f | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> FE_HAS_LOCK
> status 1f | signal ffff | snr 0122 | ber 00000000 | unc 00000000 |
> FE_HAS_LOCK
> status 1f | signal ffff | snr 0122 | ber 00000000 | unc 00000000 |
> FE_HAS_LOCK
> ^C
> [11:44AM] hamish@quokka:~ $ tzap -a2 'ABC'
> using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0'
> reading channels from file '/home/hamish/.tzap/channels.conf'
> tuning to 226500000 Hz
> video pid 0x0200, audio pid 0x028a
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 07 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 07 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0032 | ber 00000000 | unc 00000000 |
> status 07 | signal ffff | snr 0032 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0032 | ber 00000000 | unc 00000000 |
> status 07 | signal ffff | snr 0032 | ber 00000000 | unc 00000000 |
> status 00 | signal ffff | snr 0028 | ber 00000000 | unc 00000000 |
> status 07 | signal ffff | snr 0028 | ber 00000000 | unc 00000000 |
> ^C
> [11:45AM] hamish@quokka:~ $ tzap -a2 'ABC'
> using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0'
> reading channels from file '/home/hamish/.tzap/channels.conf'
> tuning to 226500000 Hz
> video pid 0x0200, audio pid 0x028a
> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> status 1f | signal ffff | snr 0000 | ber 00000000 | unc 00000000 |
> FE_HAS_LOCK
> status 1f | signal ffff | snr 0122 | ber 0009a140 | unc 00002685 |
> FE_HAS_LOCK
> ^C
>
>
> I left it trying to tune for minutes, and occasionally it would get a
> lock for one sample but then lose it again for the next.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2014-09-27 2:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 12:13 problem with second tuner on Leadtek DTV dongle dual Hamish Moffatt
2014-09-25 18:44 ` Antti Palosaari
2014-09-27 1:49 ` Hamish Moffatt
2014-09-27 2:02 ` Antti Palosaari [this message]
2014-09-27 3:32 ` Hamish Moffatt
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=54261AA6.10800@iki.fi \
--to=crope@iki.fi \
--cc=hamish@cloud.net.au \
--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 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.