Re: femon.c
On Wed, Oct 26, 2011 at 9:19 PM, James bjloc...@lockie.ca wrote: I'm trying to find femon.c I found a reference to it on the web (DVB-apps/szap//femon/.c) but I can't find it. :-( Try this repository. http://linuxtv.org/hg/dvb-apps/ HTH Jonathan -- 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 -- 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: where can I report dvb module related bug reports?
On Sun, Nov 28, 2010 at 5:06 PM, Halim Sahin halim.sa...@freenet.de wrote: Hi, Sorry folks I know that dvb driver development is done in your spare time. However posting to this list or linux-dvb I got no answers which is really frustrating :-(. Please can you tell me which is the prefered way for submitting bug reports to dvb driver developers? Hi I am not developer however been on this list since move. This is the appropriate list. However I search my archive(gmail account) and I didn't get them. I find it interesting that they are in the mail-archive archive. I would assume something may have happened with the mail server. Hopefully as this reply shows you will get your help. Later Jonathan Please can you help with the following things: http://www.mail-archive.com/linux-media@vger.kernel.org/msg12758.html http://www.mail-archive.com/linux-media@vger.kernel.org/msg21646.html THX Regards halim -- 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 -- ASUS M4A78 PRO motherboard Athlon II X4 640 Processor 4 Gigabytes of DDR2-800 Gigabyte nVidia 9400gt Graphics adapter KWorld ATSC 110 TV Capture Card KWorld ATSC 115 TV Capture Card -- 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: ibmcam (xrilink_cit) and konica webcam driver porting to gspca update
On Sun, Jul 4, 2010 at 6:29 AM, Hans de Goede hdego...@redhat.com wrote: Hi all, I've finished porting the usbvideo v4l1 ibmcam and konicawc drivers to gspcav2. The ibmcam driver is replaced by gspca_xirlink_cit, which also adds support for 2 new models (it turned out my testing cams where not supported by the old driver). This one could use more testing. I just tried using your driver. I get no video. using 2.6.35.3. Had to patch usb_buffer_[alloc free] otherwise no changes to your tree. /usr/bin/qv4l2 /dev/video2 Start Capture: Input/output error VIDIOC_STREAMON: Input/output error Start Capture: Input/output error VIDIOC_STREAMON: Input/output error -- info Model 2 KSX-X9903 0x0545 0x8080 3.0a Old, cheaper model Xirlink C-It /usr/sbin/v4l2-dbg -d /dev/video2 -D Driver info: Driver name : xirlink-cit Card type : USB IMAGING DEVICE Bus info : usb-:00:12.2-6.1 Driver version: 133376 Capabilities : 0x0501 Video Capture Read/Write Streaming Any Ideas Jonathan The konicawc driver is replaced by gspca_konica which is pretty much finished. You can get them both here: http://linuxtv.org/hg/~hgoede/ibmcam Once Douglas updates the hg v4l-dvb tree to be up2date with the latest and greatest from Mauro, then I'll rebase my tree (the ibmcam driver needs a very recent gspca core patch), and send a pull request. Regards, Hans p.s. 1) Many thanks to Patryk Biela for providing me a konica driver using camera. 2) Still to do the se401 driver. 3) I'll be on vacation the coming week and not reading email. -- 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 -- ASUS m3a78 motherboard AMD Athlon64 X2 Dual Core Processor 6000+ 3.1Ghz 2 Gigabytes of DDR2-800 Gigabyte nVidia 9400gt Graphics adapter KWorld ATSC 110 TV Capture Card KWorld ATSC 115 TV Capture Card -- 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
nxt200x: Timeout waiting for nxt2004 to init.
Just a quick question. I have an Kworld atsc 110 and 115. after 2 1/2 days I have 1624 dmesg Timeout waiting for nxt2004 to init lines. My understanding is once something in inititialize you shouldn't need to do it again. is the a reason it needs to init repeatedly? The cards are functioning fine with mythtv. Thanks Jonathan Sample with timing ---8-- [211844.717390] nxt200x: Timeout waiting for nxt2004 to init. [211864.496286] nxt200x: Timeout waiting for nxt2004 to init. [211890.602194] nxt200x: Timeout waiting for nxt2004 to init. [211904.394297] nxt200x: Timeout waiting for nxt2004 to init. [211924.747026] nxt200x: Timeout waiting for nxt2004 to init. [212302.550277] nxt200x: Timeout waiting for nxt2004 to init. [212314.356295] nxt200x: Timeout waiting for nxt2004 to init. [212335.245278] nxt200x: Timeout waiting for nxt2004 to init. [212351.161394] nxt200x: Timeout waiting for nxt2004 to init. [212365.098031] nxt200x: Timeout waiting for nxt2004 to init. [212399.819294] nxt200x: Timeout waiting for nxt2004 to init. [212435.198162] nxt200x: Timeout waiting for nxt2004 to init. [212442.446145] nxt200x: Timeout waiting for nxt2004 to init. [212446.674303] nxt200x: Timeout waiting for nxt2004 to init. [212460.008295] nxt200x: Timeout waiting for nxt2004 to init. [212461.655279] nxt200x: Timeout waiting for nxt2004 to init. [212465.454277] nxt200x: Timeout waiting for nxt2004 to init. [212498.875026] nxt200x: Timeout waiting for nxt2004 to init. [212514.791276] nxt200x: Timeout waiting for nxt2004 to init. [212520.409467] nxt200x: Timeout waiting for nxt2004 to init. [212533.584468] nxt200x: Timeout waiting for nxt2004 to init. [212537.880279] nxt200x: Timeout waiting for nxt2004 to init. [213510.585294] nxt200x: Timeout waiting for nxt2004 to init. [213526.196301] nxt200x: Timeout waiting for nxt2004 to init. [213549.076155] nxt200x: Timeout waiting for nxt2004 to init. [213553.143013] nxt200x: Timeout waiting for nxt2004 to init. [213561.282205] nxt200x: Timeout waiting for nxt2004 to init. [213612.284277] nxt200x: Timeout waiting for nxt2004 to init. [213617.087032] nxt200x: Timeout waiting for nxt2004 to init. [213624.669319] nxt200x: Timeout waiting for nxt2004 to init. [213626.324344] nxt200x: Timeout waiting for nxt2004 to init. [213720.884172] nxt200x: Timeout waiting for nxt2004 to init. [213731.081026] nxt200x: Timeout waiting for nxt2004 to init. [213754.500280] nxt200x: Timeout waiting for nxt2004 to init. [213761.917152] nxt200x: Timeout waiting for nxt2004 to init. [214210.566403] nxt200x: Timeout waiting for nxt2004 to init. [214218.086204] nxt200x: Timeout waiting for nxt2004 to init. [214226.801295] nxt200x: Timeout waiting for nxt2004 to init. [214227.838212] nxt200x: Timeout waiting for nxt2004 to init. [214247.973356] nxt200x: Timeout waiting for nxt2004 to init. [214250.661033] nxt200x: Timeout waiting for nxt2004 to init. [214271.082031] nxt200x: Timeout waiting for nxt2004 to init. [214273.469366] nxt200x: Timeout waiting for nxt2004 to init. [214281.378038] nxt200x: Timeout waiting for nxt2004 to init. [214363.528204] nxt200x: Timeout waiting for nxt2004 to init. [214375.779286] nxt200x: Timeout waiting for nxt2004 to init. [214410.896042] nxt200x: Timeout waiting for nxt2004 to init. [214450.769296] nxt200x: Timeout waiting for nxt2004 to init. [214454.652042] nxt200x: Timeout waiting for nxt2004 to init. [214457.722314] nxt200x: Timeout waiting for nxt2004 to init. [214518.751148] nxt200x: Timeout waiting for nxt2004 to init. [215357.898211] nxt200x: Timeout waiting for nxt2004 to init. [215364.899033] nxt200x: Timeout waiting for nxt2004 to init. [215370.457203] nxt200x: Timeout waiting for nxt2004 to init. [215386.914171] nxt200x: Timeout waiting for nxt2004 to init. [215392.677279] nxt200x: Timeout waiting for nxt2004 to init. [215410.894040] nxt200x: Timeout waiting for nxt2004 to init. [215420.185278] nxt200x: Timeout waiting for nxt2004 to init. [215449.908211] nxt200x: Timeout waiting for nxt2004 to init. [215464.256277] nxt200x: Timeout waiting for nxt2004 to init. [215479.878277] nxt200x: Timeout waiting for nxt2004 to init. [215496.286193] nxt200x: Timeout waiting for nxt2004 to init. [215503.028286] nxt200x: Timeout waiting for nxt2004 to init. [215514.881166] nxt200x: Timeout waiting for nxt2004 to init. [215543.269221] nxt200x: Timeout waiting for nxt2004 to init. [215561.433213] nxt200x: Timeout waiting for nxt2004 to init. [215596.010294] nxt200x: Timeout waiting for nxt2004 to init. [215641.442934] nxt200x: Timeout waiting for nxt2004 to init. [215642.540277] nxt200x: Timeout waiting for nxt2004 to init. [215643.524211] nxt200x: Timeout waiting for nxt2004 to init. [215650.046294] nxt200x: Timeout waiting for nxt2004 to init. -- 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
Re: [linux-dvb] EPG (Electronic Program Guide) Tools
On Tuesday, May 26, 2009, Devin Heitmueller dheitmuel...@kernellabs.com wrote: On Tue, May 26, 2009 at 1:51 PM, Chris Capon ttab...@gmail.com wrote: Hi: I've installed an HVR-1600 card in a Debian system to receive ATSC digital broadcasts here in Canada. Everything works great. scan /usr/share/dvb/atsc/us-ATSC-center-frequencies-8VSB channels.conf finds a complete list of broadcasters. azap -c channels.conf -r channel-name tunes in the stations and displays signal strength info. cp /dev/dvb/adapter0/dvr0 xx.mpg captures the output stream which can be played by mplayer. What I'm missing is information about the Electronic Program Guide (EPG). There doesn't seem to be much info on linuxtv.org on how to read it. Where does the EPG come from? Is it incorporated into the output stream through PID's some how or is it read from one of the other devices under adapter0? Are there simple command line tools to read it or do you have to write a custom program to interpret it somehow? Could someone please point me in the right direction to get started? If no tools exist, perhaps links to either api or lib docs/samples? Much appreciated. Chris. Hello Chris, The ATSC EPG is sent via the ATSC PSIP protocol. I do not know of any tools currently available to extract the information. MeTV has a working implementation (with some bugs I have seen), and I was looking at getting it to work in Kaffeine at some point. Dvbstreamer supports atsc epg. That is what i use The spec is freely available here: http://www.atsc.org/standards/a_65cr1_with_amend_1.pdf If you have any questions, feel free to drop me a line. Cheers, Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com ___ linux-dvb users mailing list For V4L/DVB development, please use instead linux-media@vger.kernel.org linux-...@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- ASUS m3a78 mothorboard AMD Athlon64 X2 Dual Core Processor 6000+ 3.1Ghz 4 Gigabytes of memory Gigabyte NVidia 9400gt Graphics adapter Kworld ATSC 110 TV Capture Card Kworld ATSC 115 TV Capture Card -- 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] EPG (Electronic Program Guide) Tools
On Tue, May 26, 2009 at 2:31 PM, Devin Heitmueller dheitmuel...@kernellabs.com wrote: On Tue, May 26, 2009 at 3:18 PM, Jonathan Isom jei...@gmail.com wrote: Dvbstreamer supports atsc epg. That is what i use Well, learn something new every day. I didn't realize dvbstreamer had ATSC support. Yep. Don't confuse with dvbstream. Separate apps. with dvbstreamer you have to cycle the channels with a script to fill the data for each channel. Later Jonathan Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- ASUS m3a78 mothorboard AMD Athlon64 X2 Dual Core Processor 6000+ 3.1Ghz 4 Gigabytes of memory Gigabyte NVidia 9400gt Graphics adapter Kworld ATSC 110 TV Capture Card Kworld ATSC 115 TV Capture Card -- 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: Kworld atsc 110 nxt2004 init
On Sun, Feb 22, 2009 at 8:45 PM, Jonathan Isom jei...@gmail.com wrote: On Sun, Feb 22, 2009 at 2:43 PM, CityK ci...@rogers.com wrote: Jonathan Isom wrote: Hi I was looking over my logs and I'm wondering is nxt200x: Timeout waiting for nxt2004 to init common HI all I am not sure if this is actually related to my lockups, however I think I may have figured out something. If I boot my system with clocksource equal to hpet it occurs right after boot(~8secs in), but if I set it to jiffies I don't see it(note early testing, may still end up occuring). In nxt2004_microcontroller_init there is a msleep(10) and I'm wondering if 200 msec(loop) is long enough. Any Thoughts? Jonathan No its not common or is this womething I need to worry about. I got one shortly before a lockup(No backtrace). Nothing was doing other than dvbstreamer sitting idle. I'll provide further logs if it should be needed. I would think that It would need to only be initialize at module load. Am I wrong in this thinking? in kernel drivers 2.6.28.4 Hi Looking at the logs I found that there was a backtrace. However I believe it is related to dvbstreamer and the kworld cards. I cycle thru the channels to download epg info. The previous crash I forgot that I was running the script to cycle them and export the xmltv data. -- 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: KWorld ATSC 115 all static
On Tue, Feb 10, 2009 at 12:15 AM, Mauro Carvalho Chehab mche...@infradead.org wrote: On Tue, 10 Feb 2009 04:43:15 +0100 hermann pitton hermann-pit...@arcor.de wrote: Am Dienstag, den 10.02.2009, 04:14 +0100 schrieb hermann pitton: Am Dienstag, den 10.02.2009, 00:35 -0200 schrieb Mauro Carvalho Chehab: On Tue, 10 Feb 2009 02:31:00 +0100 hermann pitton hermann-pit...@arcor.de wrote: BTW, just to remember. Tvtime with signal detection on shows a blue screen without signal. With signal detection off, just good old snow. So, the tda9887 or the PLL are configured wrongly. Urgh, not to add more confusion here at least. Good old snow means the analog signal is perfect. I stopped since long to connect a real signal to it surfing the grounds on my stomach, but it is for sure working then and the pll is always fine. Ah, ok. So, now, we just need CityK (or someone else with ATSC 115) to confirm that everything is fine on their side. This patch may also fix other similar troubles on a few devices that seem to need some i2c magic before probing the tuner. Just tried the latest hg and I can confirm that both an ATSC 110 and 115 work with tvtime and ATSC. Later Jonathan Cheers, Mauro -- 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 -- 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: KWorld ATSC 115 all static
On Tue, Feb 10, 2009 at 6:27 AM, Mauro Carvalho Chehab mche...@infradead.org wrote: On Tue, 10 Feb 2009 06:07:51 -0600 Jonathan Isom jei...@gmail.com wrote: On Tue, Feb 10, 2009 at 12:15 AM, Mauro Carvalho Chehab mche...@infradead.org wrote: On Tue, 10 Feb 2009 04:43:15 +0100 hermann pitton hermann-pit...@arcor.de wrote: Am Dienstag, den 10.02.2009, 04:14 +0100 schrieb hermann pitton: Am Dienstag, den 10.02.2009, 00:35 -0200 schrieb Mauro Carvalho Chehab: On Tue, 10 Feb 2009 02:31:00 +0100 hermann pitton hermann-pit...@arcor.de wrote: BTW, just to remember. Tvtime with signal detection on shows a blue screen without signal. With signal detection off, just good old snow. So, the tda9887 or the PLL are configured wrongly. Urgh, not to add more confusion here at least. Good old snow means the analog signal is perfect. I stopped since long to connect a real signal to it surfing the grounds on my stomach, but it is for sure working then and the pll is always fine. Ah, ok. So, now, we just need CityK (or someone else with ATSC 115) to confirm that everything is fine on their side. This patch may also fix other similar troubles on a few devices that seem to need some i2c magic before probing the tuner. Just tried the latest hg and I can confirm that both an ATSC 110 and 115 work with tvtime and ATSC. Jonathan, You tried the latest tree at http://linuxtv.org/hg/v4l-dvb or my saa7134 tree (http://linuxtv.org/hg/~mchehab/saa7134)? In the first case, could you please confirm that it works fine also with the saa7134 tree? Hi I can confirm they work with both trees. Later Jonathan Later Jonathan Cheers, Mauro -- 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 Cheers, Mauro -- 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
