Re: [PATCH] Compro S350 GPIO change
2010/1/17 JD Louw jd.l...@mweb.co.za: Hi, This patch enables LNB power on newer revision d1 Compro S350 and S300 DVB-S cards. While I don't have these cards to test with I'm confident that this works. See http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/7471 and http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/14296 and new windows driver as reference. Signed-off-by: JD Louw jd.l...@mweb.co.za diff -r 59e746a1c5d1 linux/drivers/media/video/saa7134/saa7134-cards.c --- a/linux/drivers/media/video/saa7134/saa7134-cards.c Wed Dec 30 09:10:33 2009 -0200 +++ b/linux/drivers/media/video/saa7134/saa7134-cards.c Sun Jan 17 14:51:07 2010 +0200 @@ -7037,8 +7037,8 @@ int saa7134_board_init1(struct saa7134_d break; case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; - saa_andorl(SAA7134_GPIO_GPMODE0 2, 0x8000, 0x8000); - saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0x8000, 0x8000); + saa_andorl(SAA7134_GPIO_GPMODE0 2, 0xC000, 0xC000); + saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0xC000, 0xC000); break; } return 0; -- Hi Jan, This does not fix the problem where the card is suppose to suspend and the Voltage drops to 0V? Do you still require the windows registry reference for this part? -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
SoC Realtek RTD 12xx devices
Hi, is there anyone that has started to work on Realtek RTD 1261 (http://rtd1261.wikidot.com/internals), 1283 etc type systems? Here is the kernel of RTD 1283 http://gator884.hostgator.com/~xtreamer/Xtreamer_GPL/xtr_kernel.tar.bz2 I would like to know if what they gave is enough to use encoder/decoder/osd capabilities. Or would this be the wrong mailing list to ask, if so please direct me to where I should ask. Thanks, Theunis -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Fwd: Compro S300 - ZL10313
2010/1/2 JD Louw jd.l...@mweb.co.za: On Sat, 2010-01-02 at 09:39 +0200, Theunis Potgieter wrote: 2010/1/1 JD Louw jd.l...@mweb.co.za: On Tue, 2009-12-29 at 23:23 +0200, Theunis Potgieter wrote: Hi mailing list, I have a problem with my Compro S300 pci card under Linux 2.6.32. I cannot tune with this card and STR/SNRA is very bad compared to my Technisat SkyStar 2 pci card, connected to the same dish. I have this card and are willing to run tests, tested drivers etc to make this work. I currently load the module saa7134 with options: card=169 I enabled some debug parameters on the saa7134, not sure what else I should enable. Please find my dmesg log attached. lsmod shows : # lsmod Module Size Used by zl10039 6268 2 mt312 12048 2 saa7134_dvb 41549 11 saa7134 195664 1 saa7134_dvb nfsd 416819 11 videobuf_dvb 8187 1 saa7134_dvb dvb_core 148140 1 videobuf_dvb ir_common 40625 1 saa7134 v4l2_common 21544 1 saa7134 videodev 58341 2 saa7134,v4l2_common v4l1_compat 24473 1 videodev videobuf_dma_sg 17830 2 saa7134_dvb,saa7134 videobuf_core 26534 3 saa7134,videobuf_dvb,videobuf_dma_sg tveeprom 12550 1 saa7134 thermal 20547 0 processor 54638 1 # uname -a Linux vbox 2.6.32-gentoo #4 Sat Dec 19 00:54:19 SAST 2009 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux Thanks, Theunis Hi, It's probably the GPIO settings that are wrong for your SAA7133 based card revision. See http://osdir.com/ml/linux-media/2009-06/msg01256.html for an explanation. For quick confirmation check if you have 12V - 20V DC going to your LNB. The relevant lines of code is in ~/v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c: case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; saa_andorl(SAA7134_GPIO_GPMODE0 2, 0x8000, 0x8000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0x8000, 0x8000); break; Hi thanks for the hint. I changed it to the following: case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; saa_andorl(SAA7134_GPIO_GPMODE0 2, 0xc000, 0xc000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0xc000, 0xc000); break; I now get the same SNR as on my skystar2 card, signal is still indicating 17% where as the skystar2 would show 68%. At least I'm getting a LOCK on channels :) Thanks! Looking at your log, at least the demodulator and tuner is responding correctly. You can see this by looking at the i2c traffic addressed to 0x1c (demodulator) and 0xc0 (tuner). Attached is a dmesg trace from my working SAA7130 based card. Regards JD Hi, Just to clarify, can you now watch channels? At the moment the signal strength measurement is a bit whacked, so don't worry too much about it. I also get the 75%/17% figures you mentioned when tuning to strong signals. The figure is simply reported wrongly: even weaker signals should tune fine. If you want you can have a look in ~/v4l-dvb/linux/drivers/media/dvb/frontends/mt312.c at mt312_read_signal_strength(). Also, if you have a multimeter handy, can you confirm that the 0xc000 GPIO fix enables LNB voltage? I'd like to issue a patch for this. I've already tested this on my older card with no ill effect. This is what happened when I started vdr. Vertical gave a Volt reading between 13.9 and 14.1, Horizontal Gave 19.4 ~ 19.5. When I stopped vdr, the Voltage went back to 14V. I thought that it would read 0V. What is suppose to happen? Theunis Regards JD -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Fwd: Compro S300 - ZL10313
2010/1/2 JD Louw jd.l...@mweb.co.za: On Sat, 2010-01-02 at 09:39 +0200, Theunis Potgieter wrote: 2010/1/1 JD Louw jd.l...@mweb.co.za: On Tue, 2009-12-29 at 23:23 +0200, Theunis Potgieter wrote: Hi mailing list, I have a problem with my Compro S300 pci card under Linux 2.6.32. I cannot tune with this card and STR/SNRA is very bad compared to my Technisat SkyStar 2 pci card, connected to the same dish. I have this card and are willing to run tests, tested drivers etc to make this work. I currently load the module saa7134 with options: card=169 I enabled some debug parameters on the saa7134, not sure what else I should enable. Please find my dmesg log attached. lsmod shows : # lsmod Module Size Used by zl10039 6268 2 mt312 12048 2 saa7134_dvb 41549 11 saa7134 195664 1 saa7134_dvb nfsd 416819 11 videobuf_dvb 8187 1 saa7134_dvb dvb_core 148140 1 videobuf_dvb ir_common 40625 1 saa7134 v4l2_common 21544 1 saa7134 videodev 58341 2 saa7134,v4l2_common v4l1_compat 24473 1 videodev videobuf_dma_sg 17830 2 saa7134_dvb,saa7134 videobuf_core 26534 3 saa7134,videobuf_dvb,videobuf_dma_sg tveeprom 12550 1 saa7134 thermal 20547 0 processor 54638 1 # uname -a Linux vbox 2.6.32-gentoo #4 Sat Dec 19 00:54:19 SAST 2009 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux Thanks, Theunis Hi, It's probably the GPIO settings that are wrong for your SAA7133 based card revision. See http://osdir.com/ml/linux-media/2009-06/msg01256.html for an explanation. For quick confirmation check if you have 12V - 20V DC going to your LNB. The relevant lines of code is in ~/v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c: case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; saa_andorl(SAA7134_GPIO_GPMODE0 2, 0x8000, 0x8000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0x8000, 0x8000); break; Hi thanks for the hint. I changed it to the following: case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; saa_andorl(SAA7134_GPIO_GPMODE0 2, 0xc000, 0xc000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0xc000, 0xc000); break; I now get the same SNR as on my skystar2 card, signal is still indicating 17% where as the skystar2 would show 68%. At least I'm getting a LOCK on channels :) Thanks! Looking at your log, at least the demodulator and tuner is responding correctly. You can see this by looking at the i2c traffic addressed to 0x1c (demodulator) and 0xc0 (tuner). Attached is a dmesg trace from my working SAA7130 based card. Regards JD Hi, Just to clarify, can you now watch channels? Hi Jan, yes I can watch channels on Vivid bouquet, some of which are FTA channels. Here is some channels I can get a lock and a picture on vdr: GodCh;GodCh:11674:vC56M2O0S0:S68.5E:26652:0:0:0:0:110:73:3:0 ASTV;ASTV:11674:vC56M2O0S0:S68.5E:26652:0:0:0:0:111:73:3:0 At the moment the signal strength measurement is a bit whacked, so don't worry too much about it. I also get the 75%/17% figures you mentioned when tuning to strong signals. The figure is simply reported wrongly: even weaker signals should tune fine. If you want you can have a look in ~/v4l-dvb/linux/drivers/media/dvb/frontends/mt312.c at mt312_read_signal_strength(). Also, if you have a multimeter handy, can you confirm that the 0xc000 GPIO fix enables LNB voltage? I'd like to issue a patch for this. I've already tested this on my older card with no ill effect. I will try and do this as soon as possible. Was there any worth while information in the ZL10313 documentation that could assist in setting the correct parameters for my Compro S300? Regards JD Thanks for the assistance :) Theunis -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Fwd: Compro S300 - ZL10313
2010/1/1 JD Louw jd.l...@mweb.co.za: On Tue, 2009-12-29 at 23:23 +0200, Theunis Potgieter wrote: Hi mailing list, I have a problem with my Compro S300 pci card under Linux 2.6.32. I cannot tune with this card and STR/SNRA is very bad compared to my Technisat SkyStar 2 pci card, connected to the same dish. I have this card and are willing to run tests, tested drivers etc to make this work. I currently load the module saa7134 with options: card=169 I enabled some debug parameters on the saa7134, not sure what else I should enable. Please find my dmesg log attached. lsmod shows : # lsmod Module Size Used by zl10039 6268 2 mt312 12048 2 saa7134_dvb 41549 11 saa7134 195664 1 saa7134_dvb nfsd 416819 11 videobuf_dvb 8187 1 saa7134_dvb dvb_core 148140 1 videobuf_dvb ir_common 40625 1 saa7134 v4l2_common 21544 1 saa7134 videodev 58341 2 saa7134,v4l2_common v4l1_compat 24473 1 videodev videobuf_dma_sg 17830 2 saa7134_dvb,saa7134 videobuf_core 26534 3 saa7134,videobuf_dvb,videobuf_dma_sg tveeprom 12550 1 saa7134 thermal 20547 0 processor 54638 1 # uname -a Linux vbox 2.6.32-gentoo #4 Sat Dec 19 00:54:19 SAST 2009 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux Thanks, Theunis Hi, It's probably the GPIO settings that are wrong for your SAA7133 based card revision. See http://osdir.com/ml/linux-media/2009-06/msg01256.html for an explanation. For quick confirmation check if you have 12V - 20V DC going to your LNB. The relevant lines of code is in ~/v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c: case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; saa_andorl(SAA7134_GPIO_GPMODE0 2, 0x8000, 0x8000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0x8000, 0x8000); break; Hi thanks for the hint. I changed it to the following: case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; saa_andorl(SAA7134_GPIO_GPMODE0 2, 0xc000, 0xc000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0xc000, 0xc000); break; I now get the same SNR as on my skystar2 card, signal is still indicating 17% where as the skystar2 would show 68%. At least I'm getting a LOCK on channels :) Thanks! Looking at your log, at least the demodulator and tuner is responding correctly. You can see this by looking at the i2c traffic addressed to 0x1c (demodulator) and 0xc0 (tuner). Attached is a dmesg trace from my working SAA7130 based card. Regards JD -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Fwd: Compro S300 - ZL10313
Hi mailing list, I have a problem with my Compro S300 pci card under Linux 2.6.32. I cannot tune with this card and STR/SNRA is very bad compared to my Technisat SkyStar 2 pci card, connected to the same dish. I have this card and are willing to run tests, tested drivers etc to make this work. I currently load the module saa7134 with options: card=169 I enabled some debug parameters on the saa7134, not sure what else I should enable. Please find my dmesg log attached. Thanks, Theunis dmesg.txt.bz2 Description: BZip2 compressed data
Re: KWorld DVB-T 210 Fails to work on Linux 2.6.31-r6 x86_64
kernel: tda1004x: found firmware revision 20 -- ok now I'm getting this... strange :-| I did nothing different. except to retry the module after a while again. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Request driver for cards
On 14/10/2009, Theunis Potgieter theunis.potgie...@gmail.com wrote: Hi, what is the procedure to request drivers for specific new, perhaps unknown supported cards? I did have a look at http://www.linuxtv.org/wiki/index.php/Main_Page but it didn't contain any information about supported cards. Neither did 2.6.30 /usr/src/linux/Documentation/dvb/cards.txt for the following brands: name, site: Compro, S300 http://www.comprousa.com/en/product/s300/s300.html K-World VS-DVB-S 100/IS, http://global.kworld-global.com/main/prod_in.aspx?mnuid=1248modid=6pcid=46ifid=16prodid=98 Perhaps I shouldn't waste time if I could find a dual/twin tuner card for dvb-s or dvb-s2. Are there any recommended twin-tuner pci-e cards that is support and can actually be bought by the average consumer? Thanks I guess this answers the Kworld on 2.6.30: /usr/src/linux/drivers/media/dvb/frontends/cx24123.c: * Support for KWorld DVB-S 100 by Vadim Catana skys...@moldova.cc But how would I get compro S300 support? Is there anybody that knows of a work inprogress or completed twin tuner type card in either pci or pci-e format? Thanks in advance. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [linux-dvb] request driver for cards
On 15/10/2009, H. Langos henrik-...@prak.org wrote: On Wed, Oct 14, 2009 at 03:07:00PM +0200, Theunis Potgieter wrote: Hi, what is the procedure to request drivers for specific new, perhaps unknown supported cards? The procedure is to hit google with something like linux vendor model and see what you find. :-) I meant to say: Where do I ask for a new driver to be written for an unsupported card. Or Perhaps the card is already supported and I just couldn't see it from a singular view. (linuxtv.org, mailing list, Google) Especially links to mailing list archives like linux-media and linux-dvb are worth a read. I joined linux-...@linuxtv.org recently and I was informed that the mailing list is deprecated and I should join this mailing list instead. (you will see my first mail on their list too) Perhaps I shouldn't waste time if I could find a dual/twin tuner card for dvb-s or dvb-s2. Are there any recommended twin-tuner pci-e cards that is support and can actually be bought by the average consumer? Did you risk a look at any of those? http://www.linuxtv.org/wiki/index.php/DVB-S_PCI_Cards http://www.linuxtv.org/wiki/index.php/DVB-S_PCIe_Cards http://www.linuxtv.org/wiki/index.php/DVB-S2_PCI_Cards http://www.linuxtv.org/wiki/index.php/DVB-S2_PCIe_Cards I did visit those, and I couldn't find any sellers of the twin tuner cards on http://www.linuxtv.org/wiki/index.php/DVB-S2_PCIe_Cards :( They would be perfect. Exept I can't find where to buy these. Perhaps they are re-branded and somebody here knows this already? This site http://www.linuxtv.org/wiki/index.php/DVB-S_PCI_Cards does not list the Compro S300 neither the KWorld dvb-s 100. I just happened to grep -i kworld /usr/src/linux/drivers/media/dvb/*/* and found KWorld to be somewhat supported. Great so I know that one. How to approach Compro S300? The problem is this: Either I setup my old penium 3 machine with 5 pci slots (which I try to avoid) or buy a new machine with only 2 pci slots and 2 pci-e 1x slots. The options becomes limited on new machines if you want 4 or more tuners in the same machine. So I need some advice if it is feasible to run 5 dvb-s single tuner cards in a pentium3 or 5 tuners (2 twin tuner cards and single card) on an atom based machine? I suspect they might contain some usable informaion. You should however take into account that most developers don't care to update a bazillion different places after they added support for a particular devices. So in most cases there will be a brief announcment on the developers mailinglist and the code is the documentation. I recently joined this mailing list and will be a lookout for anything related to twin tuner cards sent by developers. Or if somebody knows just reply to this thread. Thanks for the help. cheers -henrik -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Request driver for cards
Hi, what is the procedure to request drivers for specific new, perhaps unknown supported cards? I did have a look at http://www.linuxtv.org/wiki/index.php/Main_Page but it didn't contain any information about supported cards. Neither did 2.6.30 /usr/src/linux/Documentation/dvb/cards.txt for the following brands: name, site: Compro, S300 http://www.comprousa.com/en/product/s300/s300.html K-World VS-DVB-S 100/IS, http://global.kworld-global.com/main/prod_in.aspx?mnuid=1248modid=6pcid=46ifid=16prodid=98 Perhaps I shouldn't waste time if I could find a dual/twin tuner card for dvb-s or dvb-s2. Are there any recommended twin-tuner pci-e cards that is support and can actually be bought by the average consumer? Thanks -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html