Re: [linux-dvb] Any chance of help with v4l-dvb-experimental / Avermedia A16D please?
Hi Mauro, On Fri, 2008-03-14 at 17:21 -0300, Mauro Carvalho Chehab wrote: On Sat, 15 Mar 2008 04:34:34 +0900 timf [EMAIL PROTECTED] wrote: Now, do two tests, with v4l-dvb tree + the patch: Of course, you'll need to compile and install v4l-dvb ;) make make install cx88-dvb or saa7134-dvb ? saa7134-dvb. Cheers, Mauro This time: 1) new install of ubuntu 7.10 2) mercurial v4l-dvb, patched 3) make, sudo make install 4) in /etc/modprobe.d/options [EMAIL PROTECTED]:~$ sudo cat /etc/modprobe.d/options [sudo] password for timf: # Enable double-buffering so gstreamer et. al. work options quickcam compatible=2 # Default hostap to managed mode options hostap_pci iw_mode=2 options hostap_cs iw_mode=2 options tuner-xc2028 debug=1 options tuner debug=1 options saa7134 tuner=71 i2c_scan=1 [EMAIL PROTECTED]:~$ 5) xc3028-v27.fw into /lib/firmware/2.6.22-14-generic sudo chmod 644 xc3028-v27.fw 6) reboot 7) dmesg snip [ 14.856000] ACPI: PCI Interrupt :00:05.0[A] - Link [APC7] - GSI 16 (level, low) - IRQ 20 [ 14.856000] PCI: Setting latency timer of device :00:05.0 to 64 [ 14.86] NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.19 Wed Sep 12 14:12:24 PDT 2007 [ 14.86] parport_pc 00:08: reported by Plug and Play ACPI [ 14.86] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA] [ 14.936000] Linux video capture interface: v2.00 [ 14.952000] usbcore: registered new interface driver xpad [ 14.952000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/input/joystick/xpad.c: driver for Xbox controllers v0.1.6 [ 14.996000] saa7130/34: v4l2 driver version 0.2.14 loaded [ 15.00] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17 [ 15.00] ACPI: PCI Interrupt :04:09.0[A] - Link [APC2] - GSI 17 (level, low) - IRQ 21 [ 15.00] saa7133[0]: found at :04:09.0, rev: 209, irq: 21, latency: 32, mmio: 0xfdbff000 [ 15.00] saa7133[0]: subsystem: 1461:f936, board: AVerMedia Hybrid TV/Radio (A16D) [card=137,autodetected] [ 15.00] saa7133[0]: board init: gpio is 2fa00 [ 15.168000] saa7133[0]: i2c eeprom 00: 61 14 36 f9 00 00 00 00 00 00 00 00 00 00 00 00 [ 15.168000] saa7133[0]: i2c eeprom 10: ff ff ff ff ff 20 ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom 20: 01 40 01 02 02 01 01 00 08 ff 00 0e ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom 40: ff 65 00 ff c2 1e ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.168000] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.184000] saa7133[0]: i2c scan: found device @ 0xa0 [eeprom] [ 15.196000] saa7133[0]: i2c scan: found device @ 0xc2 [???] [ 15.296000] tuner' 2-0061: Setting mode_mask to 0x0e [ 15.296000] tuner' 2-0061: chip found @ 0xc2 (saa7133[0]) [ 15.296000] tuner' 2-0061: tuner 0x61: Tuner type absent [ 15.304000] tuner' 2-0061: switching to v4l2 [ 15.304000] tuner' 2-0061: tv freq set to 400.00 [ 15.304000] tuner' 2-0061: tuner type not set [ 15.304000] tuner' 2-0061: tv freq set to 400.00 [ 15.304000] tuner' 2-0061: tuner type not set [ 15.304000] saa7133[0]: registered device video0 [v4l2] [ 15.304000] saa7133[0]: registered device vbi0 [ 15.304000] saa7133[0]: registered device radio0 [ 15.304000] tuner' 2-0061: Cmd TUNER_SET_STANDBY accepted for analog TV [ 15.332000] saa7134 ALSA driver for DMA sound loaded [ 15.332000] saa7133[0]/alsa: saa7133[0] at 0xfdbff000 irq 21 registered as card -2 [ 15.392000] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22 [ 15.392000] ACPI: PCI Interrupt :00:10.1[B] - Link [AAZA] - GSI 22 (level, low) - IRQ 17 [ 15.392000] PCI: Setting latency timer of device :00:10.1 to 64 snip 7) lsmod snip loop 19076 0 snd_hda_intel 263712 1 saa7134_alsa 15648 0 snd_pcm_oss44672 0 snd_mixer_oss 17664 1 snd_pcm_oss tuner 27724 0 tea5767 8324 1 tuner tda8290
[linux-dvb] Multiproto S2 card with Terratec DVB-C scanning
Hi, I have a AzureWave S2 card running with http://jusst.de/hg/mantis and I also have a Terratec 1200-C DVB-C card that I want to use at the same time. However, when using the new scan (dvb-apps) for multiproto it's not possible to scan DVB-C. How do I make the cards work togheter, scanning for channels? Regards Claes ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Multiproto S2 card with Terratec DVB-C scanning
Use separate scan/zap for each card. Regards, Vladimir On Mar 15, 2008, at 1:34 PM, Claes Lindblom wrote: Hi, I have a AzureWave S2 card running with http://jusst.de/hg/mantis and I also have a Terratec 1200-C DVB-C card that I want to use at the same time. However, when using the new scan (dvb-apps) for multiproto it's not possible to scan DVB-C. How do I make the cards work togheter, scanning for channels? Regards Claes ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Sat, Mar 15, 2008 at 5:32 AM, Antti Palosaari [EMAIL PROTECTED] wrote: forgot attach patch... Antti Palosaari wrote: Michael Krufky wrote: 4.3 is not close enough to 3.8. If you don't know how to set the demod to 3.8, then we can do some hacks to make it work, but signal reception is likely to be very poor -- better off looking in his snoop log to see how the windows driver sets the demod to 3.8 OI have looked sniffs and tested linux driver and found that it is set to 3800. There is 4300 kHz set in eeprom, it is ok for 8 MHz but not for 6 or 7. Looks like driver needs to do some quirks when this tuner is used. Anyhow, patch attached is hardcoded to use 3.8 now. Jarryd, please test. Also some changes to stick plug done, if it does not work for you can fix it as earlier. regards Antti -- http://palosaari.fi/ I tried it with both patches separately, and both patches together. None of them worked, and with both together I got a kernel oops, lost my keyboard and it wouldn't even reboot so I had to cut the power. Michael's patch didn't produce any interesting dmesg output. I included dmesg for plugging in and tuning with antti's patch. Jarryd. Here is dmesg with antti's patch when I plugged it in: usb 5-1: new high speed USB device using ehci_hcd and address 4 usb 5-1: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: af9015_usb_probe: af9015: af9015_rw_udev: sending failed: -71 (8/0) af9015: af9015_rw_udev: receiving failed: -71 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: af9015: af9015_rw_udev: sending failed: -71 (63/0) snip - repeated about 200 times af9015: af9015_rw_udev: sending failed: -71 (26/0) af9015: af9015_rw_udev: sending failed: -71 (8/0) af9015: af9015_rw_udev: receiving failed: -71 af9015: af9015_download_firmware: boot failed: -71 dvb_usb_af9015: probe of 5-1:1.1 failed with error -71 usb 5-1: USB disconnect, address 4 dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. usb 5-1: new high speed USB device using ehci_hcd and address 5 usb 5-1: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:02 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick) af9015_eeprom_dump: 00: 31 c2 bb 0b 00 00 00 00 13 04 29 60 00 02 01 02 10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 30 32 30 20: 35 30 35 30 30 30 30 31 ff ff ff ff ff ff ff ff 30: 00 00 3a 01 00 08 02 00 cc 10 00 00 9c ff ff ff 40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff 50: ff ff ff ff ff 26 00 00 04 03 09 04 10 03 4c 00 60: 65 00 61 00 64 00 74 00 65 00 6b 00 30 03 57 00 70: 69 00 6e 00 46 00 61 00 73 00 74 00 20 00 44 00 80: 54 00 56 00 20 00 44 00 6f 00 6e 00 67 00 6c 00 90: 65 00 20 00 47 00 6f 00 6c 00 64 00 20 03 30 00 a0: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00 b0: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff af9015_read_config: xtal:2 set adc_clock:28000 af9015_read_config: tuner id1:156 af9015_read_config: spectral inversion:0 af9015_set_gpios: af9013: firmware version:4.95.0 DVB: registering frontend 0 (Afatech AF9013 DVB-T)... af9015_tuner_attach: af9015_tda18271_tuner_attach: tda18271 1-00c0: creating new instance af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 TDA18271HD/C1 detected @ 1-00c0 tda18271_init_regs: initializing registers for device @ 1-00c0 af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 snip - repeated about 30 times input: IR-receiver inside an USB DVB receiver as /class/input/input12 dvb-usb: schedule remote query interval to 200 msecs. dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected. af9015_init: af9015_download_ir_table: input: Leadtek WinFast DTV Dongle Gold as /class/input/input13 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:1d.7-1 dmesg after trying to tune: af9013_init af9013_reset af9013_power_ctrl: onoff:1 af9013_set_adc_ctrl: adc_clock:28000 af913_div: a:2800 b:100 x:19 af913_div: a:0 b:100 x:19 r:14680064 r:e0 adc_cw:00 00 e0 af9013_init: load ofsm settings af9013_init: load tuner specific settings af9013_init: setting ts mode af9013_lock_led: onoff:1 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 af9013_i2c_gate_ctrl: enable:1
Re: [linux-dvb] NXP 18211HDC1 tuner
Michael's patch didn't produce any interesting dmesg output. I included dmesg for plugging in and tuning with antti's patch. Jarryd. Just realised I didn't have debug enabled for Michael's patch. When tuning I got lots of this: tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 1-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d My keyboard was fine this time (that was the point it normally responded really slowly), and the driver loaded instantly instead of taking nearly half a minute. It looks like it might be a step in the right direction, but it's still not tuning. Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: Michael's patch didn't produce any interesting dmesg output. I included dmesg for plugging in and tuning with antti's patch. First errors came from same situation as earlier, no_reconnect. But it finally still worked. Just realised I didn't have debug enabled for Michael's patch. When tuning I got lots of this: tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 1-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d My keyboard was fine this time (that was the point it normally responded really slowly), and the driver loaded instantly instead of taking nearly half a minute. It looks like it might be a step in the right direction, but it's still not tuning. Jarryd. Frequency control values of the demodulator seems to be ok now. Also adc and coeff looks correct. It is hard to say where is problem... Can you test if demodulator can detect TPS parameter automatically? You can do that inserting AUTO to initial tuning file, for example set FEC AUTO. And then scan tuning-file regards Antti -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] First patch for Freecom DVB-T (with usb id 14aa:0160)
On Fri, 14 Mar 2008 22:24:46 +0100 Jan Hoogenraad [EMAIL PROTECTED] wrote: Dear v4l maintainer: Please, just call me by my name ;) I have created a first version of the patch for the Freecom stick, based on the latest sources I received today from RealTek. Due to several issues I've noticed at the driver, I opted, for now, to add it as a separate tree. This way, we can fix things there, without affecting the staging tree. I've made it available at: http://linuxtv.org/hg/~mchehab/rtl2831 Also, I noticed that nobody, on RealTek signed it. It would be interesting if someone there could send us a SOB for the first changeset: http://linuxtv.org/hg/~mchehab/rtl2831/rev/bb7749446173 Ah, by convention, we name directories in lowercase. So, I've did an sed before applying your patch, as I've explained at the changeset comments. I have received several updates per week from them during the fixing time, so I expect some updates later on. Ok. I'm not very familiar with Mercurial / HG. I've put the sources into a separate directory, and created the patch with hg commit / hg export / hg rollback This works ;) It compiles with the latest v4l. It has been tested on my system only yet. Please review the way of submission. In general, patches are sent as in-line. However, for big patches, it is accepted to have them compressed. Mauro: Thanks for the help. I agree that this is probably the best thing to do. Ok, this is the Lindent changeset: http://linuxtv.org/hg/~mchehab/rtl2831/rev/698c1894a3fd Unfortunately, Lindent does not fix errors that make checkpatch reports like the two below. tuner_mxl5005s.h: In '// I2C birdge module demod argument setting': tuner_mxl5005s.h:531: ERROR: do not use C99 // comments I tried to quickfix this with a small perl script, like: for i in *.c *.h; do perl -ne \ 'if (s|//\s*(.*)\n|/* \1 */\n|) { s|/\*\s*\*/||; } print $_' \ $i /tmp/tmp; mv -f /tmp/tmp $i; done However, this failed, since there are some comments with // inside. It doesn't seem to be hard to fix this by a close script. tuner_mxl5005s.h: In 'void mxl5005s_SetI2cBridgeModuleTunerArg(TUNER_MODULE * pTuner);': tuner_mxl5005s.h:532: ERROR: foo * bar should be foo *bar True. Yet, this shows another thing that is forbidden on Linux CodingStyle: the usage of typedef. While this is valid on a few cases, on most cases we prefer to use things like struct foo *foo;. --- Due to the size of the driver, and the nature of it (a port from other OS), it is natural that we will have a large amount of issues. Before visiting the code to check everything, maybe the better approach would be to do some general comments. I'll start commenting some things about CodingStyle. The better is if you could read kernel Documentation/CodingStyle. 1) Kernel already defines several types. Please use the already defined typedefs. For example: +typedef unsigned char U8Data; use, instead __u8 +typedef unsigned int UData_t; /* type must be at least 32 bits */ use, instead __u32 +typedef int SData_t; /* type must be at least 32 bits */ use, instead __s32 +typedef void *Handle_t; /* memory pointer type Just use void * 2) We don't use typedef struct foo. Instead, just declare struct foo and replace all foo * to struct foo *: +typedef struct { + UData_t nAS_Algorithm; + UData_t f_ref; + UData_t f_in; + UData_t f_LO1; + UData_t f_if1_Center; + UData_t f_if1_Request; + UData_t f_if1_bw; + UData_t f_LO2; + UData_t f_out; + UData_t f_out_bw; + UData_t f_LO1_Step; + UData_t f_LO2_Step; + UData_t f_LO1_FracN_Avoid; + UData_t f_LO2_FracN_Avoid; + UData_t f_zif_bw; + UData_t f_min_LO_Separation; + UData_t maxH1; + UData_t maxH2; + UData_t bSpurPresent; + UData_t bSpurAvoided; + UData_t nSpursFound; + UData_t nZones; + struct MT_ExclZone_t *freeZones; + struct MT_ExclZone_t *usedZones; + struct MT_ExclZone_t MT_ExclZones[MAX_ZONES]; } MT_AvoidSpursData_t; 3) Name convention. Names are generally in lower case. Since we try to have all lines with maxsize=80, the better is trying to have shorter names. I don't think that it would be a good idea to replace all names inside the driver, since this will make your life harder, when receiving patches from Realtek. Anyway, please consider this if you need to touch on some var name. There are other comments I want to do, about the integration with the tree. I intend to do it later, after having a better understanding on how the driver works and what can be done to avoid code duplication with dvb core and to allow the usage of the tuners by other drivers. Also, I'll need help from other developers on this large task ;) Cheers, Mauro ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
I tried changing to 2.6.22-19 on my ubuntu 7.10 with autosuspend=-1 but i still lost one tuner. Have reverted back to 2.6.22-14-generic now and have disabled the remote-pulling...and i just lost a tuner, restarting my cardclient and mythbackend got it back. Did you have remote-pulling disabled in -19 ? 2008/3/14 Ivor Hewitt [EMAIL PROTECTED]: Still no failures here on 2.6.22.19, had one or two mt2060 I2C write failed messages but that didn't stop anything working. Running mythtv with multi-rec. I've attached the list of usb and i2c named files that changed between 2.6.22.19 and linux-2.6.23.12. I'll browse through and if I have time I'll apply a few of the diffs and see if I can create a breakage. Cheers, Ivor ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Patrik Hansson wrote: I tried changing to 2.6.22-19 on my ubuntu 7.10 with autosuspend=-1 but i still lost one tuner. Have reverted back to 2.6.22-14-generic now and have disabled the remote-pulling...and i just lost a tuner, restarting my cardclient and mythbackend got it back. Did you have remote-pulling disabled in -19 ? Still ticking along nicely here. I have options: options dvb-usb-dib0700 force_lna_activation=1 options dvb-usb disable_rc_polling=1 (since I have no remote) Is the ubuntu kernel completely generic? I still see an mt2060 write failed error every now and then (four in the past 24 hours), but that doesn't appear to break anything. Do you have complete tuner loss as soon as you get a write error? Ivor. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Sat, 2008-03-15 at 19:42 +, Ivor Hewitt wrote: Patrik Hansson wrote: I tried changing to 2.6.22-19 on my ubuntu 7.10 with autosuspend=-1 but i still lost one tuner. Have reverted back to 2.6.22-14-generic now and have disabled the remote-pulling...and i just lost a tuner, restarting my cardclient and mythbackend got it back. Did you have remote-pulling disabled in -19 ? Still ticking along nicely here. I have options: options dvb-usb-dib0700 force_lna_activation=1 options dvb-usb disable_rc_polling=1 (since I have no remote) I only have the lna option. Is the ubuntu kernel completely generic? Really not, if you mean straight out of kernel.org. I still see an mt2060 write failed error every now and then (four in the past 24 hours), but that doesn't appear to break anything. Do you have complete tuner loss as soon as you get a write error? I do get some of those errors, never a tuner drop. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Any progress on the Avermedia DVB-S (A700)?
Hi, Matthias I've seen you have new patches available on your repository. ¿Have you made any progress lately on the driver? I tested the patches, but the results were the habitual ones... Seems this card is really hard to support... :( Best regards, Eduard ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Nicolas Will wrote: My Ubuntu-provided 2.6.22 works fine. And I am not losing any tuner. Not even with the Multirec of MythTV 0.21. Right, well I've had enough of Ubuntu 8.04a2 (and I've learned a valuable lesson about not using alpha OSes on production systems). This is mostly down to my own actions, though -- the kernel is utterly hosed, the nVidia driver won't load, and the HVR-3000 is refusing to talk (instead insisting that the demux chip isn't talking). I've backed the system off to 7.10 (Gutsy) and it seems stable -- I had to modify the patch from http://dev.kewl.org/hauppauge/ to apply on the latest Hg source... Much fun. It seems to work, so I'll probably publish the repository tomorrow some time (after the day I've had I don't feel like doing much of anything). Plus I'd rather like to see if it works before I go unleashing it on the masses at large. I'm just waiting for ScanDVB to finish making a channels.conf for ASTRA 28.2E, after that I'll see if I can crash the T500 :) -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Sat, Mar 15, 2008 at 8:42 PM, Ivor Hewitt [EMAIL PROTECTED] wrote: Patrik Hansson wrote: I tried changing to 2.6.22-19 on my ubuntu 7.10 with autosuspend=-1 but i still lost one tuner. Have reverted back to 2.6.22-14-generic now and have disabled the remote-pulling...and i just lost a tuner, restarting my cardclient and mythbackend got it back. Did you have remote-pulling disabled in -19 ? Still ticking along nicely here. I have options: options dvb-usb-dib0700 force_lna_activation=1 options dvb-usb disable_rc_polling=1 (since I have no remote) Is the ubuntu kernel completely generic? I still see an mt2060 write failed error every now and then (four in the past 24 hours), but that doesn't appear to break anything. Do you have complete tuner loss as soon as you get a write error? Ivor. The only error in my log the lat time i lost a tuner was: mt2060 I2C read failed So not even a write failed. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Nova-S-Plus scan ERROR: Initial Tuning Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The output of lspci -vvv on my computer looks like this: 04:00.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) Subsystem: Hauppauge computer works Inc. Nova-S-Plus DVB-S 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: 32 (5000ns min, 13750ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 20 Region 0: Memory at e500 (32-bit, non-prefetchable) [size=16M] Capabilities: [44] Vital Product Data Capabilities: [4c] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 04:00.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05) Subsystem: Hauppauge computer works Inc. Unknown device 9202 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: 32 (1000ns min, 63750ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 20 Region 0: Memory at e600 (32-bit, non-prefetchable) [size=16M] Capabilities: [4c] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 04:00.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) Subsystem: Hauppauge computer works Inc. Unknown device 9202 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: 32 (1500ns min, 22000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 20 Region 0: Memory at e700 (32-bit, non-prefetchable) [size=16M] Capabilities: [4c] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 04:00.4 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [IR Port] (rev 05) Subsystem: Hauppauge computer works Inc. Unknown device 9202 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: 32 (1500ns min, 63750ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 7 Region 0: Memory at e800 (32-bit, non-prefetchable) [size=16M] Capabilities: [4c] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- I installed v4l and now have a /dev/dvb/adapter0 directory demux0 dvr0 frontend0 net0 I should note that the items in that directory are colored yellow with black background (perhaps this is indicating something related to the problem? When I use scan I get this scan -a 0 /usr/share/doc/dvb-utils/examples/scan/dvb-s/Astra-19.2E scanning /usr/share/doc/dvb-utils/examples/scan/dvb-s/Astra-19.2E using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 12551500 V 2200 5 tune to: 12551:v:0:22000 WARNING: tuning failed!!! tune to: 12551:v:0:22000 (tuning failed) WARNING: tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. If I connect the cable to a decoder + tv I get all the channels and perfect image. I'm using a dual / twin LNB. Dual for Astra 19.2 E and 23.5 E with 2 connectors. I did get it to work on my previous computer. Any ideas? Timothy. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFH3FDS+j5y+etesF8RAldeAKDeRHdC3YqDZNBze975O5peeRjILgCeNQqV CukiOWQomn8Ctkn2ErrQMI4= =QbCX -END PGP SIGNATURE- ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Philip Pemberton wrote: Nicolas Will wrote: My Ubuntu-provided 2.6.22 works fine. And I am not losing any tuner. Not even with the Multirec of MythTV 0.21. Right, well I've had enough of Ubuntu 8.04a2 (and I've learned a valuable lesson about not using alpha OSes on production systems). This is mostly down to my own actions, though -- the kernel is utterly hosed, the nVidia driver won't load, and the HVR-3000 is refusing to talk (instead insisting that the demux chip isn't talking). I've backed the system off to 7.10 (Gutsy) and it seems stable -- I had to modify the patch from http://dev.kewl.org/hauppauge/ to apply on the latest Hg source... Much fun. It seems to work, so I'll probably publish the repository tomorrow some time (after the day I've had I don't feel like doing much of anything). Plus I'd rather like to see if it works before I go unleashing it on the masses at large. I'm just waiting for ScanDVB to finish making a channels.conf for ASTRA 28.2E, after that I'll see if I can crash the T500 :) Regarding the NVidia module, NVidia themselves haven't yet conjured up a fix for the latest kernels. I hope they do so as one kernel symbol (init_mm) that is needed was temporarily reexported and will again not be exported from 2.6.26-rc. That seems to be the holdup at NVidia, hopefully will be sorted by the time 2.6.25 final appears. NVIDIA_2.6.25.patch.txt can be downloaded from the NVidia Linux forum which works with later 2.6.24-git kernels and 2.6.25-rc. Here I have been running it with kernels up to current 2.6.25-rc5-git5. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Sun, Mar 16, 2008 at 1:22 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: Michael's patch didn't produce any interesting dmesg output. I included dmesg for plugging in and tuning with antti's patch. First errors came from same situation as earlier, no_reconnect. But it finally still worked. Just realised I didn't have debug enabled for Michael's patch. When tuning I got lots of this: tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 1-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d My keyboard was fine this time (that was the point it normally responded really slowly), and the driver loaded instantly instead of taking nearly half a minute. It looks like it might be a step in the right direction, but it's still not tuning. Jarryd. Frequency control values of the demodulator seems to be ok now. Also adc and coeff looks correct. It is hard to say where is problem... Can you test if demodulator can detect TPS parameter automatically? You can do that inserting AUTO to initial tuning file, for example set FEC AUTO. And then scan tuning-file regards Antti -- http://palosaari.fi/ Sorry I'm completely lost at this point, are you talking about adding something to /usr/share/dvb-apps/dvb-t/au-sydney_north_shore and then running scandvb, or are you talking about something else? Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: On Sun, Mar 16, 2008 at 1:22 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Frequency control values of the demodulator seems to be ok now. Also adc and coeff looks correct. It is hard to say where is problem... Can you test if demodulator can detect TPS parameter automatically? You can do that inserting AUTO to initial tuning file, for example set FEC AUTO. And then scan tuning-file Sorry I'm completely lost at this point, are you talking about adding something to /usr/share/dvb-apps/dvb-t/au-sydney_north_shore and then running scandvb, or are you talking about something else? yes, adding parameters to tuning-file. I added some AUTO parameters, use attached file to scan. Try scan au-Sydney_North_Shore_test, hopefully it says something more that tuning failed. It is good indicator if there is even PID-filter timeouts. I have no idea how to debug more. Without device it is rather hard to test many things. It will help a little if we know is tuner locked. Mike, is it easy to add debug writing for tuner to indicate if tuner is locked or not locked? I have used that method earlier with mt2060 tuner... Good luck for Kimi and Heikki todays F1 Australian GP:) regards Antti -- http://palosaari.fi/ # Australia / Sydney / North Shore (aka Artarmon/Gore Hill/Willoughby) # # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy # # ABC VHF12 T 22650 7MHz 3/4 NONE QAM64 AUTO 1/16 NONE # Seven VHF6 T 17750 7MHz AUTO NONE QAM64 8k 1/16 NONE # Nine VHF8 T 191625000 7MHz 3/4 NONE AUTO 8k 1/16 NONE # Ten VHF11 T 21950 7MHz 3/4 NONE QAM64 8k AUTO NONE # SBS UHF34 T 57150 7MHz 2/3 NONE QAM64 8k 1/8 NONE # D44 UHF35 T 57850 7MHz 2/3 NONE QAM64 8k 1/32 NONE ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Sid Boyce wrote: Regarding the NVidia module, NVidia themselves haven't yet conjured up a fix for the latest kernels. [snip] This was on 2.6.24 -- once I downgraded to 2.6.22, just about everything that could break, did. For bonus points, none of the packages would recompile either (but maybe I was being stupid). Like said, it was easier to just hose it down and start over. I've got the following kopts enabled for the DVB modules: == [EMAIL PROTECTED]:~$ cat /etc/modprobe.d/dvb-options # enable LNA for Hauppauge Nova-T-500 options dvb-usb-dib0700 force_lna_activation=1 # disable IR remote for Nova-T-500 (and other USB-DVB IRCs) options dvb-usb disable_rc_polling=1 # force card order -- DiB0700 (Nova-T-500) first, then CX88 (HVR-3000). # also creates virtual i/f 10 so Myth can see the Freeview hybrid install cx88-dvb /sbin/modprobe dvb-usb-dib0700; /sbin/modprobe --ignore-install cx88-dvb; mkdir -p /dev/dvb/adapter10; ln -sf /dev/dvb/adapter2/demux1 /dev/dvb/adapter10/demux0; ln -sf /dev/dvb/adapter2/dvr1 /dev/dvb/adapter10/dvr0; ln -sf /dev/dvb/adapter2/frontend1 /dev/dvb/adapter10/frontend0; ln -sf /dev/dvb/adapter2/net1 /dev/dvb/adapter10/net0 == At the moment both of the Nova-T-500's tuners are recording live TV, and the HVR-3000 is in DVT-T mode and recording too. No problems yet, but uptime is only 75 minutes. It's got a massive list of things to record overnight (think stress test), so fingers crossed. The only USB disconnect warning in dmesg is from when I unplugged the USB mouse after I got the R/C working. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Sun, Mar 16, 2008 at 11:08 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Sun, Mar 16, 2008 at 1:22 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Frequency control values of the demodulator seems to be ok now. Also adc and coeff looks correct. It is hard to say where is problem... Can you test if demodulator can detect TPS parameter automatically? You can do that inserting AUTO to initial tuning file, for example set FEC AUTO. And then scan tuning-file Sorry I'm completely lost at this point, are you talking about adding something to /usr/share/dvb-apps/dvb-t/au-sydney_north_shore and then running scandvb, or are you talking about something else? yes, adding parameters to tuning-file. I added some AUTO parameters, use attached file to scan. Try scan au-Sydney_North_Shore_test, hopefully it says something more that tuning failed. It is good indicator if there is even PID-filter timeouts. I have no idea how to debug more. Without device it is rather hard to test many things. It will help a little if we know is tuner locked. Mike, is it easy to add debug writing for tuner to indicate if tuner is locked or not locked? I have used that method earlier with mt2060 tuner... Good luck for Kimi and Heikki todays F1 Australian GP:) regards Antti -- http://palosaari.fi/ # Australia / Sydney / North Shore (aka Artarmon/Gore Hill/Willoughby) # # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy # # ABC VHF12 T 22650 7MHz 3/4 NONE QAM64 AUTO 1/16 NONE # Seven VHF6 T 17750 7MHz AUTO NONE QAM64 8k 1/16 NONE # Nine VHF8 T 191625000 7MHz 3/4 NONE AUTO 8k 1/16 NONE # Ten VHF11 T 21950 7MHz 3/4 NONE QAM64 8k AUTO NONE # SBS UHF34 T 57150 7MHz 2/3 NONE QAM64 8k 1/8 NONE # D44 UHF35 T 57850 7MHz 2/3 NONE QAM64 8k 1/32 NONE Here's the first frequency it tuned to, as you can see the one you set auto on is still auto, it didn't seem to autodetect anything. It was the same for all the other frequencies as well. tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: Here's the first frequency it tuned to, as you can see the one you set auto on is still auto, it didn't seem to autodetect anything. It was the same for all the other frequencies as well. tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! It does not matter what scan outputs as tuning parameters because it just shows same parameter that are set by used tuning file (at least when tuning fails). Driver will still try to auto detect correct parameters. In this case it still fails for reason or other that is not found yet. regards Antti -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Sun, Mar 16, 2008 at 11:37 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: Here's the first frequency it tuned to, as you can see the one you set auto on is still auto, it didn't seem to autodetect anything. It was the same for all the other frequencies as well. tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! It does not matter what scan outputs as tuning parameters because it just shows same parameter that are set by used tuning file (at least when tuning fails). Driver will still try to auto detect correct parameters. In this case it still fails for reason or other that is not found yet. regards Antti -- http://palosaari.fi/ So the fact that it failed isn't actually telling us anything extra then? Would it only have been useful if it had actually worked? Also just to make sure I'm using the right drivers here, I'm using Michael's patch and not Antti's patch. Since it kernel oopses with both, Antti, do you want me to try with just your patch and not Michael's? Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: On Sun, Mar 16, 2008 at 11:37 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: Here's the first frequency it tuned to, as you can see the one you set auto on is still auto, it didn't seem to autodetect anything. It was the same for all the other frequencies as well. tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! It does not matter what scan outputs as tuning parameters because it just shows same parameter that are set by used tuning file (at least when tuning fails). Driver will still try to auto detect correct parameters. In this case it still fails for reason or other that is not found yet. regards Antti -- http://palosaari.fi/ So the fact that it failed isn't actually telling us anything extra then? Would it only have been useful if it had actually worked? Also just to make sure I'm using the right drivers here, I'm using Michael's patch and not Antti's patch. Since it kernel oopses with both, Antti, do you want me to try with just your patch and not Michael's? Jarryd. You need to use that patch of mine because I dont think the af9015 i2c likes 39-byte i2c transfers. The patch that I sent to you breaks the tda182x1 register initialization into 16 register chunks. -Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Antti Palosaari wrote: I have no idea how to debug more. Without device it is rather hard to test many things. It will help a little if we know is tuner locked. Mike, is it easy to add debug writing for tuner to indicate if tuner is locked or not locked? I have used that method earlier with mt2060 tuner... There is a lock bit in register 0x01[6] but I have not found it to be reliable, especially not on the c1 part. -Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] big problem with dexatek sphere dk-5701 bt878 sat card
Hallo, I'm having a big trouble with dexatek sphere dk-5701 card. When I have this pci card plugged in motherboard, when trying to install or boot (after having installed without the card)ubuntu (any version) the system freezes when it has to recognize the card giving this message: bttv0: subsytsem :2001 unknown card detected=0 bt878 (rev 17) irq 17 latency 32 mmio 0xfdaff000 I can't find a driver that make it works neither a way to disable the card just to boot ubuntu. The only way to use ubuntu for me at the moment is to unplug the card! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Sun, Mar 16, 2008 at 11:47 AM, Michael Krufky [EMAIL PROTECTED] wrote: Antti Palosaari wrote: I have no idea how to debug more. Without device it is rather hard to test many things. It will help a little if we know is tuner locked. Mike, is it easy to add debug writing for tuner to indicate if tuner is locked or not locked? I have used that method earlier with mt2060 tuner... There is a lock bit in register 0x01[6] but I have not found it to be reliable, especially not on the c1 part. -Mike You won't believe this, but it worked. I think every time I tried both patches together I left .no_reconnect in. I tried it again with both patches applied, no other modifications, and it worked. Thanks for all your help, Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: You won't believe this, but it worked. I think every time I tried both patches together I left .no_reconnect in. I tried it again with both patches applied, no other modifications, and it worked. Thanks for all your help, Jarryd. Great. I will finalize support for this tuner and add it to tree. It will take some time because I will need to test whether or not there is maximum byte count in af9015 i2c-hardware. If yes, there is two solutions 1) print error to log that too long i2c-transfer = tuner driver needs changed. 2) Split i2c-transfer in the driver. Is there any other driver that splits i2c-messages? Can you make some test to find solution where no_reconnect is not used, means same as no_reconnect=0 ? There is #if 0 / #if 1 definitions in download firmware. Also sleep in same place can be changed. This (reconnection after fw download) is really problem. Any ideas to resolving it is highly welcome. regards Antti Palosaari -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Sun, Mar 16, 2008 at 12:39 PM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: You won't believe this, but it worked. I think every time I tried both patches together I left .no_reconnect in. I tried it again with both patches applied, no other modifications, and it worked. Thanks for all your help, Jarryd. Great. I will finalize support for this tuner and add it to tree. It will take some time because I will need to test whether or not there is maximum byte count in af9015 i2c-hardware. If yes, there is two solutions 1) print error to log that too long i2c-transfer = tuner driver needs changed. 2) Split i2c-transfer in the driver. Is there any other driver that splits i2c-messages? Can you make some test to find solution where no_reconnect is not used, means same as no_reconnect=0 ? There is #if 0 / #if 1 definitions in download firmware. Also sleep in same place can be changed. This (reconnection after fw download) is really problem. Any ideas to resolving it is highly welcome. regards Antti Palosaari -- http://palosaari.fi/ I'll have a fiddle with no_reconnect and the firmware download and see what happens. Also there's a blue light that comes on in windows when I tune, but it didn't come on in linux when tuned. Would it be possible to work out how to make that light come on when it has successfully tuned? Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: On Sun, Mar 16, 2008 at 11:47 AM, Michael Krufky [EMAIL PROTECTED] wrote: Antti Palosaari wrote: I have no idea how to debug more. Without device it is rather hard to test many things. It will help a little if we know is tuner locked. Mike, is it easy to add debug writing for tuner to indicate if tuner is locked or not locked? I have used that method earlier with mt2060 tuner... There is a lock bit in register 0x01[6] but I have not found it to be reliable, especially not on the c1 part. -Mike You won't believe this, but it worked. I think every time I tried both patches together I left .no_reconnect in. I tried it again with both patches applied, no other modifications, and it worked. Thanks for all your help, Jarryd. This is great news! For an experiment, can you try once more without my patch applied? This will just confirm whether or not we can write all 39 registers at once. If the patch that I gave you is truly needed, then I will integrate it into the official driver. Regards, Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: Also there's a blue light that comes on in windows when I tune, but it didn't come on in linux when tuned. Would it be possible to work out how to make that light come on when it has successfully tuned? Should be peace of cake to fix. I will check it later... Antti -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Sun, Mar 16, 2008 at 1:04 PM, Michael Krufky [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Sun, Mar 16, 2008 at 11:47 AM, Michael Krufky [EMAIL PROTECTED] wrote: Antti Palosaari wrote: I have no idea how to debug more. Without device it is rather hard to test many things. It will help a little if we know is tuner locked. Mike, is it easy to add debug writing for tuner to indicate if tuner is locked or not locked? I have used that method earlier with mt2060 tuner... There is a lock bit in register 0x01[6] but I have not found it to be reliable, especially not on the c1 part. -Mike You won't believe this, but it worked. I think every time I tried both patches together I left .no_reconnect in. I tried it again with both patches applied, no other modifications, and it worked. Thanks for all your help, Jarryd. This is great news! For an experiment, can you try once more without my patch applied? This will just confirm whether or not we can write all 39 registers at once. If the patch that I gave you is truly needed, then I will integrate it into the official driver. Regards, Mike Takes half a minute to load when plugging in, keyboard is slow to respond when tuning, and I get lots of this: af9013_i2c_gate_ctrl: enable:0 af9013_i2c_gate_ctrl: enable:1 Applied the patch again and it was all fine. Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: On Sun, Mar 16, 2008 at 1:04 PM, Michael Krufky [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Sun, Mar 16, 2008 at 11:47 AM, Michael Krufky [EMAIL PROTECTED] wrote: Antti Palosaari wrote: I have no idea how to debug more. Without device it is rather hard to test many things. It will help a little if we know is tuner locked. Mike, is it easy to add debug writing for tuner to indicate if tuner is locked or not locked? I have used that method earlier with mt2060 tuner... There is a lock bit in register 0x01[6] but I have not found it to be reliable, especially not on the c1 part. -Mike You won't believe this, but it worked. I think every time I tried both patches together I left .no_reconnect in. I tried it again with both patches applied, no other modifications, and it worked. Thanks for all your help, Jarryd. This is great news! For an experiment, can you try once more without my patch applied? This will just confirm whether or not we can write all 39 registers at once. If the patch that I gave you is truly needed, then I will integrate it into the official driver. Regards, Mike Takes half a minute to load when plugging in, keyboard is slow to respond when tuning, and I get lots of this: af9013_i2c_gate_ctrl: enable:0 af9013_i2c_gate_ctrl: enable:1 Applied the patch again and it was all fine. Jarryd. Thanks for the test, Jarryd. I will integrate this into the official tda18271 driver after testing again on my hardware here. I will probably make it an attach-time configurable option. Regards, Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Antti Palosaari wrote: Jarryd Beck wrote: Also there's a blue light that comes on in windows when I tune, but it didn't come on in linux when tuned. Would it be possible to work out how to make that light come on when it has successfully tuned? Should be peace of cake to fix. I will check it later... Antti Antti, I created an attach-time parameter to limit the i2c transfer size during tda18271 initialization. Please take a look: http://linuxtv.org/hg/~mkrufky/tda18271/rev/8ab90c649c7b Regards, Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb