[linux-dvb] TT S2-3200 vlc streaming
I'm getting late buffers with vlc on some transponders (DVB-S, same parameters, good signal guaranteed) while everything is fine with others. Using multiproto and TT S2-3200. Anyone having same problems? Regards, Vladimir ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] illegal bandwith value, driver for Terratec Cinergy DT usb XS
Hi Derk, On 3/10/08, Derk Dukker [EMAIL PROTECTED] wrote: Thank you very much Markus!! Do you also have any idea how to get the Cinergy CI usb working? I live in Holland and most of the channels are encrypted, so I need to use the Cinergy CI usb but I can't find drivers/information anywhere. I bought this in the firstplace for my playstation 3 with linux on it, I knew that support for CI was hard, but they said it would work with eyetv. So I thought, if it isn't working on linux it will on mac with eyetv. Everything works on my mac with eyetv except the CI usb :( there's no support for this CI device at this time. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Nova-T 500 issues - losing one tuner
Not sure if this helps or adds that much to the discussion... (I think this was concluded before) But I finally switched back to kernel 2.6.22.19 on March 5th (with current v4l-dvb code) and haven't had any problems with the Nova-t 500 since. Running mythtv with EIT scanning enabled. Looking in the kernel log I see a single mt2060 read failed message on March 6th and 9th and a single mt2060 write failed on March 8th. These events didn't cause any problems or cause the tuner or mythtv to fail though. 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 Tue, 2008-03-11 at 11:07 +, [EMAIL PROTECTED] wrote: Not sure if this helps or adds that much to the discussion... (I think this was concluded before) But I finally switched back to kernel 2.6.22.19 on March 5th (with current v4l-dvb code) and haven't had any problems with the Nova-t 500 since. Running mythtv with EIT scanning enabled. Looking in the kernel log I see a single mt2060 read failed message on March 6th and 9th and a single mt2060 write failed on March 8th. These events didn't cause any problems or cause the tuner or mythtv to fail though. ah. So this begs the question: What changed between 2.6.22 and 2.6.24? huh... funny, heh? So, if 2.6.24 is finger pointed, I'm interested in a solution, as I have a planned upgrade to it in about a month's time. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] initial scan file update for Australia - Tamworth
2008/3/7, Dominic Gardiner [EMAIL PROTECTED]: Please find attached, an updated initial scan file for Tamworth, Australia. Update includes Mt.Soma, Mt.Dowe, and Mt. Cen Cruaich transmitters. As of Friday March 7th 2008, NBN are finally broadcasting in Digital. Thanks, applying it :) Christoph ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Updated scan file for fr-noos-numericable
Hi, 2008/3/8, Guillaume Membré [EMAIL PROTECTED]: Hello Attached is a scan file for the french cable operator Numericable. Hope this helps :) snip diff -r 3cde3460d120 util/scan/dvb-c/fr-noos-numericable --- a/util/scan/dvb-c/fr-noos-numericable Tue Mar 11 12:40:20 2008 +0100 +++ b/util/scan/dvb-c/fr-noos-numericable Tue Mar 11 12:41:03 2008 +0100 @@ -1,41 +1,90 @@ # Cable en France # freq sr fec mod C 12300 6875000 NONE QAM64 +C 123125000 6875000 NONE QAM64 C 13100 6875000 NONE QAM64 +C 131125000 6875000 NONE QAM64 snip Nearly every entry is duplicated (two frequencies are too close to each other -- both lead to the same transponder ...). Regards Guillaume Christoph ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Trying to setup PCTV HD Card 800i
On Tue, Mar 11, 2008 at 3:36 AM, Brandon Rader [EMAIL PROTECTED] wrote: I tried the different repo that you suggested, and get the same error. Here is my new dmesg output http://pastebin.com/m4d43d4ef Brandon Please do not drop the list from the cc. Use the reply to all function of your email client instead of just reply. It seems the i2c bus is not working the way it should. Can you try the following? (With the current v4l-dvb tree) First, unload all the modules related to your card (cx88-*, s5h1409, xc5000). Then, load cx88xx with options i2c_debug=1 and i2c_scan=1 Post the relevant dmesg output to the list. -- Chaogui Zhang ___ 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
Have you applied any patches to the v4l-dvb source before compiling ? On 3/11/08, Nicolas Will [EMAIL PROTECTED] wrote: On Tue, 2008-03-11 at 11:07 +, [EMAIL PROTECTED] wrote: Not sure if this helps or adds that much to the discussion... (I think this was concluded before) But I finally switched back to kernel 2.6.22.19 on March 5th (with current v4l-dvb code) and haven't had any problems with the Nova-t 500 since. Running mythtv with EIT scanning enabled. Looking in the kernel log I see a single mt2060 read failed message on March 6th and 9th and a single mt2060 write failed on March 8th. These events didn't cause any problems or cause the tuner or mythtv to fail though. ah. So this begs the question: What changed between 2.6.22 and 2.6.24? huh... funny, heh? So, if 2.6.24 is finger pointed, I'm interested in a solution, as I have a planned upgrade to it in about a month's time. Nico ___ 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
[linux-dvb] Nova T-500 detection problem
Hi, I recently purchased two Nova T-500 (as far as I can tell it’s not one of the diversity range) cards one is the 99101 LF rev D8B5 and one is the 99102 LF rev C1B5. The 99101 LF is detected, the other is not. The only difference I can see is the postfix of the Dib 0700 chips. The working one is the Dib0700C-XCXXa-G and the other is Dib0700-1211b-G. With only the undetected card in, there is no mention of the dib0700 in dmesg and lspci shows: 02:05.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 02:05.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 02:05.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) Which I presume is the VT6212L on the cards. Is there something different I need to do for the second card or is it just not supported? Since I can get them both to work with the supplied Hauppauge software under Windows I am assuming it is not a faulty card. Any help is very much appreciated. Many thanks, Ian --- Ian Liverton ICT Technician Internal Virus Database is out-of-date. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.21.4 - Release Date: 03/03/2008 00:00 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova T-500 detection problem
On Tue, 2008-03-11 at 17:06 +, Ian Liverton wrote: Hi, I recently purchased two Nova T-500 (as far as I can tell it’s not one of the diversity range) cards one is the 99101 LF rev D8B5 and one is the 99102 LF rev C1B5. The 99101 LF is detected, the other is not. The only difference I can see is the postfix of the Dib 0700 chips. The working one is the Dib0700C-XCXXa-G and the other is Dib0700-1211b-G. With only the undetected card in, there is no mention of the dib0700 in dmesg and lspci shows: 02:05.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 02:05.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 02:05.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) Which I presume is the VT6212L on the cards. Is there something different I need to do for the second card or is it just not supported? Since I can get them both to work with the supplied Hauppauge software under Windows I am assuming it is not a faulty card. What is lsusb saying ? nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova T-500 detection problem
On Tue, 2008-03-11 at 17:36 +, Ian Liverton wrote: What is lsusb saying? Thanks for the fast reply! lsusb says: Bus 005 Device 002: ID 2040:9940 Hauppauge Bus 005 Device 001: ID : Bus 004 Device 001: ID : Bus 003 Device 001: ID : Bus 002 Device 001: ID : Bus 001 Device 001: ID : going back on list. Mine says Bus 010 Device 002: ID 2040:9950 Hauppauge and is recognized. You will need to edit linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h and define a new ID there (around line 128), then edit linux/drivers/media/dvb/dvb-usb/dib0700_devices.c and add the ID info (around line 980). I wonder if there is something to do around line 114 too, but not being a coder, I'm lost there. A proper dev should probably confirm. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [PATCH] support key repeat with dib0700 ir receiver - (resend signed off)
This patch enables support for repeating last event when a key is holded
down with dib0700 devices. It works with rc5 and nec remotes.
It also fixes an annoying bug that floods kernel log with Unknown key
messages after each keypress. This happened because the driver was not
resetting infrared register after each poll so it kept polling last key
even if nothing was being pressed. Fixing this, (calling rc_setup after
each poll), permits to implement key repeat.
Signed-off-by: Filippo Argiolas filippo.argiolas at gmail.com
I'm resending the patch because I didn't sign it off the first time.
It's been a while since it's out, it has been tested and received many
positive comments and no complaint. Please refer to my previous post for
a complete description of the problem and how the patch fixes it.
Hope everything is ok for inclusion :P
Thanks,
Cheers,
Filippo
diff -r 127f67dea087 linux/drivers/media/dvb/dvb-usb/dib0700.h
--- a/linux/drivers/media/dvb/dvb-usb/dib0700.h Tue Feb 26 20:43:56 2008 +
+++ b/linux/drivers/media/dvb/dvb-usb/dib0700.h Sun Mar 02 20:30:41 2008 +0100
@@ -37,6 +37,7 @@ struct dib0700_state {
u8 channel_state;
u16 mt2060_if1[2];
u8 rc_toggle;
+ u8 rc_counter;
u8 is_dib7000pc;
};
@@ -44,12 +45,15 @@ extern int dib0700_ctrl_clock(struct dvb
extern int dib0700_ctrl_clock(struct dvb_usb_device *d, u32 clk_MHz, u8 clock_out_gp3);
extern int dib0700_ctrl_rd(struct dvb_usb_device *d, u8 *tx, u8 txlen, u8 *rx, u8 rxlen);
extern int dib0700_download_firmware(struct usb_device *udev, const struct firmware *fw);
+extern int dib0700_rc_setup(struct dvb_usb_device *d);
extern int dib0700_streaming_ctrl(struct dvb_usb_adapter *adap, int onoff);
extern struct i2c_algorithm dib0700_i2c_algo;
extern int dib0700_identify_state(struct usb_device *udev, struct dvb_usb_device_properties *props,
struct dvb_usb_device_description **desc, int *cold);
extern int dib0700_device_count;
+extern int dvb_usb_dib0700_ir_proto;
extern struct dvb_usb_device_properties dib0700_devices[];
extern struct usb_device_id dib0700_usb_id_table[];
+
#endif
diff -r 127f67dea087 linux/drivers/media/dvb/dvb-usb/dib0700_core.c
--- a/linux/drivers/media/dvb/dvb-usb/dib0700_core.c Tue Feb 26 20:43:56 2008 +
+++ b/linux/drivers/media/dvb/dvb-usb/dib0700_core.c Sun Mar 02 20:30:41 2008 +0100
@@ -13,7 +13,7 @@ module_param_named(debug,dvb_usb_dib0700
module_param_named(debug,dvb_usb_dib0700_debug, int, 0644);
MODULE_PARM_DESC(debug, set debugging level (1=info,2=fw,4=fwdata,8=data (or-able)). DVB_USB_DEBUG_STATUS);
-static int dvb_usb_dib0700_ir_proto = 1;
+int dvb_usb_dib0700_ir_proto = 1;
module_param(dvb_usb_dib0700_ir_proto, int, 0644);
MODULE_PARM_DESC(dvb_usb_dib0700_ir_proto, set ir protocol (0=NEC, 1=RC5 (default), 2=RC6).);
@@ -261,7 +261,7 @@ int dib0700_streaming_ctrl(struct dvb_us
return dib0700_ctrl_wr(adap-dev, b, 4);
}
-static int dib0700_rc_setup(struct dvb_usb_device *d)
+int dib0700_rc_setup(struct dvb_usb_device *d)
{
u8 rc_setup[3] = {REQUEST_SET_RC, dvb_usb_dib0700_ir_proto, 0};
int i = dib0700_ctrl_wr(d, rc_setup, 3);
diff -r 127f67dea087 linux/drivers/media/dvb/dvb-usb/dib0700_devices.c
--- a/linux/drivers/media/dvb/dvb-usb/dib0700_devices.c Tue Feb 26 20:43:56 2008 +
+++ b/linux/drivers/media/dvb/dvb-usb/dib0700_devices.c Sun Mar 02 20:30:41 2008 +0100
@@ -301,6 +301,9 @@ static int stk7700d_tuner_attach(struct
static u8 rc_request[] = { REQUEST_POLL_RC, 0 };
+/* Number of keypresses to ignore before start repeating */
+#define RC_REPEAT_DELAY 2
+
static int dib0700_rc_query(struct dvb_usb_device *d, u32 *event, int *state)
{
u8 key[4];
@@ -314,18 +317,67 @@ static int dib0700_rc_query(struct dvb_u
err(RC Query Failed);
return -1;
}
+
+ /* losing half of KEY_0 events from Philipps rc5 remotes.. */
if (key[0]==0 key[1]==0 key[2]==0 key[3]==0) return 0;
- if (key[3-1]!=st-rc_toggle) {
+
+ /* info(%d: %2X %2X %2X %2X,dvb_usb_dib0700_ir_proto,(int)key[3-2],(int)key[3-3],(int)key[3-1],(int)key[3]); */
+
+ dib0700_rc_setup(d); /* reset ir sensor data to prevent false events */
+
+ switch (dvb_usb_dib0700_ir_proto) {
+ case 0: {
+ /* NEC protocol sends repeat code as 0 0 0 FF */
+ if ((key[3-2] == 0x00) (key[3-3] == 0x00)
+ (key[3] == 0xFF)) {
+ st-rc_counter++;
+ if(st-rc_counter RC_REPEAT_DELAY) {
+*event = d-last_event;
+*state = REMOTE_KEY_PRESSED;
+st-rc_counter = RC_REPEAT_DELAY;
+ }
+ return 0;
+ }
for (i=0;id-props.rc_key_map_size; i++) {
if (keymap[i].custom == key[3-2] keymap[i].data == key[3-3]) {
+st-rc_counter = 0;
*event = keymap[i].event;
*state = REMOTE_KEY_PRESSED;
-st-rc_toggle=key[3-1];
+d-last_event = keymap[i].event;
return 0;
}
}
- err(Unknown remote controller key : %2X %2X,(int)key[3-2],(int)key[3-3]);
- }
+ break;
+ }
+ default: {
+ /* RC-5 protocol changes toggle bit on new keypress */
+ for (i=0;id-props.rc_key_map_size; i++) {
+ if
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] Nova-T 500 issues - losing one tuner
[EMAIL PROTECTED] wrote: Not sure if this helps or adds that much to the discussion... (I think this was concluded before) But I finally switched back to kernel 2.6.22.19 on March 5th (with current v4l-dvb code) and haven't had any problems with the Nova-t 500 since. Running mythtv with EIT scanning enabled. Is this a distribution kernel, or one built from virgin (i.e. unmodified from www.kernel.org or one of the mirrors) source code? Is there any possibility of you uploading your .config file somewhere? I'm curious what kernel options you have set.. especially USB_SUSPEND (USB autosuspend -- not sure if this was added to 2.6.24 or if .22 had it as well; I don't have a .22 source tree at the moment). I'm building a kernel from the 2.6.24.2 virgin source on Ubuntu to do some testing; I'd like to prove that the problem exists in 2.6.24 proper before screaming kernel bug. But if 2.6.22 works, a bug is looking more and more likely. Thanks, -- 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 Tue, 2008-03-11 at 22:03 +, Philip Pemberton wrote: [EMAIL PROTECTED] wrote: Not sure if this helps or adds that much to the discussion... (I think this was concluded before) But I finally switched back to kernel 2.6.22.19 on March 5th (with current v4l-dvb code) and haven't had any problems with the Nova-t 500 since. Running mythtv with EIT scanning enabled. Is this a distribution kernel, or one built from virgin (i.e. unmodified from www.kernel.org or one of the mirrors) source code? Is there any possibility of you uploading your .config file somewhere? I'm curious what kernel options you have set.. especially USB_SUSPEND (USB autosuspend -- not sure if this was added to 2.6.24 or if .22 had it as well; I don't have a .22 source tree at the moment). I'm building a kernel from the 2.6.24.2 virgin source on Ubuntu to do some testing; I'd like to prove that the problem exists in 2.6.24 proper before screaming kernel bug. But if 2.6.22 works, a bug is looking more and more likely. My Ubuntu-provided 2.6.22 works fine. And I am not losing any tuner. Not even with the Multirec of MythTV 0.21. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] dvb fronted: LOCK but no data received.
Hi, I'd like to understand the behavior and meaning of the LOCK returned by the fronted. If I open the fronted in readonly, and ask for the INFO, it is possible that I get a LOCK but no data is actually received. This because the fronted receives data ONLY while it is opened in READ/WRITE. In dvb_frontend.c, in dvb_frontend_open, the fronted is started via dvb_frontend_start only if it opened in READ/WRITE. I see it as a misbehavior: 1) either a LOCK should NOT be returned 2) or the frontend should be started in any case (even if READ only) Which ioctl call should I use to know if the fronted is currently active? ___ 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 5:05 PM, Jarryd Beck [EMAIL PROTECTED] wrote: 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. This helps. I can tell that your tda18211 is located at 0xC0, and it contains 0x83 in its ID register. This is the same ID byte that the tda18271c1 uses to identify itself -- hopefully that implies driver compatability, but we won't know for sure until you try it. The windows driver is only using the primary sixteen registers -- I don't know if the device even HAS the 23 extended registers that the tda18271 has... The driver that you're running does not seem to touch the extended registers at all. It's possible that the driver is simply blasting the register bytes to the tuner, without doing any calibration explicitly -- that could explain the 16 byte blasts without any transactions to the extended registers not sure -- this is all speculation. 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 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova T-500 detection problem
You will need to edit linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h Genius! Thank you very much! I changed line 127 from #define USB_PID_HAUPPAUGE_NOVA_T_5000x9941 To #define USB_PID_HAUPPAUGE_NOVA_T_5000x9940 and it worked perfectly. A proper dev should probably confirm. If you need any more information on this card to make it supported out of the box, let me know! Thanks again, Ian Internal Virus Database is out-of-date. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.21.4 - Release Date: 03/03/2008 00:00 ___ 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
Jarryd Beck wrote: 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. 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. I don't know how the AF9015 works, but Antti does. What demod is on this device? ...or is that part of the AF9015? After googling some more, I found that the tda18211 supports DVB-T, ATSC and QAM ... Seems to be a digital-only tuner, while the tda18271 supports both digital and analog. The IF frequencies used for the tda18211 are the same as the default settings for the tda18271c1. - QAM: IF output centered at 4 and 5 MHz (bandwidth = 6 and 8 MHz respectively) - DVB-T: IF output centered at 3.3, 3.8 and 4.3 MHz (bandwidth = 6, 7 and 8MHz respectively) - ATSC: IF output centered at 3.25 MHz (bandwidth = 6MHz) ...I am looking at the snoop log some more -- My earlier statement was wrong -- I *do* see the driver programming all 39 registers, and now I do see calibration transactions taking place. I can see from this snoop that the value that belongs in the linux driver's std_bits parameter should be 0x19. It looks like the windows driver starts off with 0x18, and after some wiggling, locks at 0x19. Maybe it is first trying to tune to a 7 MHz DVB-T channel, then changes to 8 MHz. You said that you tuned to channel 7, sydney, australia -- is that an 8 MHz channel? What frequency is it on? -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 said that you tuned to channel 7, sydney, australia -- is that an 8 MHz channel? What frequency is it on? Australia uses 7MHz channels in VHF and UHF. - Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] v4l-dvb won't compile on Linux kernel 2.6.24.
Hi, list I wanted to try my television card on slax Linux which uses Linux 2.6.24 as its kernel. And I compiled my downloaded v4l-dvb on slax, but unfortunately, it won't compile. From the dmesg, I noticed that Linux i2c core and Linux v4l2 have some changes. Such as struct video_device and struct i2c_client. So, what should I do to make my v4l-dvb compiled under the newest Linux kernel. Thanks in advance. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re : TT S2-3200 vlc streaming
On 03/11/2008 02:27:31 AM, Vladimir Prudnikov wrote: I'm getting late buffers with vlc on some transponders (DVB-S, same parameters, good signal guaranteed) while everything is fine with others. Using multiproto and TT S2-3200. Anyone having same problems? Yep same here: some transponders give me perfect picture, others are corrupted and another one just does not lock reliably. I observed that the bad ones have higher frequencies in the 116550+ MHz. HTH Bye Manu ___ 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
[linux-dvb] KWorld ATSC 120 - Ubuntu DVB drivers?
I asked on IRC about the KWorld ATSC 120 tuner and was told it isn't supported currently however it could be made to work. I was also informed that all the pre-requisites are finally there, and all that is needed is glue code. Could anybody offer advice on obtaining or developing this glue code? I have minimal experience in unix programming but am always willing to learn new things. Thank you. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KWorld ATSC 120 - Ubuntu DVB drivers?
On Tuesday 11 March 2008 10:50:43 pm TaRDy eyedontcheat wrote: I asked on IRC about the KWorld ATSC 120 tuner and was told it isn't supported currently however it could be made to work. I was also informed that all the pre-requisites are finally there, and all that is needed is glue code. This card is not yet supported, but the individual chips on it do have driver code. Mauro is working on the driver while I do the testing, since I also have one of these cards. Right now though, the composite and S-video inputs work fine in the mainstream kernel (2.6.24 and up). I believe recent additions to the v4l-dvb repository have already incorporated the code changes that make the FM radio work, also. The TV tuner code isn't ready, but its close. Specifically, the analog TV side is already partially working (we've got reliable video, just no audio yet), and the ATSC/digital tuner *wants* to work, but something is tripping us up. I have a feeling that it'll be working fairly soon. SO if you can justify getting the card before the driver is ready, please do so - more testers are always appreciated. -- Life is full of happy and sad events. If you take the time to concentrate on the former, you'll get further in life. Vanessa Ezekowitz [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
