Re: [linux-dvb] New unsupported device
On Mon, Mar 17, 2008 at 9:48 PM, insomniac [EMAIL PROTECTED] wrote: On Mon, 17 Mar 2008 10:41:47 +0100 insomniac [EMAIL PROTECTED] wrote: Patched and recompiled the modules. Now plugging in the usb stick triggers the loading of the related kernel modules. The one error I get in dmesg is dvb_core: exports duplicate symbol dvb_unregister_adapter (owned by kernel) Great :-) Here my dmesg: dvb-usb: found a 'Pinnacle PCTV 73e' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' dib0700: firmware started successfully. dvb-usb: found a 'Pinnacle PCTV 73e' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Pinnacle PCTV 73e) dvb-usb: no frontend was attached by 'Pinnacle PCTV 73e' dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Pinnacle PCTV 73e) dvb-usb: no frontend was attached by 'Pinnacle PCTV 73e' input: IR-receiver inside an USB DVB receiver as /class/input/input6 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: Pinnacle PCTV 73e successfully initialized and connected. But another problem here: w_scan version 20060902 Info: using DVB adapter auto detection. Info: unable to open frontend /dev/dvb/adapter0/frontend0' Info: unable to open frontend /dev/dvb/adapter1/frontend0' Info: unable to open frontend /dev/dvb/adapter2/frontend0' Info: unable to open frontend /dev/dvb/adapter3/frontend0' main:2140: FATAL: * NO USEABLE DVB CARD FOUND. * Please check wether dvb driver is loaded and verify that no dvb application (i.e. vdr) is running. and also: # ls /dev/dvb/* /dev/dvb/adapter0: demux0 dvr0 net0 /dev/dvb/adapter1: demux0 dvr0 net0 So, no frontend is created. What may be? Thanks, -- Andrea Barberio That means the driver either couldn't work out what the tuner is and therefore, couldn't attach a frontend, or there was an error attaching the frontend. The next job is to work out what the tuner chip is, you might have to open it up and read the writing off the chip to find that out. Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] New unsupported device
On Mon, Mar 17, 2008 at 4:26 AM, insomniac [EMAIL PROTECTED] wrote: Hi to everyone on the list, this is my first post on the mailing list. I landed here after a lot of searching for a working driver for my DVB-T USB stick. I bought a Pinnacle PCTV Nano Stick (code: 73e) with HD capabilities, and I discovered that it came on the market very recently (less than one month ago). As long as no google search, nor post search on linux-dvb mailing list had success, it looks this is my last chance to get my card working on GNU/Linux. Here is the (actually useless) output I get from dmesg: usb 1-1: new high speed USB device using ehci_hcd and address 5 usb 1-1: configuration #1 chosen from 1 choice and here is my lsusb -v output about the card: http://insomniac.slackware.it/lsusb.pinnacle.txt In the hope that there's a light at the end of the tunnel, I thank you all for your patience and your work. Best regards, -- Andrea Barberio The best way you can help is to either tell us what the windows drivers are, or open the device up and tell us what is written on both the tuner chip and the main chip. They are generally the two biggest chips on the board and they have writing on the top. 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
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
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
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
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
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
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
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
On Thu, Mar 13, 2008 at 1:20 PM, Jarryd Beck [EMAIL PROTECTED] wrote: On Thu, Mar 13, 2008 at 10:11 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote: Then, please turn ON debug, repeat your tests, and post again with dmesg. I am not familiar with the af9015 driver, but for tda18271, set debug=1. (you must unload all modules first -- do 'make unload' in the v4l-dvb dir, then replug your device) -Mike Sorry I'm unsure where to set debug. Jarryd. I added initial support for this tda-tuner to the driver. Jarryd, can you test? http://linuxtv.org/hg/~anttip/af9015_new/ There is debug switch in af9013 module that may be helpful if it does not work. You can enable it as described or if it is too hard to play with modprobe just edit af9013.c file in frontend directory and set debug=1 by hard coding. If it does not work you can also try set GPIO3 setting (af9015) to 0xb instead 0x3 used currently. Also try to change rf-spectral inversion to see if it helps. Firmware should be ok and all other settings as well as I can see from usb-sniffs. With little lucky it should start working. regards Antti -- http://palosaari.fi/ Thanks, but now for some reason all I get is this: usb 2-10: new high speed USB device using ehci_hcd and address 6 usb 2-10: configuration #1 chosen from 1 choice input: Leadtek WinFast DTV Dongle Gold as /class/input/input8 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 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: usbcore: registered new interface driver dvb_usb_af9015 Jarryd. I found the problem, the driver I had set .no_reconnect = 1 in af9015_properties, the one in af9015_new didn't. So after I changed that I tried again, it still didn't work. I enabled debugging and tried to tune to a channel and this is what I got in dmesg. usb 2-10: new high speed USB device using ehci_hcd and address 27 usb 2-10: 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: 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 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 tda18271_init_regs: initializing registers for device @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input39 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/input40 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_set_standby_mode: sm = 1, sm_lt = 0, sm_xt = 0 Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux
Re: [linux-dvb] NXP 18211HDC1 tuner
On Fri, Mar 14, 2008 at 11:13 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: I found the problem, the driver I had set .no_reconnect = 1 in af9015_properties, the one in af9015_new didn't. So after I changed that I tried again, it still didn't work. I enabled debugging and tried to tune to a channel and this is what I got in dmesg. I know this no_reconnect problem. But haven't found proper correction yet. Looks like sometimes with some hw / sw configuration it reconnects USB-bus after firmware download and sometimes not. When there is no_reconnect set it is possible that driver loads twice (two adapters) and it causes race condition when two drivers are accessing same hw same time and it hangs (remote polling causes hangs very soon after plug). You can help and test if it is OK set no_reconnect=0 and remove #if 0 -killed code by changing it to #if 1 in line where is comment firmware is running, reconnect device in the usb bus. This forces AF9015 chipset reconnect USB. usb 2-10: new high speed USB device using ehci_hcd and address 27 usb 2-10: 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: 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 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 tda18271_init_regs: initializing registers for device @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input39 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/input40 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_set_standby_mode: sm = 1, sm_lt = 0, sm_xt = 0 There is no debug logs from af9013 demodulator module. You can enable logs by modprobe af9013 debug=1. Remember rmmod modules first from memory rmmod dvb_usb_af9015 af9013 mt2060 dvb_usb dvb_core af9013 debug should log rather much useful data when tuning to channel. Did you try change GPIO3 as mentioned earlier? regards Antti -- http://palosaari.fi/ I tried what you said, it works with no_reconnect = 1 and #if 0, and it also works with no_reconnect = 0 and #if 1, but no_reconnect = 0 and #if 0 doesn't work. It has a fit if I use no_reconnect = 1 and #if 1. It gives me a lot of this: Mar 14 13:42:17 localhost kernel: af9015: af9015_rw_udev: receiving failed: -22 Mar 14 13:42:17 localhost kernel: dvb-usb: error while querying for an remote control event. I also tried changing the rf_spec_inv and gpio3 but that didn't seem to do anything. It seems like it's the tuner, from dmesg the rest seems to be working fine. Here is dmesg with debug enabled on af9013 too: usb 2-10: new high speed USB device using ehci_hcd and address 7 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0
Re: [linux-dvb] NXP 18211HDC1 tuner
On Fri, Mar 14, 2008 at 2:19 PM, Michael Krufky [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Fri, Mar 14, 2008 at 11:13 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: I found the problem, the driver I had set .no_reconnect = 1 in af9015_properties, the one in af9015_new didn't. So after I changed that I tried again, it still didn't work. I enabled debugging and tried to tune to a channel and this is what I got in dmesg. I know this no_reconnect problem. But haven't found proper correction yet. Looks like sometimes with some hw / sw configuration it reconnects USB-bus after firmware download and sometimes not. When there is no_reconnect set it is possible that driver loads twice (two adapters) and it causes race condition when two drivers are accessing same hw same time and it hangs (remote polling causes hangs very soon after plug). You can help and test if it is OK set no_reconnect=0 and remove #if 0 -killed code by changing it to #if 1 in line where is comment firmware is running, reconnect device in the usb bus. This forces AF9015 chipset reconnect USB. usb 2-10: new high speed USB device using ehci_hcd and address 27 usb 2-10: 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: 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 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 tda18271_init_regs: initializing registers for device @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input39 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/input40 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_set_standby_mode: sm = 1, sm_lt = 0, sm_xt = 0 There is no debug logs from af9013 demodulator module. You can enable logs by modprobe af9013 debug=1. Remember rmmod modules first from memory rmmod dvb_usb_af9015 af9013 mt2060 dvb_usb dvb_core af9013 debug should log rather much useful data when tuning to channel. Did you try change GPIO3 as mentioned earlier? regards Antti -- http://palosaari.fi/ I tried what you said, it works with no_reconnect = 1 and #if 0, and it also works with no_reconnect = 0 and #if 1, but no_reconnect = 0 and #if 0 doesn't work. It has a fit if I use no_reconnect = 1 and #if 1. It gives me a lot of this: Mar 14 13:42:17 localhost kernel: af9015: af9015_rw_udev: receiving failed: -22 Mar 14 13:42:17 localhost kernel: dvb-usb: error while querying for an remote control event. I also tried changing the rf_spec_inv and gpio3 but that didn't seem to do anything. It seems
Re: [linux-dvb] NXP 18211HDC1 tuner
On Fri, Mar 14, 2008 at 2:22 PM, Jarryd Beck [EMAIL PROTECTED] wrote: On Fri, Mar 14, 2008 at 2:19 PM, Michael Krufky [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Fri, Mar 14, 2008 at 11:13 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: I found the problem, the driver I had set .no_reconnect = 1 in af9015_properties, the one in af9015_new didn't. So after I changed that I tried again, it still didn't work. I enabled debugging and tried to tune to a channel and this is what I got in dmesg. I know this no_reconnect problem. But haven't found proper correction yet. Looks like sometimes with some hw / sw configuration it reconnects USB-bus after firmware download and sometimes not. When there is no_reconnect set it is possible that driver loads twice (two adapters) and it causes race condition when two drivers are accessing same hw same time and it hangs (remote polling causes hangs very soon after plug). You can help and test if it is OK set no_reconnect=0 and remove #if 0 -killed code by changing it to #if 1 in line where is comment firmware is running, reconnect device in the usb bus. This forces AF9015 chipset reconnect USB. usb 2-10: new high speed USB device using ehci_hcd and address 27 usb 2-10: 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: 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 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 tda18271_init_regs: initializing registers for device @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input39 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/input40 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_set_standby_mode: sm = 1, sm_lt = 0, sm_xt = 0 There is no debug logs from af9013 demodulator module. You can enable logs by modprobe af9013 debug=1. Remember rmmod modules first from memory rmmod dvb_usb_af9015 af9013 mt2060 dvb_usb dvb_core af9013 debug should log rather much useful data when tuning to channel. Did you try change GPIO3 as mentioned earlier? regards Antti -- http://palosaari.fi/ I tried what you said, it works with no_reconnect = 1 and #if 0, and it also works with no_reconnect = 0 and #if 1, but no_reconnect = 0 and #if 0 doesn't work. It has a fit if I use no_reconnect = 1 and #if 1. It gives me a lot
Re: [linux-dvb] Implementing support for multi-channel
2008/3/12 Ben Backx [EMAIL PROTECTED]: Hello, I was wondering if there's some info to find on how to implement (and test) multi-channel receiving? It's possible, because dvb uses streams and the driver is currently capable to filter one channel, but how can I implement the support of multi-channel filtering? Is there perhaps an open-source driver supporting this that I can have a look at? AFAIK tuners can already receive from multiple channels as long as they are on the same transponder (I think that's the right word). So in Australia you can receive channel 7 and the channel 7 guide because they are broadcast together. But I don't think you can do anymore than that. I think mythtv is capable of doing it so you could have a look at that. 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, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike I've got another tuner which works, so I know I'm tuning correctly, it just doesn't actually tune. I tried with mplayer, it just sat there saying dvb_tune Freq: 21950 and did nothing. It also made my whole computer go really slow, I don't know what it was actually doing. Antti, as I said I've never done anything like this before so I have no idea what I'm doing, so I have no idea where to paste which table. 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
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED] wrote: On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike I've got another tuner which works, so I know I'm tuning correctly, it just doesn't actually tune. I tried with mplayer, it just sat there saying dvb_tune Freq: 21950 and did nothing. It also made my whole computer go really slow, I don't know what it was actually doing. Antti, as I said I've never done anything like this before so I have no idea what I'm doing, so I have no idea where to paste which table. Please try using tzap. This will show you FE status once every second. Let it run for a whole minute -- maybe there is some noise that may cause it to take a longer time to lock (if that's the case, then there are some tweaks that we can do.) Show us the femon output produced by running tzap. -Mike $ tzap -a 2 TEN Digital using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' tuning to 21950 Hz video pid 0x0200, audio pid 0x028a status 01 | signal | snr | ber | unc | $ femon -a 2 using '/dev/dvb/adapter2/frontend0' FE: Afatech AF9013 DVB-T (TERRESTRIAL) status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | The status 00 lines were from before I started tzap, after I started tzap it did nothing for half a minute, then printed the status 01 line, then sat there for another half a minute, and I killed it at that point. My computer was also taking quite a few seconds to respond to me pressing the keyboard for the whole time I was tuning it. 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
On Thu, Mar 13, 2008 at 8:09 AM, [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED] wrote: On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike I've got another tuner which works, so I know I'm tuning correctly, it just doesn't actually tune. I tried with mplayer, it just sat there saying dvb_tune Freq: 21950 and did nothing. It also made my whole computer go really slow, I don't know what it was actually doing. Antti, as I said I've never done anything like this before so I have no idea what I'm doing, so I have no idea where to paste which table. Please try using tzap. This will show you FE status once every second. Let it run for a whole minute -- maybe there is some noise that may cause it to take a longer time to lock (if that's the case, then there are some tweaks that we can do.) Show us the femon output produced by running tzap. -Mike $ tzap -a 2 TEN Digital using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' tuning to 21950 Hz video pid 0x0200, audio pid 0x028a status 01 | signal | snr | ber | unc | $ femon -a 2 using '/dev/dvb/adapter2/frontend0' FE: Afatech AF9013 DVB-T (TERRESTRIAL) status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | The status 00 lines were from before I started tzap, after I started tzap it did nothing for half a minute, then printed the status 01 line, then sat there for another half a minute, and I killed it at that point. My computer was also taking quite a few seconds to respond to me pressing the keyboard for the whole time I was tuning it. Jarryd. What shows in dmesg during the above? -Mike nothing new 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
On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Thu, Mar 13, 2008 at 8:09 AM, [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED] wrote: On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike I've got another tuner which works, so I know I'm tuning correctly, it just doesn't actually tune. I tried with mplayer, it just sat there saying dvb_tune Freq: 21950 and did nothing. It also made my whole computer go really slow, I don't know what it was actually doing. Antti, as I said I've never done anything like this before so I have no idea what I'm doing, so I have no idea where to paste which table. Please try using tzap. This will show you FE status once every second. Let it run for a whole minute -- maybe there is some noise that may cause it to take a longer time to lock (if that's the case, then there are some tweaks that we can do.) Show us the femon output produced by running tzap. -Mike $ tzap -a 2 TEN Digital using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' tuning to 21950 Hz video pid 0x0200, audio pid 0x028a status 01 | signal | snr | ber | unc | $ femon -a 2 using '/dev/dvb/adapter2/frontend0' FE: Afatech AF9013 DVB-T (TERRESTRIAL) status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | The status 00 lines were from before I started tzap, after I started tzap it did nothing for half a minute, then printed the status 01 line, then sat there for another half a minute, and I killed it at that point. My computer was also taking quite a few seconds to respond to me pressing the keyboard for the whole time I was tuning it. Jarryd. What shows in dmesg during the above
Re: [linux-dvb] NXP 18211HDC1 tuner
On Thu, Mar 13, 2008 at 10:11 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote: Then, please turn ON debug, repeat your tests, and post again with dmesg. I am not familiar with the af9015 driver, but for tda18271, set debug=1. (you must unload all modules first -- do 'make unload' in the v4l-dvb dir, then replug your device) -Mike Sorry I'm unsure where to set debug. Jarryd. I added initial support for this tda-tuner to the driver. Jarryd, can you test? http://linuxtv.org/hg/~anttip/af9015_new/ There is debug switch in af9013 module that may be helpful if it does not work. You can enable it as described or if it is too hard to play with modprobe just edit af9013.c file in frontend directory and set debug=1 by hard coding. If it does not work you can also try set GPIO3 setting (af9015) to 0xb instead 0x3 used currently. Also try to change rf-spectral inversion to see if it helps. Firmware should be ok and all other settings as well as I can see from usb-sniffs. With little lucky it should start working. regards Antti -- http://palosaari.fi/ Thanks, but now for some reason all I get is this: usb 2-10: new high speed USB device using ehci_hcd and address 6 usb 2-10: configuration #1 chosen from 1 choice input: Leadtek WinFast DTV Dongle Gold as /class/input/input8 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 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: usbcore: registered new interface driver dvb_usb_af9015 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
Can you take logs with vendor WHQL driver and sent for further analysis? http://www.afatech.com/EN/support.aspx Antti -- http://palosaari.fi For some reason windows didn't like that driver. When I used the installer nothing happened, and when I used device manager it said this folder contains no information about your device. So I made a snoop with the driver on the CD, I hope it's good enough. I uploaded the snoop to http://download.yousendit.com/2B0B420876BFB959 While it was snooping, I plugged it in, tuned the card to a tv channel and pulled it out as quick as I could. If it helps, the channel was channel 7, sydney, australia. 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
One thing I can say -- the Linux tda18271 driver should be able to detect your tuner at 0xC0 (0x60) as a tda18271c1 -- It's worth a try, and could certainly be possible that the driver *may* work as-is, although I suspect that some tweaking will be needed. Regards, Mike I changed it's i2c as loaded by af9015 to 0xC0, then got this in dmesg: TDA18271HD/C1 detected @ 5-00c0 Also when I plugged it in, it sat there for about 10 seconds before finishing loading (dmesg printed another 5 lines about the device after about 10 seconds), but still no 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
Also when I plugged it in, it sat there for about 10 seconds before finishing loading (dmesg printed another 5 lines about the device after about 10 seconds), but still no tuning. Can I see those five lines? ;-) While you're at it, you may as well include dmesg from the point that the bridge driver loads and on. Here's dmesg from the point it starts up until it finishes printing stuff. usb 2-10: new high speed USB device using ehci_hcd and address 22 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Leadtek Winfast DTV Dongle Gold' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: dvb-usb: found a 'Leadtek Winfast DTV Dongle Gold' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Leadtek Winfast DTV Dongle Gold) 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 2 (Afatech AF9013 DVB-T)... af9015_tuner_attach: tda18271_tuner_attach: tda18271 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input34 dvb-usb: schedule remote query interval to 200 msecs. dvb-usb: Leadtek Winfast DTV Dongle Gold successfully initialized and connected. af9015_init: af9015_download_ir_table: input: Leadtek WinFast DTV Dongle Gold as /class/input/input35 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 You said that you tuned to channel 7, sydney, australia -- is that an 8 MHz channel? What frequency is it on? This is channel 7's entry in channels.conf: 7 Digital:17750:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:513:514:1312 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
I think that the tda18271 driver will work with your tuner, but we may need to make some small adjustments. If you look in tda18271-fe.c , you'll find the code that autodetects between a TDA18271c1 and a TDA18271c2 ... I just realised there's a problem with versions of code. I'm using the code from http://www.linuxtv.org/hg/~anttip/af9015 However I suppose you want me to use the code from the main repository. Needless to say it doesn't work with 0x60 or 0x61 as the address for the tuner. Also if I could somehow get this working with the right code, I don't know how to set up the values in the tda182171_config struct. Jarryd. On Mon, Mar 10, 2008 at 3:28 PM, Michael Krufky [EMAIL PROTECTED] wrote: On Mon, Mar 10, 2008 at 12:46 PM, Michael Krufky [EMAIL PROTECTED] wrote: Jarryd Beck wrote: Would someone be interested in writing tuner drivers for the NXP 18211HDC1 tuner? I recently bought the Winfast DTV Dongle Gold which uses an AF9015 chip and the NXP tuner. I've managed to get it working up to the point of needing the tuner, after that nothing works. I have no idea how to write tuner code, so if someone is interested, I can supply all the info I've got about the card and test whatever you write. Jarryd. Try the tda18271 driver -- I am under the impression that the tda18211 is a dvb-t only subset of the tda18271, but I dont have a tda18211 to test with and find out, nor do I have a tda18211 spec to look at. :-( Good Luck, Mike Jarryd Beck wrote: I tried that, but I wasn't sure about a few things, I was kind of making stuff up as I went along. Can you tell me if I've done this right? At the af9015_tuner_attach function I wrote a function tda18211_tuner_attach which calls dvb_attach. The one thing I'm not sure about is the function tda18271_attach has a parameter u8 addr. I don't know what that is supposed to do or where I am supposed to get it from. You can look up a datasheet from the nxp site, it appears it goes under the name tda18211HD, I don't know what the C1 at the end means, I'm hoping it's the same thing. The datasheet isn't very useful though, it pretty much only has a circuit diagram and a couple of numbers on it. Jarryd. Jarryd, Please don't drop cc to the mailing list (added back), and also remember not to top quote. The addr parameter is the i2c address of the tuner. It is most likely 0x60 or 0x61. For an example of how to attach the tda18271 driver, look in cx23885-dvb.c for CX23885_BOARD_HAUPPAUGE_HVR1800 where alt_tuner is 1. The datasheet on the nxp site wont help me -- i need to see the register map. I think that the tda18271 driver will work with your tuner, but we may need to make some small adjustments. If you look in tda18271-fe.c , you'll find the code that autodetects between a TDA18271c1 and a TDA18271c2 ... If the autodetection fails for your tuner, you might want to try hardcoding it to the tda18271c1. If that works, then I'll ask you to enable the register dump debug option (debug = 4) in the tda18271 driver and send me a dmesg snippit. That should help us to add the autodetection later. hth, 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
You can update af9015-tree to master level easily: hg pull -u http://linuxtv.org/hg/v4l-dvb hg merge Thanks, that worked well. Also if I could somehow get this working with the right code, I don't know how to set up the values in the tda182171_config struct. Take USB-sniffs and look there correct configuration values. I've looked at usb sniffs, and unfortunately I have no idea what I'm looking at, I don't have a clue what goes where. I've never even looked at a driver for anything before, so this is all new to me. 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
On Tue, Mar 11, 2008 at 12:38 AM, Michael Krufky [EMAIL PROTECTED] wrote: Jarryd Beck wrote: I think that the tda18271 driver will work with your tuner, but we may need to make some small adjustments. If you look in tda18271-fe.c , you'll find the code that autodetects between a TDA18271c1 and a TDA18271c2 ... [snip] Also if I could somehow get this working with the right code, I don't know how to set up the values in the tda182171_config struct. Jarryd, Assuming that there is no tda829x analog demod present, and that this is a digital-only device, try something like this: static struct tda18271_config jarryd_tda18271_config = { .gate = TDA18271_GATE_DIGITAL } You should leave .std_map as NULL unless you need to override the default values per standard. The value in the .std_bits corresponds to the lower five bits in EP3 (register 0x05 [4:0]) Most likely, the driver's default setting will work for you, but you may find that the vendor chose a different value if you sniff the usb traffic from the windows driver. This value is directly tied to the IF frequency between the tuner and demod. -Mike Krufky That didn't work, the problem is I can't tell where it's going wrong and I don't understand usb sniffs. I have a few questions: When af9015 reads the tuner, the existing tuners set the spectral inversion state-gpio3. Do you know what state-gpio3 does? The code then goes on to read the spectral inversion, but there's a comment there saying it's always 0, and the existing tuners have theirs set to 1, what should I set it to for this one? If it's the case that some of the other values in the config are wrong, how would I go about making sense of a usb sniff? Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] NXP 18211HDC1 tuner
Would someone be interested in writing tuner drivers for the NXP 18211HDC1 tuner? I recently bought the Winfast DTV Dongle Gold which uses an AF9015 chip and the NXP tuner. I've managed to get it working up to the point of needing the tuner, after that nothing works. I have no idea how to write tuner code, so if someone is interested, I can supply all the info I've got about the card and test whatever you write. Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Leadtek Winfast DTV Dongle Gold
It looks like there is a driver, it's just not official yet, I'll try that and see what happens. On Fri, Mar 7, 2008 at 1:57 PM, Jarryd Beck [EMAIL PROTECTED] wrote: It appears that the driver is the AF9015 which is unsupported at the moment. Quite a few devices appear to use this driver, is anyone planning on supporting it anytime soon? Looks like I'll be returning this one anyway, I'll get one that I know works. On Thu, Mar 6, 2008 at 2:28 PM, Jarryd Beck [EMAIL PROTECTED] wrote: I just bought a Leadtek Winfast DTV Dongle Gold, I thought it would be the same as the DTV Dongle, but apparently it's not, it's a new model fresh of the production line about a month ago. Of course it doesn't work following the instructions for the older model, I even recompiled the kernel so it would be recognised (changed the usb id, similar to changing the 6f00 to 6f01 for the last model), and got the firmware for the old one but it appears that it is quite different. Does anyone have any plans for working on this one? Or can someone give me some pointers about how all this stuff works, especially how to get the firmware out of the windows driver or at least work out which firmware and driver it should be using. Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Leadtek Winfast DTV Dongle Gold
It appears that the driver is the AF9015 which is unsupported at the moment. Quite a few devices appear to use this driver, is anyone planning on supporting it anytime soon? Looks like I'll be returning this one anyway, I'll get one that I know works. On Thu, Mar 6, 2008 at 2:28 PM, Jarryd Beck [EMAIL PROTECTED] wrote: I just bought a Leadtek Winfast DTV Dongle Gold, I thought it would be the same as the DTV Dongle, but apparently it's not, it's a new model fresh of the production line about a month ago. Of course it doesn't work following the instructions for the older model, I even recompiled the kernel so it would be recognised (changed the usb id, similar to changing the 6f00 to 6f01 for the last model), and got the firmware for the old one but it appears that it is quite different. Does anyone have any plans for working on this one? Or can someone give me some pointers about how all this stuff works, especially how to get the firmware out of the windows driver or at least work out which firmware and driver it should be using. Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Leadtek Winfast DTV Dongle Gold
I just bought a Leadtek Winfast DTV Dongle Gold, I thought it would be the same as the DTV Dongle, but apparently it's not, it's a new model fresh of the production line about a month ago. Of course it doesn't work following the instructions for the older model, I even recompiled the kernel so it would be recognised (changed the usb id, similar to changing the 6f00 to 6f01 for the last model), and got the firmware for the old one but it appears that it is quite different. Does anyone have any plans for working on this one? Or can someone give me some pointers about how all this stuff works, especially how to get the firmware out of the windows driver or at least work out which firmware and driver it should be using. Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb