[linux-dvb] [PATHC] Enable XX_AUTO in tzap and zap
The following patch enables the use of XXX_AUTO in channels.conf,
mainly to be used by zap and tzap.
diff -r 92cd5208d2cf lib/libdvbcfg/dvbcfg_zapchannel.c
--- a/lib/libdvbcfg/dvbcfg_zapchannel.c Mon Sep 18 21:27:12 2006 +0100
+++ b/lib/libdvbcfg/dvbcfg_zapchannel.c Sat Oct 28 12:16:04 2006 +
@@ -74,12 +74,13 @@ static const struct dvbcfg_setting dvbcf
};
static const struct dvbcfg_setting dvbcfg_constellation_list[] = {
- { QAM_16, DVBFE_DVBT_CONST_QAM_16 },
- { QAM_32, DVBFE_DVBT_CONST_QAM_32 },
- { QAM_64, DVBFE_DVBT_CONST_QAM_64 },
- { QAM_128, DVBFE_DVBT_CONST_QAM_128 },
- { QAM_256, DVBFE_DVBT_CONST_QAM_256 },
- { QPSK,DVBFE_DVBT_CONST_QPSK},
+ { QAM_16, DVBFE_DVBT_CONST_QAM_16 },
+ { QAM_32, DVBFE_DVBT_CONST_QAM_32 },
+ { QAM_64, DVBFE_DVBT_CONST_QAM_64 },
+ { QAM_128, DVBFE_DVBT_CONST_QAM_128 },
+ { QAM_256, DVBFE_DVBT_CONST_QAM_256 },
+ { QPSK, DVBFE_DVBT_CONST_QPSK},
+ { QAM_AUTO, DVBFE_DVBT_CONST_AUTO},
{ NULL, 0 }
};
diff -r 92cd5208d2cf util/szap/tzap.c
--- a/util/szap/tzap.c Mon Sep 18 21:27:12 2006 +0100
+++ b/util/szap/tzap.c Wed Oct 25 19:51:39 2006 +
@@ -93,14 +93,16 @@ static const Param guard_list [] = {
{GUARD_INTERVAL_1_16, GUARD_INTERVAL_1_16},
{GUARD_INTERVAL_1_32, GUARD_INTERVAL_1_32},
{GUARD_INTERVAL_1_4, GUARD_INTERVAL_1_4},
- {GUARD_INTERVAL_1_8, GUARD_INTERVAL_1_8}
+ {GUARD_INTERVAL_1_8, GUARD_INTERVAL_1_8},
+ {GUARD_INTERVAL_AUTO, GUARD_INTERVAL_AUTO}
};
static const Param hierarchy_list [] = {
{ HIERARCHY_1, HIERARCHY_1 },
{ HIERARCHY_2, HIERARCHY_2 },
{ HIERARCHY_4, HIERARCHY_4 },
- { HIERARCHY_NONE, HIERARCHY_NONE }
+ { HIERARCHY_NONE, HIERARCHY_NONE },
+ { HIERARCHY_AUTO, HIERARCHY_AUTO }
};
static const Param constellation_list [] = {
@@ -109,12 +111,14 @@ static const Param constellation_list []
{ QAM_16, QAM_16 },
{ QAM_256, QAM_256 },
{ QAM_32, QAM_32 },
- { QAM_64, QAM_64 }
+ { QAM_64, QAM_64 },
+ { QAM_AUTO, QAM_AUTO }
};
static const Param transmissionmode_list [] = {
{ TRANSMISSION_MODE_2K, TRANSMISSION_MODE_2K },
{ TRANSMISSION_MODE_8K, TRANSMISSION_MODE_8K },
+ { TRANSMISSION_MODE_AUTO, TRANSMISSION_MODE_AUTO }
};
#define LIST_SIZE(x) sizeof(x)/sizeof(Param)
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Kernel 2.6.18 (FC6) and Nova-T DVB cards
Hi, Are there any known issues with using Hauppauge Nova-T DVB PCI cards on kernel 2.6.18? I've just upgraded to Fedora Core 6 which comes with kernel 2.6.18 (uname -r gives 2.6.18-1.2798.fc6). Unfortunately both my Nova-T PCI cards are non-functional. Below is an extract from my /var/log/messages. The log messages continually repeat until I do rmmod cx88-dvb. Where should I start looking for the cause/solution to this problem? Thanks, -- Graeme Hilton Oct 29 10:05:46 myth kernel: cx88[0]: mpeg risc op code error Oct 29 10:05:46 myth kernel: cx88[0]: mpeg - dma channel status dump Oct 29 10:05:46 myth kernel: cx88[0]: cmds: initial risc: 0x Oct 29 10:05:46 myth kernel: cx88[0]: cmds: cdt base: 0x Oct 29 10:05:46 myth kernel: cx88[0]: cmds: cdt size: 0x Oct 29 10:05:46 myth kernel: cx88[0]: cmds: iq base : 0x Oct 29 10:05:46 myth kernel: cx88[0]: cmds: iq size : 0x Oct 29 10:05:46 myth kernel: cx88[0]: cmds: risc pc : 0x Oct 29 10:05:46 myth kernel: cx88[0]: cmds: iq wr ptr : 0x Oct 29 10:05:46 myth kernel: cx88[0]: cmds: iq rd ptr : 0x Oct 29 10:05:46 myth kernel: cx88[0]: cmds: cdt current : 0x Oct 29 10:05:46 myth kernel: cx88[0]: cmds: pci target : 0x Oct 29 10:05:46 myth kernel: cx88[0]: cmds: line / byte : 0x Oct 29 10:05:46 myth kernel: cx88[0]: risc0: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:46 myth kernel: cx88[0]: risc1: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:46 myth kernel: cx88[0]: risc2: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:46 myth kernel: cx88[0]: risc3: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:46 myth kernel: cx88[0]: iq 0: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:46 myth kernel: cx88[0]: iq 1: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:46 myth kernel: cx88[0]: iq 2: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:46 myth kernel: cx88[0]: iq 3: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:46 myth kernel: cx88[0]: iq 4: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: iq 5: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: iq 6: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: iq 7: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: iq 8: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: iq 9: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: iq a: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: iq b: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: iq c: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: iq d: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: iq e: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: iq f: 0x [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] Oct 29 10:05:47 myth kernel: cx88[0]: fifo: 0x00186400 - 0x187400 Oct 29 10:05:47 myth kernel: cx88[0]: ctrl: 0x001807c0 - 0x180820 Oct 29 10:05:47 myth kernel: cx88[0]: ptr1_reg: 0x Oct 29 10:05:47 myth kernel: cx88[0]: ptr2_reg: 0x Oct 29 10:05:47 myth kernel: cx88[0]: cnt1_reg: 0x Oct 29 10:05:47 myth kernel: cx88[0]: cnt2_reg: 0x Oct 29 10:05:47 myth kernel: cx88_wakeup: 0 buffers handled (should be 1) Oct 29 10:05:47 myth kernel: cx88[0]: mpeg risc op code error Oct 29 10:05:47 myth kernel: cx88[0]: mpeg - dma channel status dump Oct 29 10:05:47 myth kernel: cx88[0]: cmds: initial risc: 0x Oct 29 10:05:47 myth kernel: cx88[0]: cmds: cdt base: 0x Oct 29 10:05:47 myth kernel: cx88[0]: cmds: cdt
Re: [linux-dvb] Another patch for hvr1110
tomlohave a écrit :
[EMAIL PROTECTED] a écrit :
[EMAIL PROTECTED] a écrit :
-Original Message-
Date: Fri, 27 Oct 2006 09:08:38 +0200
Subject: [linux-dvb] HVR1110, no signal lock on tda8290
From: tomlohave [EMAIL PROTECTED]
To: linux-dvb@linuxtv.org
Hi,
After some researchs, it seems that tuner on hvr110 is a Philips
8275A.
with the app Productinfo provide by Hauppauge :
Begin :
Model 67019 Rev. B1B4
Serial #XX
Tuner Model/Formats: Philips 8275A // (MN/BG/I/DK/LL') / DVB-T (FM)
Tuner Audio: Stereo (SAA7131)
Video Formats: NTSC ( M ) PAL ( B G H I D K M N NCOMBO ) SECAM ( L L' )
Audio Outputs: None
External Inputs: 2
S-Video Inputs: 2
Teletext:
Radio: FM
Decoder: SAA7131
IR: Blaster
MAC Address: 00-0D-FE-0C-E8-F1
EEprom Contents:
84 09 00 04 20 77 00 40 f0 1a 0c f0
73 05 29 00
84 08 00 06 cb 05 01 00 94 18 89
72 07 70
73 09 23 5f
73 0a fc 72
72 0b 2f
72 0e 01
72 0f 03
72 10 01
72 11 ff
79 58
end.
But i have no lock with this settings :
snip
I don't have the patch here, but:
- If you live in france, you need to set the option secam=l
well, it's already done, here why i do :
modprobe -r tuner saa7134-alsa saa7134-dvb saa7134 modprobe tuner
secam=l debug=1 modprobe saa7134 i2c_debug=1 gpio_tracking=1
core_debug=1 irq_debug=1
- For this card, you need some GPIO settings to get the AGC
routed correctly.
for FM Radio, you typically need GPIO21 of the SAA7131 and
for DVB-T it typically is GPIO 1 of the TDA10046.
Somebody reported that the card works with the settings
for the Pinnacle 310i, so you might steal the code fragments
from there.
Already done, my configuration is based on the 310i.
Today i 've got analogic tv but without sound, tnt is ok, and no radio
(why ?)
Need more work.
Sound on analogic tv is ok, (mplayer problem)
Sorry for the noise !
so :
TNT ok
Analogic TV : OK
Capture device : not tested
Remote control : Nothing works (perhaps ...)
Radio : not tested
Radio is Ok
Bye, Bye
Well, that's all for today !
Good luck
Hartmut
Thanks :)
Tom
Seulement dans v4l-dvb-modif/linux/drivers/media/video/saa7134:
hvr1110.diff
diff -ur v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c
v4l-dvb-modif/linux/drivers/media/video/saa7134/saa7134-cards.c
--- v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c
2006-10-22 16:12:24.0 +0200
+++
v4l-dvb-modif/linux/drivers/media/video/saa7134/saa7134-cards.c
2006-10-28 11:15:02.0 +0200
@@ -3098,6 +3098,39 @@
.gpio = 0x020,
},
},
+[SAA7134_BOARD_HAUPPAUGE_HVR1110] = {
+.name = Hauppauge WinTV-HVR1110 DVB-T/Hybrid,
+.audio_clock= 0x00187de7,
+.tuner_type = TUNER_PHILIPS_TDA8290,
+.radio_type = UNSET,
+.tuner_addr = ADDR_UNSET,
+.radio_addr = ADDR_UNSET,
+.mpeg = SAA7134_MPEG_DVB,
+.gpiomask = 0x00020,
+.inputs = {{
+.name = name_tv,
+.vmux = 1,
+.amux = TV,
+.tv = 1,
+},{
+.name = name_comp1,
+.vmux = 2,
+.amux = LINE2,
+},{
+.name = name_comp2,
+.vmux = 0,
+.amux = LINE2,
+},{
+.name = name_svideo,
+.vmux = 8,
+.amux = LINE2,
+}},
+.radio = {
+.name = name_radio,
+.amux = TV,
+.gpio = 0x020,
+},
+},
[SAA7134_BOARD_AVERMEDIA_STUDIO_507] = {
/* Mikhail Fedotov [EMAIL PROTECTED] */
.name = Avermedia AVerTV Studio 507,
@@ -3758,6 +3791,12 @@
},{
.vendor = PCI_VENDOR_ID_PHILIPS,
.device = PCI_DEVICE_ID_PHILIPS_SAA7133,
+.subvendor= 0x0070,
+.subdevice= 0x6701,
+.driver_data = SAA7134_BOARD_HAUPPAUGE_HVR1110,
+},{
+.vendor = PCI_VENDOR_ID_PHILIPS,
+.device = PCI_DEVICE_ID_PHILIPS_SAA7133,
.subvendor= 0x1461, /* Avermedia Technologies Inc */
.subdevice= 0x9715,
.driver_data = SAA7134_BOARD_AVERMEDIA_STUDIO_507,
@@ -3909,6 +3948,7 @@
case SAA7134_BOARD_FLYDVBT_LR301:
case SAA7134_BOARD_FLYDVBTDUO:
case SAA7134_BOARD_PROTEUS_2309:
+case SAA7134_BOARD_HAUPPAUGE_HVR1110:
dev-has_remote = SAA7134_REMOTE_GPIO;
break;
case SAA7134_BOARD_FLYDVBS_LR300:
@@ -4100,6 +4140,7 @@
break;
case SAA7134_BOARD_PHILIPS_TIGER:
case SAA7134_BOARD_PINNACLE_PCTV_310i:
+case SAA7134_BOARD_HAUPPAUGE_HVR1110:
case SAA7134_BOARD_TEVION_DVBT_220RF:
case SAA7134_BOARD_ASUSTeK_P7131_DUAL:
case SAA7134_BOARD_MEDION_MD8800_QUADRO:
Seulement dans v4l-dvb-modif/linux/drivers/media/video/saa7134:
saa7134-cards.c~
diff -ur v4l-dvb/linux/drivers/media/video/saa7134/saa7134-dvb.c
[linux-dvb] Problem (was: DiB7000M-driver released (Nova-T Stick, AverMedia and others))
Hi, I've just tried Partick's latest DiB7000M driver (via hg clone http://linuxtv.org/hg/~pb/v4l-dvb) on a linux 2.6.16 kernel and it can't detect a frontend. I get: usb 1-8: new high speed USB device using ehci_hcd and address 12 usb 1-8: configuration #1 chosen from 1 choice dib0700: loaded with support for 2 different device-types dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw' dib0700: firmware started successfully. dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-T Stick). DiB7000P:-D- DiB7000PC not detected DiB7000M:i2c read error on 896 DiB7000M:-E- DiB7000M: wrong Vendor ID (read=0x5388) dvb-usb: no frontend was attached by 'Hauppauge Nova-T Stick' dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected. usbcore: registered new driver dvb_usb_dib0700 This is with a brand new Hauppauge WinTV NOVA-T stick. Anybody got any ideas? Thanks Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: nova-t 500 remote status?
On Fri Oct 27, 2006 at 05:18:00PM +0100, Torgeir Veimo wrote: Any update on this? Is the hardware spec for the remote input available for this card? I've been trying to get this working, but with absolutely no success :( I've done a snoop on the device under Windows (attached) but this hasn't helped me at all - it looks like the USB endpoint is in interrupt mode there, whereas it appears to be in bulk mode under Linux. The device IDs also look to change under Windows (after the firmware is loaded), which is even more confusing. Anyone got any ideas? I've got a system set aside for testing this so I'm quite happy to try anything out. Cheers, Robin -- ___ ( ' } | Robin Hill [EMAIL PROTECTED] | / / ) | Little Jim says | // !! | He fallen in de water !! | [0 ms] UsbSnoop compiled on Jan 18 2003 22:41:32 loading [0 ms] UsbSnoop - DriverEntry(f7bf9c40) : Windows NT WDM version 1.32 [85121 ms] UsbSnoop - AddDevice(f7bf9f50) : DriverObject 8655e340, pdo 865b9c10 [85121 ms] UsbSnoop - DispatchAny(f7bf7610) : IRP_MJ_PNP (0x0018) [85121 ms] UsbSnoop - MyDispatchPNP(f7bf9ee0) : IRP_MJ_PNP (0x0018) [85121 ms] UsbSnoop - DispatchAny(f7bf7610) : IRP_MJ_PNP (IRP_MN_QUERY_RESOURCE_REQUIREMENTS) [85121 ms] UsbSnoop - MyDispatchPNP(f7bf9ee0) : IRP_MJ_PNP (IRP_MN_QUERY_RESOURCE_REQUIREMENTS) [85121 ms] UsbSnoop - DispatchAny(f7bf7610) : IRP_MJ_PNP (IRP_MN_FILTER_RESOURCE_REQUIREMENTS) [85121 ms] UsbSnoop - MyDispatchPNP(f7bf9ee0) : IRP_MJ_PNP (IRP_MN_FILTER_RESOURCE_REQUIREMENTS) [85121 ms] UsbSnoop - MyDispatchPNP(f7bf9ee0) : IRP_MJ_PNP (IRP_MN_QUERY_CAPABILITIES) [85121 ms] UsbSnoop - DispatchAny(f7bf7610) : IRP_MJ_PNP (IRP_MN_START_DEVICE) [85121 ms] UsbSnoop - MyDispatchPNP(f7bf9ee0) : IRP_MJ_PNP (IRP_MN_START_DEVICE) [85121 ms] UsbSnoop - DispatchAny(f7bf7610) : IRP_MJ_INTERNAL_DEVICE_CONTROL [85121 ms] UsbSnoop - MyDispatchInternalIOCTL(f7bf8e80) : fdo=865b9c10, Irp=85b64360, IRQL=0 [85121 ms]URB 1 going down -- URB_FUNCTION_GET_DESCRIPTOR_FROM_DEVICE: TransferBufferLength = 0022 TransferBuffer = 85d27534 TransferBufferMDL= Index= DescriptorType = 0002 (USB_CONFIGURATION_DESCRIPTOR_TYPE) LanguageId = [85121 ms] UsbSnoop - MyInternalIOCTLCompletion(f7bf8db0) : fido=, Irp=85b64360, Context=85ea0ed0, IRQL=0 [85121 ms]URB 1 coming back -- URB_FUNCTION_GET_DESCRIPTOR_FROM_DEVICE: TransferBufferLength = 0022 TransferBuffer = 85d27534 TransferBufferMDL= : 09 02 22 00 01 01 00 80 fa 09 04 01 00 01 ff ff 0010: ff 00 09 21 11 01 00 01 22 2f 00 07 05 81 03 40 0020: 00 0c Index= DescriptorType = 0002 (USB_CONFIGURATION_DESCRIPTOR_TYPE) LanguageId = [85121 ms] UsbSnoop - DispatchAny(f7bf7610) : IRP_MJ_INTERNAL_DEVICE_CONTROL [85121 ms] UsbSnoop - MyDispatchInternalIOCTL(f7bf8e80) : fdo=865b9c10, Irp=85b64360, IRQL=0 [85121 ms]URB 2 going down -- URB_FUNCTION_SELECT_CONFIGURATION: ConfigurationDescriptor = 0x85d27534 (configure) ConfigurationDescriptor : bLength = 9 ConfigurationDescriptor : bDescriptorType = 0x0002 ConfigurationDescriptor : wTotalLength= 0x0022 ConfigurationDescriptor : bNumInterfaces = 0x0001 ConfigurationDescriptor : bConfigurationValue = 0x0001 ConfigurationDescriptor : iConfiguration = 0x ConfigurationDescriptor : bmAttributes= 0x0080 ConfigurationDescriptor : MaxPower= 0x00fa ConfigurationHandle = 0x Interface[0]: Length= 36 Interface[0]: InterfaceNumber = 1 Interface[0]: AlternateSetting = 0 [85121 ms] UsbSnoop - MyInternalIOCTLCompletion(f7bf8db0) : fido=, Irp=85b64360, Context=85efbaf8, IRQL=0 [85121 ms]URB 2 coming back -- URB_FUNCTION_SELECT_CONFIGURATION: ConfigurationDescriptor = 0x85d27534 (configure) ConfigurationDescriptor : bLength = 9 ConfigurationDescriptor : bDescriptorType = 0x0002 ConfigurationDescriptor : wTotalLength= 0x0022 ConfigurationDescriptor : bNumInterfaces = 0x0001 ConfigurationDescriptor : bConfigurationValue = 0x0001 ConfigurationDescriptor : iConfiguration = 0x ConfigurationDescriptor : bmAttributes= 0x0080 ConfigurationDescriptor : MaxPower= 0x00fa ConfigurationHandle = 0x865e2468 Interface[0]: Length= 36 Interface[0]: InterfaceNumber = 1 Interface[0]: AlternateSetting = 0 Interface[0]: Class = 0x00ff Interface[0]: SubClass = 0x00ff Interface[0]: Protocol = 0x00ff Interface[0]: InterfaceHandle = 0x86614ad0 Interface[0]: NumberOfPipes = 1 Interface[0]: Pipes[0] :
Re: [linux-dvb] Another patch for hvr1110
Hi, Tom [EMAIL PROTECTED] wrote: Hartmut Hackmann a écrit : Hi. Tom snip TNT ok Analogic TV : OK Capture device : not tested Remote control : Nothing works (perhaps ...) Radio : not tested Radio is Ok Bye, Bye Well, that's all for today ! Good luck Hartmut Thanks :) Tom So you have the board fully working now? I am in doubt about this: +case SAA7134_BOARD_HAUPPAUGE_HVR1110: +ir_codes = ir_codes_hauppauge_new; +//ir_type = IR_TYPE_RC5; +mask_keycode = 0; +polling = 50; // ms +break; No, there is no remote control. Nothing with regspy about gpio when i press a button under windows so it's not for today. I search ... need test about input device too. So to summarize : tv : ok tnt : ok radio : ok input device : not tested. remote control : nothing. Even with tv working, i have the same logs about device not locked, so is there something wrong ? Logs are here : http://perso.wanadoo.fr/tomlohave/log-with-i2c_debug=1.log Thanks. if mask_keycode applies to the complete GPIO port (not sure in this case), this cannot be right since part of this port is used for the DVB transport stream. Can you please cross check this? Also i must say that i lost sync. After you checked, can you please resend your patch (maybe to me personally) so that i can integrate it? Hartmut Tom. The not locked messages are ok. Right after initialization, the tner driver tunes to 400MHz, to get the tuner into a legal state. If there is no signal, the tda8290 will report no lock. Best regards Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500 tuning problems
On Sun, 2006-10-29 at 20:18 +, Torgeir Veimo wrote: On 29 Oct 2006, at 16:09, Patrick Boettcher wrote: Hi Torgeir, On Sat, 28 Oct 2006, Torgeir Veimo wrote: On 28 Oct 2006, at 00:35, Torgeir Veimo wrote: Am not sure where to start looking. I've included my dmesg output below; using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 52983 Hz video pid 0x, audio pid 0x01b2 status 01 | signal 7abf | snr | ber 001f | unc | status 01 | signal 7aab | snr | ber 001f | unc | status 01 | signal 7abe | snr | ber 001f | unc | status 01 | signal 7ac8 | snr | ber 001f | unc | Can you please send your channels.conf-line for this channel? Well, there's something weird going on with the signal I'm receiving, so it might be related to that. I'd expect to find a BBC transponder at frequency 50580, but it's actually at frequency 506000. I have to configure VDR to not add new transponders, as when I use the channel.conf file eg from the w_scan output below, it tries to retune to 5058333, and I loose the picture. I guess it might be related to that I'm living in a block where I get the signal from the socket in the wall, and there might be some kind of reamplification of the tv signal. I'm just not knowledgeable about dvb-t standards to understand what's going on. Before I moved into this block, I used to have (using a roof arial) in my VDR channels.conf eg. BBC ONE;BBC:50580:C34D34M16B8T2G32Y0:T:27500:600:601=eng,602=eng: 0:0:4164:9018:4100:0 Now I have to use BBC ONE:506000:I999B8C999D999M999T999G999Y999:T: 27500:600:601,602:0:0:4164:0:0:0 Maybe someone can explain the difference between the numbers 506000 and 50580? The former seems to be just a rounding of the latter, but there's a digit too little.. The transmitter frequency used by any given transmitter is based on a channel number and an offset. The offset is -167kHz, zero or +167kHz. This is the difference that you see in the numbers. The two links below give the channel numbers and offsets of every freeview transmitter in the UK: http://www.ofcom.org.uk/static/reception_advice/index.asp.html http://www.ofcom.org.uk/static/reception_advice/dtt_pocket_guide_2-8.pdf To convert the channel number into a frequency, first calculate 306 + 8*N MHz, where N is the channel number. Then add or subtract 167 kHz depending on the + or - in the tables above. e.g. Crystal palace BBC(Multiplex 1) is show as 25 - 306 + 8 * 25 = 506MHz = 506000kHz Apply the - offset: 506000 - 167 = 505833kHz So the frequency line for the Crystal palace transmitter is 505833. It would seem the transmitter that you have now moved to is on channel 25 with no offset. The re-amplification should make no difference. I suspect that the aerial might be taking the signal from a different transmitter to your old one. Jon ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500 tuning problems
On 29 Oct 2006, at 22:21, Jon Burgess wrote: To convert the channel number into a frequency, first calculate 306 + 8*N MHz, where N is the channel number. Then add or subtract 167 kHz depending on the + or - in the tables above. e.g. Crystal palace BBC(Multiplex 1) is show as 25 - 306 + 8 * 25 = 506MHz = 506000kHz Apply the - offset: 506000 - 167 = 505833kHz So the frequency line for the Crystal palace transmitter is 505833. It would seem the transmitter that you have now moved to is on channel 25 with no offset. The re-amplification should make no difference. I suspect that the aerial might be taking the signal from a different transmitter to your old one. Ok, it makes sense with your explanation, but I can't understand what transmitter that would be. I was previously as postcode N16, now I'm at N7, which is less than three miles away, and the webpage you gave link to says there's no other transmitter (in London) sending on channel 25. Can it be that the signal is coming from a cable provider? It seems both xawtv and VDR tries to retune with the offset applied, resulting in lost signal? Is this per standard or are they doing something wrong? My freeview box manages to tune correctly. At least I can turn this off in VDR by turning off add transponders. Could there be a problem in the nova-t 500 driver in that it doesn't allow tuning without offset? -- Torgeir Veimo [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [PATCH] lgdt330x: SNR and signal strength reporting
I'm posting this to the list for final review before requesting merge into
master.
lgdt330x: SNR and signal strength reporting
Update the SNR calculations to use the new dvb_math log function, and add
SNR calculations for all supported modulations for both lg dt3302 and dt3303.
The QAM equations don't appear in the dt3302 datasheet, so the ones from the
dt3303 datasheet were used.
SNR returned is the actual value in dB as 8.8 fixed point.
Reporting of real signal strength isn't supported, so rather than return 0,
which confuses some software and users, a re-scaled SNR value is returned.
Code originally by Rusty Scott.
Signed-off-by: Trent Piepho [EMAIL PROTECTED]
Signed-off-by: Rusty Scott [EMAIL PROTECTED]
Signed-off-by: Michael Krufky [EMAIL PROTECTED]
diff -r a80a23f896b2 -r 7d0f07be41e8
linux/drivers/media/dvb/frontends/lgdt330x.c
--- a/linux/drivers/media/dvb/frontends/lgdt330x.c Sun Oct 29 11:12:27
2006 -0300
+++ b/linux/drivers/media/dvb/frontends/lgdt330x.c Sun Oct 29 11:35:39
2006 -0500
@@ -31,9 +31,6 @@
* Air2PC/AirStar 2 ATSC 3rd generation (HD5000)
* pcHDTV HD5500
*
- * TODO:
- * signal strength always returns 0.
- *
*/
#include linux/kernel.h
@@ -46,8 +43,12 @@
#include asm/byteorder.h
#include dvb_frontend.h
+#include dvb_math.h
#include lgdt330x_priv.h
#include lgdt330x.h
+
+/* Use Equalizer Mean Sqaured Error instead of Phaser Tracker MSE */
+/* #define USE_EQMSE */
static int debug = 0;
module_param(debug, int, 0644);
@@ -68,6 +69,7 @@ struct lgdt330x_state
/* Demodulator private data */
fe_modulation_t current_modulation;
+ u32 snr; /* Result of last SNR calculation */
/* Tuner private data */
u32 current_frequency;
@@ -549,161 +551,150 @@ static int lgdt3303_read_status(struct d
return 0;
}
+/* Calculate SNR estimation (scaled by 2^24)
+
+ 8-VSB SNR equations from LGDT3302 and LGDT3303 datasheets, QAM
+ equations from LGDT3303 datasheet. VSB is the same between the '02
+ and '03, so maybe QAM is too? Perhaps someone with a newer datasheet
+ that has QAM information could verify?
+
+ For 8-VSB: (two ways, take your pick)
+ LGDT3302:
+ SNR_EQ = 10 * log10(25 * 24^2 / EQ_MSE)
+ LGDT3303:
+ SNR_EQ = 10 * log10(25 * 32^2 / EQ_MSE)
+ LGDT3302 LGDT3303:
+ SNR_PT = 10 * log10(25 * 32^2 / PT_MSE) (we use this one)
+ For 64-QAM:
+ SNR= 10 * log10( 688128 / MSEQAM)
+ For 256-QAM:
+ SNR= 10 * log10( 696320 / MSEQAM)
+
+ We re-write the snr equation as:
+ SNR * 2^24 = 10*(c - intlog10(MSE))
+ Where for 256-QAM, c = log10(696320) * 2^24, and so on. */
+
+static u32 calculate_snr(u32 mse, u32 c)
+{
+ if (mse == 0) /* No signal */
+ return 0;
+
+ mse = intlog10(mse);
+ if (mse c) {
+ /* Negative SNR, which is possible, but realisticly the
+ demod will lose lock before the signal gets this bad. The
+ API only allows for unsigned values, so just return 0 */
+ return 0;
+ }
+ return 10*(c - mse);
+}
+
+static int lgdt3302_read_snr(struct dvb_frontend* fe, u16* snr)
+{
+ struct lgdt330x_state* state = (struct lgdt330x_state*)
fe-demodulator_priv;
+ u8 buf[5]; /* read data buffer */
+ u32 noise; /* noise value */
+ u32 c; /* per-modulation SNR calculation constant */
+
+ switch(state-current_modulation) {
+ case VSB_8:
+ i2c_read_demod_bytes(state, LGDT3302_EQPH_ERR0, buf, 5);
+#ifdef USE_EQMSE
+ /* Use Equalizer Mean-Square Error Register */
+ /* SNR for ranges from -15.61 to +41.58 */
+ noise = ((buf[0] 7) 16) | (buf[1] 8) | buf[2];
+ c = 69765745; /* log10(25*24^2)*2^24 */
+#else
+ /* Use Phase Tracker Mean-Square Error Register */
+ /* SNR for ranges from -13.11 to +44.08 */
+ noise = ((buf[0] 73) 13) | (buf[3] 8) | buf[4];
+ c = 73957994; /* log10(25*32^2)*2^24 */
+#endif
+ break;
+ case QAM_64:
+ case QAM_256:
+ i2c_read_demod_bytes(state, CARRIER_MSEQAM1, buf, 2);
+ noise = ((buf[0] 3) 8) | buf[1];
+ c = state-current_modulation == QAM_64 ? 97939837 : 98026066;
+ /* log10(688128)*2^24 and log10(696320)*2^24 */
+ break;
+ default:
+ printk(KERN_ERR lgdt330x: %s: Modulation set to unsupported
value\n,
+ __FUNCTION__);
+ return -EREMOTEIO; /* return -EDRIVER_IS_GIBBERED; */
+ }
+
+ state-snr = calculate_snr(noise, c);
+ *snr = (state-snr) 16; /* Convert from 8.24 fixed-point to 8.8 */
+
+ dprintk(%s: noise = 0x%08x, snr = %d.%02d dB\n, __FUNCTION__, noise,
+ state-snr 24, (((state-snr8) 0x) * 100) 16);
+
+ return 0;
+}
+
+static int lgdt3303_read_snr(struct
Re: [linux-dvb] DiB7000M-driver released (Nova-T Stick, AverMedia and others)
El dom, 29-10-2006 a las 17:29 +0100, Patrick Boettcher escribió: On Sat, 21 Oct 2006, Jose Carlos Garcia Sogo wrote: El mar, 17-10-2006 a las 14:54 +0200, Patrick Boettcher escribió: Hi, in my repository (http://linuxtv.org/hg/~pb/v4l-dvb) I just committed a first working version of the dib7000m/p-driver along with some modifications in the dib0700-driver. Thanks for the great work. I tested with a first generation Nova-T stick - it works (AverMedia is identical). There is a chance that someone has the newer version of those devices - it contains a different version of the DiB7000 - I will try to release this one as soon as possible. As Volar device id defined in dvb-usb-ids.h is 0xa807, and I have a 0xb808, I think I have one of those new devices you say. I hope you can modify it soon so I can test it. I also committed the DiB7000P-driver, can you try it? (just add the USB IDs to dib0700_devices.c) Yes, it works like a charm. Thanks! The only thing is that I have to subtitute VOLAR ID, instead of adding. If I add another device, I get: Oct 29 19:29:50 gimli kernel: dib0700: loaded with support for 2 different device-types Oct 29 19:29:50 gimli kernel: usbcore: registered new driver dvb_usb_dib0700 And no frontend is loaded. Thanks! -- Jose Carlos Garcia Sogo [EMAIL PROTECTED] signature.asc Description: Esta parte del mensaje está firmada digitalmente ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Cam Menu?
On Sat, Oct 28, 2006 at 07:09:32PM +0100, Andrew Lyon wrote: Is there any util I can use with Technotrend S-1500 with CI to get into the cam menu? The cam has settings that I need to change, apparently with a set top box you can go into the cam menu, but I cannot find any way with a dvb card on linux. Try the gnutv app from the dvb-apps repo using the -cammenu option -- David Härdeman ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Hauppauge Nova-T Stick - problem with sound moduls after reboot
Hello all, I have an Hauppauge Nova-T Stick and I tried it on a debian system with the kernels 2.6.17 and 2.6.18. After installing it (with this stuff for example http://linuxtv.org/hg/v4l-dvb?ca=a80a23f896b2;type=gz ), everything worked perfectly. I watched tv with kaffeine for hours. But after the first reboot there are problems with the sound modules... ...nothing works... dmesg says: snd_tea575x_tuner: disagrees about version of symbol video_devdata snd_tea575x_tuner: Unknown symbol video_devdata snd_tea575x_tuner: disagrees about version of symbol video_unregister_device snd_tea575x_tuner: Unknown symbol video_unregister_device snd_tea575x_tuner: disagrees about version of symbol video_register_device snd_tea575x_tuner: Unknown symbol video_register_device snd_tea575x_tuner: disagrees about version of symbol video_devdata snd_tea575x_tuner: Unknown symbol video_devdata snd_tea575x_tuner: disagrees about version of symbol video_unregister_device snd_tea575x_tuner: Unknown symbol video_unregister_device snd_tea575x_tuner: disagrees about version of symbol video_register_device snd_tea575x_tuner: Unknown symbol video_register_device snd_fm801: Unknown symbol snd_tea575x_exit snd_fm801: Unknown symbol snd_tea575x_init and also kaffeine is crashing with the message kaffeine: Fatal IO error: client killed ICE default IO error handler doing an exit(), pid = 4923, errno = 9 KCrash: Application 'kaffeine' crashing... system call fstat: Ungültiger Dateideskriptor system call fstat: Ungültiger Dateideskriptor Any ideas? Thank you for helping, Katha. -- GMX DSL-Flatrate 0,- Euro* - Überall, wo DSL verfügbar ist! NEU: Jetzt bis zu 16.000 kBit/s! http://www.gmx.net/de/go/dsl ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500 tuning problems
On Sun, 2006-10-29 at 20:47 +, Torgeir Veimo wrote: On 29 Oct 2006, at 16:09, Patrick Boettcher wrote: Hi Torgeir, On Sat, 28 Oct 2006, Torgeir Veimo wrote: On 28 Oct 2006, at 00:35, Torgeir Veimo wrote: Am not sure where to start looking. I've included my dmesg output below; using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 52983 Hz video pid 0x, audio pid 0x01b2 status 01 | signal 7abf | snr | ber 001f | unc | status 01 | signal 7aab | snr | ber 001f | unc | status 01 | signal 7abe | snr | ber 001f | unc | status 01 | signal 7ac8 | snr | ber 001f | unc | Can you please send your channels.conf-line for this channel? Oops, there was an error there, I was supposed to enclose the channel name in quotes, so it simply used the wrong frequency. Still doesn't lock though. [EMAIL PROTECTED] szap]# ./tzap -c channels.conf-dvbt-crystal-palace BBC ONE using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 50583 Hz video pid 0x0258, audio pid 0x0259 status 01 | signal 7cb8 | snr | ber 001f | unc | status 01 | signal 7cd9 | snr | ber 001f | unc | status 01 | signal 7cc7 | snr | ber 001f | unc | status 01 | signal 7cdd | snr | ber 001f | unc | In your original post you mentioned that you had an older card which worked fine with this same setup. Is this still correct that if you run this same test with the other card then it will receive a signal OK? If this is the case, then your issue is that the new card doesn't like the offset and can only tune using the non-offset 506MHz frequency? Or do both cards only work at 506MHz now that you've moved? Jon ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Another patch for hvr1110
Hi. Tom snip TNT ok Analogic TV : OK Capture device : not tested Remote control : Nothing works (perhaps ...) Radio : not tested Radio is Ok Bye, Bye Well, that's all for today ! Good luck Hartmut Thanks :) Tom So you have the board fully working now? I am in doubt about this: +case SAA7134_BOARD_HAUPPAUGE_HVR1110: +ir_codes = ir_codes_hauppauge_new; +//ir_type = IR_TYPE_RC5; +mask_keycode = 0; +polling = 50; // ms +break; if mask_keycode applies to the complete GPIO port (not sure in this case), this cannot be right since part of this port is used for the DVB transport stream. Can you please cross check this? Also i must say that i lost sync. After you checked, can you please resend your patch (maybe to me personally) so that i can integrate it? Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500 tuning problems
On 29 Oct 2006, at 22:32, Jon Burgess wrote: In your original post you mentioned that you had an older card which worked fine with this same setup. Is this still correct that if you run this same test with the other card then it will receive a signal OK? If this is the case, then your issue is that the new card doesn't like the offset and can only tune using the non-offset 506MHz frequency? Or do both cards only work at 506MHz now that you've moved? Only the old card works at 506MHz. I have a tiny antenna which I tried with force_lna_activation=1, and it seems to pick up at least one transponder at 522MHz, so it seems it can tune when the offset is correct (I don't have a proper outdoor antenna to test with..) I guess I need to wait until some offset issues are resolved in the nova-t 500 driver then.. I'm still baffled by why the in-wall signal doesn't have the correct offset though. -- Torgeir Veimo [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kernel 2.6.18 (FC6) and Nova-T DVB cards
I demand that Graeme Hilton may or may not have written... Are there any known issues with using Hauppauge Nova-T DVB PCI cards on kernel 2.6.18? I've just upgraded to Fedora Core 6 which comes with kernel 2.6.18 (uname -r gives 2.6.18-1.2798.fc6). That's probably really 2.6.19-git*. Unfortunately both my Nova-T PCI cards are non-functional. Mine have been working with 2.6.18.1 (but I'm currently running 2.6.17.x on that machine due to crashes with 2.6.18.1). You should try 2.6.18.1 or 2.6.17.latest. [snip] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | URL:http://www.youmustbejoking.demon.co.uk/progs.packages.html You will forget that you ever knew me. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500 tuning problems
On 29 Oct 2006, at 16:09, Patrick Boettcher wrote: Hi Torgeir, On Sat, 28 Oct 2006, Torgeir Veimo wrote: On 28 Oct 2006, at 00:35, Torgeir Veimo wrote: Am not sure where to start looking. I've included my dmesg output below; using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 52983 Hz video pid 0x, audio pid 0x01b2 status 01 | signal 7abf | snr | ber 001f | unc | status 01 | signal 7aab | snr | ber 001f | unc | status 01 | signal 7abe | snr | ber 001f | unc | status 01 | signal 7ac8 | snr | ber 001f | unc | Can you please send your channels.conf-line for this channel? Oops, there was an error there, I was supposed to enclose the channel name in quotes, so it simply used the wrong frequency. Still doesn't lock though. [EMAIL PROTECTED] szap]# ./tzap -c channels.conf-dvbt-crystal-palace BBC ONE using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 50583 Hz video pid 0x0258, audio pid 0x0259 status 01 | signal 7cb8 | snr | ber 001f | unc | status 01 | signal 7cd9 | snr | ber 001f | unc | status 01 | signal 7cc7 | snr | ber 001f | unc | status 01 | signal 7cdd | snr | ber 001f | unc | The channels.conf-dvbt-crystal-palace file contains #channels.conf for DVB-T - Crystal Palace Transmitter # Multiplex 1 BBC - Channel 25, Offset -, Freq 50583 BBCi: 50583:INVERSION_OFF:BANDWIDTH_8_MHZ:FEC_3_4:FEC_NONE:QAM_16:TRANSMIS SION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:0:4479 CBBC Channel: 50583:INVERSION_OFF:BANDWIDTH_8_MHZ:FEC_3_4:FEC_NONE:QAM_16:TRANSMIS SION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:0:4671 BBC ONE: 50583:INVERSION_OFF:BANDWIDTH_8_MHZ:FEC_3_4:FEC_NONE:QAM_16:TRANSMIS SION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:600:601 BBC TWO: 50583:INVERSION_OFF:BANDWIDTH_8_MHZ:FEC_3_4:FEC_NONE:QAM_16:TRANSMIS SION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:610:611 BBC THREE: 50583:INVERSION_OFF:BANDWIDTH_8_MHZ:FEC_3_4:FEC_NONE:QAM_16:TRANSMIS SION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:620:621 BBC NEWS 24:50583:INVERSION_OFF:BANDWIDTH_8_MHZ:FEC_3_4:FEC_NONE:QAM_16:TRANS MISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:640:641 etc.. -- Torgeir Veimo [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500 tuning problems
Hi Torgeir, On Sat, 28 Oct 2006, Torgeir Veimo wrote: On 28 Oct 2006, at 00:35, Torgeir Veimo wrote: Am not sure where to start looking. I've included my dmesg output below; using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 52983 Hz video pid 0x, audio pid 0x01b2 status 01 | signal 7abf | snr | ber 001f | unc | status 01 | signal 7aab | snr | ber 001f | unc | status 01 | signal 7abe | snr | ber 001f | unc | status 01 | signal 7ac8 | snr | ber 001f | unc | Can you please send your channels.conf-line for this channel? The firmware i use is the one mentioned in; http://www.linuxtv.org/pipermail/linux-dvb/2006-September/012847.html, points http:to http://vaasa.wi-bw.tfh-wildau.de/~pboettch/home/files/dvb-usb-dib0700-01.fw Correct. Patrick. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TTBudget/Wintv Nova big transponder problem
I have tt budget s1102 with Philips SU1278/S tuner, not ALPS BSRU6. It's init file is a budget-ci.c. I found many distinctions between stv0299 setting in bsru6.h and budget-ci.c, may be in this is a trouble? I not use 2.4 kernel, but I will do it for testing. sorry bad english... On Sat, 28 Oct 2006 03:08:19 +0200 Oliver Endriss [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: lspci :00:12.0 0480: 1131:7146 (rev 01) Subsystem: 13c2:100f kern.log Oct 1 09:22:26 (none) kernel: saa7146: register extension 'budget_ci dvb'. Oct 1 09:22:27 (none) kernel: DVB: registering frontend 1 (ST STV0299 DVB-S)... Ok, an Nova-CI with BSRU6 tuner. Apparently there must be some difference between the 2.4 and 2.6 drivers. I own an old Nova-S but I cannot access any transponder with that symbol rate. :-( Could someone who is able to reproduce the problem please find out which change is causing the regression? It might be some register setting in the inittab (2.6 - bsru6.h, 2.4 - stv0299.c) or in the frontend driver (stv0299.c). CU Oliver -- VDR Remote Plugin 0.3.8 available at http://www.escape-edv.de/endriss/vdr/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Pridvorov Andrey Anatolyevich Vladivostok --- Professional hosting for everyone - http://www.host.ru ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] kernel 2.6.18.1 sa7146
== Date: Sat, 28 Oct 2006 15:31:58 +0200 From: Thomas Dressler [EMAIL PROTECTED] To: linux-dvb@linuxtv.org Subject: [linux-dvb] kernel 2.6.18.1 sa7146 == hi! at first: sorry my english is bad. i want compile kernel 2.6.18.1 with the included sa7146 dvb driver as module. but i can't select it in menuconfig. which moduls must i select also? or where can i find more infos?. i2c, pci, v4l, dvb-core is selected. It should be: Device Drivers - Multimedia devices -Digital Video Video Broadcasting Devices - DVB Core Support In fact, DVB Core support should add support for SAA7146 based cards However, I think support for this kind od device is rather problematic, please report whether you'll be successful. BTW, is has anyone been able to get a Technotrend budget card (mine is DVB 3200-S2) working? Rgds, Marco ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] CA_CI_MODULE_READY not reset when CAM removed from AV7110 DVB card
I'm currently improving VDR's CAM handling, and while doing so I came across what seems to be a bug in the AV7110 driver code. If I do int fd = open(/dev/dvb/adapter0/ca0, O_RDWR); ca_slot_info_t sinfo; sinfo.num = 0; ioctl(fd, CA_GET_SLOT_INFO, sinfo); to check whether the CI adapter contains a CAM, the value of sinfo.flags is 0 as long as no CAM is inserted. When I insert a CAM, it first goes to 1 (CA_CI_MODULE_PRESENT) and then to 3 (CA_CI_MODULE_PRESENT | CA_CI_MODULE_READY). So far everything is ok. However, when I remove the CAM from the slot, sinfo.flags still remains set to 3. It never goes back to 0. Is this a bug or intended behavior? Klaus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] lgdt330x: SNR and signal strength reporting
Hi, On Sun, 29 Oct 2006, Michael Krufky wrote: I'm posting this to the list for final review before requesting merge into master. You get what you've asked for: lgdt330x: SNR and signal strength reporting Update the SNR calculations to use the new dvb_math log function, and add SNR calculations for all supported modulations for both lg dt3302 and dt3303. The QAM equations don't appear in the dt3302 datasheet, so the ones from the dt3303 datasheet were used. SNR returned is the actual value in dB as 8.8 fixed point. Reporting of real signal strength isn't supported, so rather than return 0, which confuses some software and users, a re-scaled SNR value is returned. Code originally by Rusty Scott. Signed-off-by: Trent Piepho [EMAIL PROTECTED] Signed-off-by: Rusty Scott [EMAIL PROTECTED] Signed-off-by: Michael Krufky [EMAIL PROTECTED] diff -r a80a23f896b2 -r 7d0f07be41e8 linux/drivers/media/dvb/frontends/lgdt330x.c --- a/linux/drivers/media/dvb/frontends/lgdt330x.cSun Oct 29 11:12:27 2006 -0300 +++ b/linux/drivers/media/dvb/frontends/lgdt330x.cSun Oct 29 11:35:39 2006 -0500 @@ -31,9 +31,6 @@ * Air2PC/AirStar 2 ATSC 3rd generation (HD5000) * pcHDTV HD5500 * - * TODO: - * signal strength always returns 0. - * */ #include linux/kernel.h @@ -46,8 +43,12 @@ #include asm/byteorder.h #include dvb_frontend.h +#include dvb_math.h #include lgdt330x_priv.h #include lgdt330x.h + +/* Use Equalizer Mean Sqaured Error instead of Phaser Tracker MSE */ ^^^ Squared? + /* Negative SNR, which is possible, but realisticly the + demod will lose lock before the signal gets this bad. The + API only allows for unsigned values, so just return 0 */ In DVB-T QPSK FEC 1/2 it is possible to receive while having a negative SNR. best regards, Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TT-premium DVB-S rev1.5 audio problem
Hi Oliver! On Sat, 28 Oct 2006 03:19:36 +0200 Oliver Endriss [EMAIL PROTECTED] bubbled: Martin Zwickel wrote: Hi there! I have a small problem: I get no audio from my DVB-S card since a few months. But I can't remember what could have changed that. There is no audio from the jack, nor from my Aux-In Mixer. Everything else works as expected (at least with vdr), I can tune, set filters, watch TV, ... but no audio from the HW. I'm already thinking about a DAC issue... I'm using kernel 2.6.18, v4l-hg latest and alsa. Also the av7110 firmware is the latest, but also tried older ones. My card pci info: 00:0c.0 0480: 1131:7146 (rev 01) Subsystem: 13c2: Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (3750ns min, 9500ns max) Interrupt: pin A routed to IRQ 5 Region 0: Memory at dfffac00 (32-bit, non-prefetchable) [size=512] If you cannot get any sound out of the 3.5mm audio jack of the card, and - cable is ok - sound is not muted [vdr] - sound is not set to digital output [vdr audio menu] your card is probably broken. Cable is ok, vdr unmuted, analog output ... :( Hm - you have a Technotrend mail address, and TT is the manufacturer of those cards. They should be able to fix it... At least I work for them :) But I wonder why it should be broken somehow. I thought it could be a software problem, something that I missed during the last year. Now it's time to use my solder iron ... ;) Thanks anyway! Regards, Martin -- MyExcuse: Interference between the keyboard and the chair. Martin Zwickel [EMAIL PROTECTED] Research Development TechnoTrend AG http://www.technotrend.de signature.asc Description: PGP signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
