public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Simon Baxter" <linuxtv@nzbaxters.com>
To: <linux-dvb@linuxtv.org>
Subject: [linux-dvb] 682Mhz problem with TT-1501 driver in v4l-dvb
Date: Tue, 22 Jul 2008 22:25:43 +1200	[thread overview]
Message-ID: <008401c8ebe5$4e09ea90$450011ac@ad.sytec.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3462 bytes --]

Hi - please help!!!!

I have patched the v4l-dvb driver with Sigmund Augdal's changes to support 
C-1501.  I can't get channels to work on all but one frequency - 682Mhz.
Frequencies which work:  578, 586, 594, 602, 610, 626, 634, 642, 666, 674 
Mhz.

I have some channels at 674Mhz and at 682Mhz.  My initial is:
# Initial Testing
# freq sr fec mod
# freq sr fec mod
C 674000000 6900000 AUTO QAM64
C 682000000 6900000 AUTO QAM64


Scanning gives me:
./scan -A 2 test_initial
initial transponder 674000000 6900000 9 3
initial transponder 682000000 6900000 9 3
>>> tune to: 674000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64
0x0000 0x0321: pmt_pid 0x0029 T -- Sky Movies (running, scrambled)
0x0000 0x0322: pmt_pid 0x002a T -- Sky Movies Greats (running, scrambled)
0x0000 0x0323: pmt_pid 0x002b T -- Trackside (running, scrambled)
>>> tune to: 682000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0030
WARNING: filter timeout pid 0x002d
WARNING: filter timeout pid 0x0029
WARNING: filter timeout pid 0x002f
WARNING: filter timeout pid 0x002a

-------------->>  What does this pid timeout mean??



I end up with channels:

Living 
Channel:674000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:1309:1409:809
UKTV:674000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:1310:1410:810
The Cheese:674000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:0:1420:820
[0385]:682000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:0:0:901
[0386]:682000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:0:0:902
[0387]:682000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:1303:1403:903
[0388]:682000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:0:0:904
[0389]:682000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:0:0:905


-------------->>  Has picked up the pids, but missing information??



When I try and czap them, I get:

[root@freddy scan]# czap -c ~/.channels.conf.tmp TV3
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '/root/.channels.conf.tmp'
  2 TV3:578000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:1303:1403:1003
  2 TV3: f 578000000, s 6900000, i 2, fec 9, qam 3, v 0x517, a 0x57b
status 00 | signal 9090 | snr b9b9 | ber 000fffff | unc 00000032 |
status 1f | signal e1e1 | snr f2f2 | ber 000005e8 | unc 000001ec | 
FE_HAS_LOCK
status 1f | signal e1e1 | snr f2f2 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status 1f | signal e1e1 | snr f2f2 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status 1f | signal e1e1 | snr f3f3 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status 1f | signal e1e1 | snr f2f2 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK


but with 682Mhz, I get a lock but loads of errors:

[root@freddy scan]# czap -c ~/.channels.conf.tmp [0385]
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '/root/.channels.conf.tmp'
  1 [0385]:682000000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:0:0:901
  1 [0385]: f 682000000, s 6900000, i 2, fec 9, qam 3, v 0, a 0
status 03 | signal 8f8f | snr b9b9 | ber 000fffff | unc 00000032 |
status 1f | signal cfcf | snr dcdc | ber 000005e8 | unc 000061a7 | 
FE_HAS_LOCK
status 1f | signal cfcf | snr dcdc | ber 000005e8 | unc 000061e8 | 
FE_HAS_LOCK
status 1f | signal cfcf | snr dede | ber 000006c0 | unc 00006234 | 
FE_HAS_LOCK
status 1f | signal cfcf | snr e0e0 | ber 000006a9 | unc 0000627f | 
FE_HAS_LOCK
status 1f | signal cfcf | snr dbdb | ber 000006a5 | unc 000062b6 | 
FE_HAS_LOCK



Any ideas??? 

