From: Diorser <diorser@gmx.fr>
To: "Antti Palosaari" <crope@iki.fi>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: AverTV_A918R (af9035-af9033-tda18218) / patch proposal
Date: Wed, 02 Jan 2013 01:23:23 +0100 [thread overview]
Message-ID: <op.wp9co90r4bfdfw@quantal> (raw)
In-Reply-To: <op.wp9b661h4bfdfw@quantal>
Just to compare, this is the same tzap test made on same channel with a
AverTV 007 (saa7134) on a another PC, with same antenna.
It works perfectly.
tzap -r TEST
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '~/.tzap/channels.conf'
tuning to 586167000 Hz
video pid 0x0200, audio pid 0x028a
status 00 | signal b2b2 | snr 2929 | ber 0001fffe | unc 00000000 |
status 1f | signal b2b2 | snr fefe | ber 0000004e | unc ffffffff |
FE_HAS_LOCK
status 1f | signal b2b2 | snr fefe | ber 00000050 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b2b2 | snr fefe | ber 0000005c | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b1b1 | snr fefe | ber 00000054 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b2b2 | snr fefe | ber 0000004e | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b2b2 | snr ffff | ber 00000050 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b1b1 | snr ffff | ber 00000052 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b2b2 | snr ffff | ber 00000050 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b1b1 | snr ffff | ber 0000004a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b1b1 | snr ffff | ber 00000050 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b1b1 | snr ffff | ber 0000004e | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b1b1 | snr ffff | ber 00000044 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b2b2 | snr ffff | ber 0000004a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b2b2 | snr ffff | ber 0000004e | unc 00000000 |
FE_HAS_LOCK
next prev parent reply other threads:[~2013-01-02 0:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 21:40 AverTV_A918R (af9035-af9033-tda18218) / patch proposal Diorser
2013-01-01 22:26 ` Antti Palosaari
[not found] ` <op.wp88epxu4bfdfw@quantal>
2013-01-01 23:09 ` Diorser
2013-01-01 23:32 ` Antti Palosaari
2013-01-02 0:12 ` Diorser
2013-01-02 0:17 ` Antti Palosaari
2013-01-03 21:24 ` Diorser
2013-01-03 21:45 ` Antti Palosaari
2013-01-02 0:23 ` Diorser [this message]
2013-04-09 14:46 ` Diorser
2013-04-09 18:33 ` Antti Palosaari
2013-04-09 18:58 ` Diorser
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=op.wp9co90r4bfdfw@quantal \
--to=diorser@gmx.fr \
--cc=crope@iki.fi \
--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;
as well as URLs for NNTP newsgroup(s).