[linux-dvb] Problems with Hauppauge DEC3000-s

Peter Beutner p.beutner at gmx.net
Fri Apr 7 03:48:04 CEST 2006


Hi

Jens Krehbiel-Gräther schrieb:
[snip]
> I loaded the modules ttusb_dec and dvb_usb with debugging information
> and got the following output in the syslog:
you don't need to load the dvb_usb module btw.

[snip]
> Now when I want to do a channel scan with scan or dvbscan I got the
> following output in syslog:
> 
> Apr  3 19:16:38 NCC-1701A kernel: [4295971.109000] ttusb_dec_send_command
> Apr  3 19:16:38 NCC-1701A kernel: [4295971.109000]
> ttusb_dec_send_command: command: 0xAA 0x94 0x72 0x08 0x00 0xFF 0x00 0x00 0
> xE0 0x10 0x38 0xF1
> Apr  3 19:16:38 NCC-1701A kernel: [4295971.186000]
> ttusb_dec_send_command: result: 0x55 0x94 0x72 0x04 0x00 0x00 0x00 0x00
> Apr  3 19:16:38 NCC-1701A kernel: [4295971.257000] ttusb_dec_send_command
> Apr  3 19:16:38 NCC-1701A kernel: [4295971.257000]
> ttusb_dec_send_command: command: 0xAA 0x95 0x71 0x28 0x00 0x00 0x00 0x01 0
> x00 0xB2 0x8C 0xFC 0x00 0x00 0x00 0x01 0x01 0x4F 0xB1 0x80 0x00 0x00
> 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x94 0xC5 0xF0 0x00 0
> x00 0x00 0x0D 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> Apr  3 19:16:38 NCC-1701A kernel: [4295971.262000]
> ttusb_dec_send_command: result: 0x55 0x95 0x71 0x04 0x00 0x00 0x00 0x00
> Apr  3 19:16:38 NCC-1701A kernel: [4295971.312000] ttusb_dec_send_command
> Apr  3 19:16:38 NCC-1701A kernel: [4295971.312000]
> ttusb_dec_send_command: command: 0xAA 0x96 0x73 0x08 0x00 0x00 0x00 0x00 0
> x00 0x00 0x00 0x00
> Apr  3 19:16:39 NCC-1701A kernel: [4295971.537000]
> ttusb_dec_send_command: result: 0x55 0x96 0x73 0x04 0x00 0x00 0x00 0x00
> Apr  3 19:16:39 NCC-1701A kernel: [4295971.538000]
> ttusbdecfe_read_status: returned unknown value: 0
hmm seems the read_status command works different than with the dec2000t device.
Could you try the attached patch?
 
> So can anyone tell me what I am doing wrong? Mythtv also hangs when I do
> a full channel scan.
> I read in the mailinglist archive that I can use the same firmware as
> the windows-driver, but when I donwload the actual firmware from
> Hauppauge I found only a dll-file and an exe-file in zip archive. How
> can I use them? The firmware I am using at the moment is downloaded from
> linuxtv.org (I think, I forgot where I have it from):
> 
> root at NCC-1701A:~# md5sum dvb-ttusb-dec-3000s.fw
> b013ececea83f4d6d8d2a29ac7c1b448  dvb-ttusb-dec-3000s.fw
> root at NCC-1701A:~#
> 
> When I plugged it into my linux box and the modules where loaded I could
> not change anything with the remove control on the reciever any more.
> Even I could not turn it off! I must pull out the power supply to get it
> back running standalone again!!
dvb-apps includes a program to reset the device to standalone mode.
-------------- next part --------------
diff -r a0c636ae2d1a linux/drivers/media/dvb/ttusb-dec/ttusbdecfe.c
--- a/linux/drivers/media/dvb/ttusb-dec/ttusbdecfe.c	Wed Apr  5 16:39:19 2006 -0300
+++ b/linux/drivers/media/dvb/ttusb-dec/ttusbdecfe.c	Fri Apr  7 01:05:01 2006 +0200
@@ -79,6 +79,14 @@ static int ttusbdecfe_read_status(struct
 	return 0;
 }
 
+static int ttusbdec3000s_read_status(struct dvb_frontend* fe, fe_status_t* status)
+{
+	*status = FE_HAS_SIGNAL | FE_HAS_VITERBI |
+		  FE_HAS_SYNC | FE_HAS_CARRIER | FE_HAS_LOCK;
+
+	return 0;
+}
+
 static int ttusbdecfe_dvbt_set_frontend(struct dvb_frontend* fe, struct dvb_frontend_parameters *p)
 {
 	struct ttusbdecfe_state* state = (struct ttusbdecfe_state*) fe->demodulator_priv;
@@ -277,7 +285,7 @@ static struct dvb_frontend_ops ttusbdecf
 
 	.set_frontend = ttusbdecfe_dvbs_set_frontend,
 
-	.read_status = ttusbdecfe_read_status,
+	.read_status = ttusbdec3000s_read_status,
 
 	.diseqc_send_master_cmd = ttusbdecfe_dvbs_diseqc_send_master_cmd,
 	.set_voltage = ttusbdecfe_dvbs_set_voltage,


More information about the linux-dvb mailing list