[-- Attachment #2: c-1501_try2.patch --]
[-- Type: application/octet-stream, Size: 1954 bytes --]

Signed-off-by: Sigmund Augdal <sigmund@snap.tv>
diff -r 6541620a09b7 linux/drivers/media/dvb/ttpci/budget-ci.c
--- a/linux/drivers/media/dvb/ttpci/budget-ci.c	Tue Jun 03 10:32:16 2008 -0300
+++ b/linux/drivers/media/dvb/ttpci/budget-ci.c	Thu Jun 05 11:02:28 2008 +0200
@@ -46,6 +46,8 @@
 #include "lnbp21.h"
 #include "bsbe1.h"
 #include "bsru6.h"
+#include "tda1002x.h"
+#include "tda827x.h"
 
 /*
  * Regarding DEBIADDR_IR:
@@ -1069,6 +1071,16 @@
 
 
 
+static struct tda10023_config tda10023_config = {
+	.demod_address = 0xc,
+	.invert = 0,
+	.xtal = 16000000,
+	.pll_m = 11,
+	.pll_p = 3,
+	.pll_n = 1,
+	.deltaf = 0xA511,
+};
+
 static void frontend_init(struct budget_ci *budget_ci)
 {
 	switch (budget_ci->budget.dev->pci->subsystem_device) {
@@ -1137,6 +1149,20 @@
 			}
 		}
 
+		break;
+	case 0x101a: /* TT Budget-C-1501 (philips tda10023/philips tda8274A) */
+		budget_ci->budget.dvb_frontend =
+			dvb_attach(tda10023_attach, &tda10023_config,
+				   &budget_ci->budget.i2c_adap, 0x48);
+		if (budget_ci->budget.dvb_frontend) {
+			if (dvb_attach(tda827x_attach,
+				       budget_ci->budget.dvb_frontend, 0x61,
+				       &budget_ci->budget.i2c_adap, NULL)
+			    == NULL)
+				printk(KERN_ERR "%s: No tda827x found!\n",
+				       __func__);
+			break;
+		}
 		break;
 	}
 
@@ -1226,6 +1252,7 @@
 MAKE_BUDGET_INFO(ttbt2, "TT-Budget/WinTV-NOVA-T	 PCI", BUDGET_TT);
 MAKE_BUDGET_INFO(ttbtci, "TT-Budget-T-CI PCI", BUDGET_TT);
 MAKE_BUDGET_INFO(ttbcci, "TT-Budget-C-CI PCI", BUDGET_TT);
+MAKE_BUDGET_INFO(ttc1501, "TT-Budget C-1501 PCI", BUDGET_TT);
 
 static struct pci_device_id pci_tbl[] = {
 	MAKE_EXTENSION_PCI(ttbci, 0x13c2, 0x100c),
@@ -1234,6 +1261,7 @@
 	MAKE_EXTENSION_PCI(ttbt2, 0x13c2, 0x1011),
 	MAKE_EXTENSION_PCI(ttbtci, 0x13c2, 0x1012),
 	MAKE_EXTENSION_PCI(ttbs2, 0x13c2, 0x1017),
+	MAKE_EXTENSION_PCI(ttc1501, 0x13c2, 0x101A),
 	{
 	 .vendor = 0,
 	 }

[-- Attachment #3: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

             reply	other threads:[~2008-07-22 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 10:25 Simon Baxter [this message]
2008-07-22 10:40 ` [linux-dvb] 682Mhz problem with TT-1501 driver in v4l-dvb Simon Baxter
2008-07-23 10:53 ` [linux-dvb] ANYONE?? " Simon Baxter
2008-07-25 10:02   ` [linux-dvb] Please - anyone at all?? 682Mhz problem with TT-1501 driver inv4l-dvb Simon Baxter
2008-07-25 13:42     ` Antti Palosaari
2008-07-27 11:24     ` Arthur Konovalov
2008-08-02  4:44       ` Simon Baxter
2008-08-03  9:27         ` [linux-dvb] THINGS ARE LOOKING UP!!682Mhz problem withTT-1501 " Simon Baxter
2008-08-03 11:34           ` SUBHRANIL CHOUDHURY
2008-08-13 17:03           ` SG

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='008401c8ebe5$4e09ea90$450011ac@ad.sytec.com' \
    --to=linuxtv@nzbaxters.com \
    --cc=linux-dvb@linuxtv.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