Re: USB Wintv HVR-900 Hauppauge
Em Wed, 19 Aug 2009 13:16:23 -0400 Devin Heitmueller dheitmuel...@kernellabs.com escreveu: Unfortunately, it is not clear when/if Mauro will ever get back to getting that bridge to a supported state (it hasn't had any active development in over nine months). This is a recorrent question, already discussed at the ML. Probably, I should update the wiki. The driver is still on my TODO list. I intend to return back to it, but this is not on my current top priorities. Those chips are very buggy and they behave badly if the driver doesn't do exactly the same thing as the original one (it starts to loose frames). I suspect that this is a firmware bug at tm6000/tm6010, although I'm not sure. Maybe the conversion of the driver to the new i2c approach could help to fix this issue, since this will avoid sending probing packets at i2c bus. Also, on all tests we've done so far, it can't reliably read data from an i2c device. This prevents that tools like scan to properly detect the signal strength of a channel. You can't even be sure if xc3028 firmware were successfully loaded on this device, due to this issue. It is important to notice that the vendor (Trident) doesn't seem to want helping with open source development. I tried during 2007 and 2008 to get their help by opening docs to me, via Linux Foundation NDA program, without success. Currently, they are refusing so far to help with their demod DRX-K line that they acquired from Micronas (as pointed at http://linux.terratec.de/tv_en.html). In brief, while I want to fix the driver issues, I recommend to avoid buying any devices with tm5600/tm6000/tm6010 (and DRX demod) chips. There are other offers at the market with drivers that work properly, including some nice HVR devices that are fully supported. 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
Re: Philips webcam support
Hi, On Thursday 20 August 2009 16:48:16 Rath wrote: are the Philips SPC1330NC and SPC2050NC supported by v4l? The SPC1330NC is supported by the uvcvideo driver. I haven't heard about the SPC2050NC yet. My guess is that it would be a UVC device as well. Could you please post the output of lsusb -v for your camera (using usbutils 0.72 or newer, 0.73+ preferred) ? Thanks. Can I get higher framerates than 30fps (The webcam supports framerates up to 90fps)? Not with the SPC1330NC. 90fps is just a marketing claim achieved by software interpolation. The camera itself supports frame rates up to 30fps. I want to use one of them with a Beagleboard when they are supported. -- Regards, Laurent Pinchart -- 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] Anysee E30 C Plus + MPEG-4?
Thanks for the advice, it worked! mplayer -identify dvb://channel name produced the following result: PROGRAM_ID=0 (0x00), PMT_PID: 16(0x10) PROGRAM_ID=109 (0x6D), PMT_PID: 7029(0x1B75) PROGRAM_ID=1001 (0x3E9), PMT_PID: 59(0x3B) PROGRAM_ID=1930 (0x78A), PMT_PID: 1930(0x78A) PROGRAM_ID=15551 (0x3CBF), PMT_PID: 8021(0x1F55) I was searching for the HD channel with program id 15551, so I added +8021 to the video identifier in channels.conf and it works. regards s. BOUWSMA Barry: I said it before and I'll say it again, what `mplayer' needs is -- I mean, I don't know if it would be possible for `mplayer' to identify the video as H.264, but for me, it needs this additional PID stream to do that. That is something for the `mplayer' developers or for someone more familiar with H.264 in DVB to answer. I'm guessing your `channels.conf' file is simple with one field for video and one for audio, but no extra fields. If this is the case, then what you will need to do as a test would be to write more of the stream to a file; the example I gave in my earlier reply for BBC-HD is what I pass to `dvbstream'. Then `mplayer' should be able to play this file with no problems. --- | Make it idiot proof and someone will make a better idiot. | --- -- 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] USB technotrend CT-3650
Hi, I can confirm DVB-C does not work. Tried with Kaffine and a custom transponder list for my aera and with w_scan which takes an age to change between frequencies. Chris / Christopher J. Thornley is c...@coolrose.fsnet.co.uk ( //--, (*)OXOXOXOXO(*=*=O=S=U=0=3=6=*=- ( \\--' \ Home Page :-http://www.coolrose.fsnet.co.uk -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of Bert Haverkamp Sent: 19 August 2009 21:17 To: linux-media@vger.kernel.org Subject: Re: [linux-dvb] USB technotrend CT-3650 Hello Jens, I'm also looking into the CT-3650. I posted a few days back about the support for this device for dvb-c. Are you trying to get dvb-c working or dvb-t? Can anyone else answer if dvb-c is indeed working with current linux? Regards, Bert Wed, Aug 19, 2009 at 8:01 PM, Jens Kjellerupj...@kjellerup-hansen.dk wrote: I am not a developer and my programming skills dates back to the late 1970's where i programmed insurance applications i Cobol - so they are a bit rusty. I have been given a Technotrend connect CT-3650 CI device as a birthday present for my myth server (don't ask for my age). I run Mythbuntu 9.04. I have searched for drivers to get the unit up and running but can't find any. I have read: http://osdir.com/ml/linux-media/2009-03/msg01137.html http://www.mail-archive.com/linux-media@vger.kernel.org/msg08610.html http://www.spinics.net/linux/lists/linux-dvb/msg27678.html and several others, but i haven't found any workable solution. I have tried to follow the recipee on this device - a sister product for dvb-s2 http://linuxtv.org/wiki/index.php/TechnoTrend_TT-connect_S2-3650_CI Up until now i have found no way to get the device running. I have compiled and installed the newest v4l repository with no further luck. I have extracted the newest firmware from the latest BDA files on the the Technotrend site www.tt-pc.de Dmesg only shows that the usb bus is detecting a tehcnotrend device Lsusb shows the same. Can anyone point me in a direction to get it working patches, drivers etc. Alternatively has the community all together given up on this device. Sorry for this non development question but i don't know where else to turn to. If someone would help me i could make the testing and documentation for the linuxtv site. Thank you in advance JK ___ 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 -- - 38 is NOT a random number -- 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
compat.h required to build
Hi, The following files: /linux/drivers/media/dvb/frontends/stb6100.c /linux/drivers/media/dvb/frontends/tda10021.c /linux/drivers/media/dvb/frontends/ves1820.c Fail to build with: error: implicit declaration of function 'DIV_ROUND_CLOSEST' and need the addition of: #include compat.h when building on my system. Is this related to my kernel version (2.6.28) or is it something else? Thanks, Lou -- 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: USB Wintv HVR-900 Hauppauge
On Fri, Aug 21, 2009 at 2:07 AM, Mauro Carvalho Chehabmche...@infradead.org wrote: In brief, while I want to fix the driver issues, I recommend to avoid buying any devices with tm5600/tm6000/tm6010 (and DRX demod) chips. There are other offers at the market with drivers that work properly, including some nice HVR devices that are fully supported. The more I think about it, the more I think we should setup something along the lines of a Wall of Shame on the LinuxTV wiki, so that people will be better informed exactly which products they should not buy because of the chipset vendor's behavior. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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: USB Wintv HVR-900 Hauppauge
On Fri, Aug 21, 2009 at 6:12 PM, Devin Heitmuellerdheitmuel...@kernellabs.com wrote: On Fri, Aug 21, 2009 at 2:07 AM, Mauro Carvalho Chehabmche...@infradead.org wrote: In brief, while I want to fix the driver issues, I recommend to avoid buying any devices with tm5600/tm6000/tm6010 (and DRX demod) chips. There are other offers at the market with drivers that work properly, including some nice HVR devices that are fully supported. The more I think about it, the more I think we should setup something along the lines of a Wall of Shame on the LinuxTV wiki, so that people will be better informed exactly which products they should not buy because of the chipset vendor's behavior. I doubt that this will help, it will moreover scare them off and also put a bad light on Linux we already have a list of supported devices on linuxtv.org if people buy the wrong devices it's their fault in the end. Better support the available devices properly so that everyone can easily use them... everyone is the highest burden at this time... James Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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: compat.h required to build
On Fri, 2009-08-21 at 17:02 +0100, Lou Otway wrote: Hi, The following files: /linux/drivers/media/dvb/frontends/stb6100.c /linux/drivers/media/dvb/frontends/tda10021.c /linux/drivers/media/dvb/frontends/ves1820.c Fail to build with: error: implicit declaration of function 'DIV_ROUND_CLOSEST' and need the addition of: #include compat.h when building on my system. Is this related to my kernel version (2.6.28) or is it something else? DIV_ROUND_CLOSEST is probably available only in more recent kernels. When its use was added to those files, backward compatability was likely not tested. Including compat.h is the proper thing to do. Regards, Andy Thanks, Lou -- 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: compat.h required to build
On Fri, Aug 21, 2009 at 12:34 PM, Andy Wallsawa...@radix.net wrote: DIV_ROUND_CLOSEST is probably available only in more recent kernels. When its use was added to those files, backward compatability was likely not tested. Including compat.h is the proper thing to do. Regards, Andy I'm pretty sure Mauro just added the macro to compat.h yesterday (and I can only assume he missed a couple of includes). Lou, feel free to submit a patch with the extra includes, including an SOB. Thanks, Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
[PATCH] v4l-dvb-compat: Fix build for older kernels using DIV_ROUND_CLOSEST
DIV_ROUND_CLOSEST() is not available on older kernels. Include compat.h in a few files to fix building v4l-dvb from mercurial on older kernels. Reported-by: Lou Otway lot...@nildram.co.uk Reported-by: Avo Aasma avo.aa...@webit.ee Signed-off-by: Andy Walls awa...@radix.net diff -r d0ec20a376fe linux/drivers/media/dvb/frontends/stb6100.c --- a/linux/drivers/media/dvb/frontends/stb6100.c Thu Aug 20 01:30:58 2009 + +++ b/linux/drivers/media/dvb/frontends/stb6100.c Fri Aug 21 12:33:46 2009 -0400 @@ -24,6 +24,7 @@ #include linux/module.h #include linux/string.h +#include compat.h #include dvb_frontend.h #include stb6100.h diff -r d0ec20a376fe linux/drivers/media/dvb/frontends/tda10021.c --- a/linux/drivers/media/dvb/frontends/tda10021.c Thu Aug 20 01:30:58 2009 + +++ b/linux/drivers/media/dvb/frontends/tda10021.c Fri Aug 21 12:33:46 2009 -0400 @@ -29,6 +29,7 @@ #include linux/string.h #include linux/slab.h +#include compat.h #include dvb_frontend.h #include tda1002x.h diff -r d0ec20a376fe linux/drivers/media/dvb/frontends/ves1820.c --- a/linux/drivers/media/dvb/frontends/ves1820.c Thu Aug 20 01:30:58 2009 + +++ b/linux/drivers/media/dvb/frontends/ves1820.c Fri Aug 21 12:33:46 2009 -0400 @@ -27,6 +27,7 @@ #include linux/slab.h #include asm/div64.h +#include compat.h #include dvb_frontend.h #include ves1820.h -- 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
detection of Empire Media Pen Dual TV
As of latest v4l-dvb trunk installed, detection of Pen Dual TV isn't correct: Aug 21 20:26:55 box [ 2534.584239] usb 2-1: new high speed USB device using ehci_hcd and address 7 Aug 21 20:26:55 box [ 2534.701630] usb 2-1: New USB device found, idVendor=eb1a, idProduct=e310 Aug 21 20:26:55 box [ 2534.701635] usb 2-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 Aug 21 20:26:55 box [ 2534.701639] usb 2-1: Product: USB 2881 Device Aug 21 20:26:55 box [ 2534.702254] usb 2-1: configuration #1 chosen from 1 choice Aug 21 20:26:55 box [ 2534.720606] em28xx: New device USB 2881 Device @ 480 Mbps (eb1a:e310, interface 0, class 0) Aug 21 20:26:55 box [ 2534.720712] em28xx #0: chip ID is em2882/em2883 Aug 21 20:26:55 box [ 2534.849865] em28xx #0: i2c eeprom 00: 1a eb 67 95 1a eb 10 e3 d0 12 5c 03 6a 22 00 00 Aug 21 20:26:55 box [ 2534.849872] em28xx #0: i2c eeprom 10: 00 00 04 57 4e 07 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849878] em28xx #0: i2c eeprom 20: 46 00 01 00 f0 10 01 00 00 00 00 00 5b 1e 00 00 Aug 21 20:26:55 box [ 2534.849884] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849889] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849895] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849901] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 22 03 55 00 53 00 Aug 21 20:26:55 box [ 2534.849906] em28xx #0: i2c eeprom 70: 42 00 20 00 32 00 38 00 38 00 31 00 20 00 44 00 Aug 21 20:26:55 box [ 2534.849912] em28xx #0: i2c eeprom 80: 65 00 76 00 69 00 63 00 65 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849918] em28xx #0: i2c eeprom 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849923] em28xx #0: i2c eeprom a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849929] em28xx #0: i2c eeprom b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849934] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849940] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849946] em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849951] em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849958] em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0x166a0441 Aug 21 20:26:55 box [ 2534.849959] em28xx #0: EEPROM info: Aug 21 20:26:55 box [ 2534.849960] em28xx #0: AC97 audio (5 sample rates) Aug 21 20:26:55 box [ 2534.849962] em28xx #0: 500mA max power Aug 21 20:26:55 box [ 2534.849963] em28xx #0: Table at 0x04, strings=0x226a, 0x, 0x Aug 21 20:26:55 box [ 2534.849965] em28xx #0: Identified as MSI DigiVox A/D (card=49) Aug 21 20:26:55 box [ 2534.849967] em28xx #0: Your board has no unique USB ID. Aug 21 20:26:55 box [ 2534.849968] em28xx #0: A hint were successfully done, based on eeprom hash. Aug 21 20:26:55 box [ 2534.849970] em28xx #0: This method is not 100% failproof. Aug 21 20:26:55 box [ 2534.849971] em28xx #0: If the board were missdetected, please email this log to: Aug 21 20:26:55 box [ 2534.849973] em28xx #0: V4L Mailing List linux-media@vger.kernel.org Aug 21 20:26:55 box [ 2534.849974] em28xx #0: Board detected as Empire dual TV Aug 21 20:26:55 box [ 2534.905501] tvp5150 4-005c: chip found @ 0xb8 (em28xx #0) Aug 21 20:26:55 box [ 2534.910109] tuner 4-0061: chip found @ 0xc2 (em28xx #0) The identified card still is a MSI DigiVox A/D (card=49), but as you can see at http://www.reghardware.co.uk/2006/06/07/review_kworld_310u/ and http://www.empiremedia.it/site/prodotto.asp?idprodotto=231 Empire Media Pen Dual TV is a Kworld 310U based usb pen analogtv+dvbt+audio/video_in device. You can check downloads on 2nd link to get drivers, info, layouts and manual also. -- 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
Driver for Mystique Satix-SX
Hi list,
I'm having problems getting a DVB-S card labeled Mystique SaTix-SX
to run. According to the manufacturer (www.mystique-tv.de) all their
cards are supported by the linux dvb drivers.
But I can't get this one to work.
lspci collected the following information about the card:
#lspci -nvv
[...]
01:09.0 Multimedia controller [0480]: Philips Semiconductors SAA7146
[1131:7146] (rev 01)
Subsystem: KNC One Device [1894:0054]
Flags: bus master, medium devsel, latency 123, IRQ 11
Memory at fc005800 (32-bit, non-prefetchable) [size=512]
[...]
So I think this means that the card is actually a clone of some card
from KNC One (I think it's the TV Star DVB-S one).
A quick grep in the source delivered:
# grep -R 0x1894 *
drivers/media/dvb/ttpci/budget-av.c: if (saa-pci-subsystem_vendor
== 0x1894) {
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(knc1s, 0x1894,
0x0010),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(knc1sp,
0x1894, 0x0011),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(kncxs, 0x1894,
0x0014),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(knc1spx4,
0x1894, 0x0015),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(kncxs, 0x1894,
0x0016),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(knc1s2,
0x1894, 0x0018),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(knc1s2,
0x1894, 0x0019),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(sates2,
0x1894, 0x001d),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(satewpls,
0x1894, 0x001e),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(satewpls1,
0x1894, 0x001a),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(satewps,
0x1894, 0x001b),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(satewplc,
0x1894, 0x002a),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(satewcmk3,
0x1894, 0x002c),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(satewt,
0x1894, 0x003a),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(knc1c, 0x1894,
0x0020),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(knc1cp,
0x1894, 0x0021),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(knc1cmk3,
0x1894, 0x0022),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(knc1cpmk3,
0x1894, 0x0023),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(knc1t, 0x1894,
0x0030),
drivers/media/dvb/ttpci/budget-av.c: MAKE_EXTENSION_PCI(knc1tp,
0x1894, 0x0031),
drivers/media/video/saa7134/saa7134-cards.c:.subvendor= 0x1894,
drivers/media/video/saa7134/saa7134-cards.c:.subvendor= 0x1894,
So it seems this card is not supported at the time as I don't see any
SubID of 0x0054. How can I help to get this one supported?
Thanks for your help,
Chris
--
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: detection of Empire Media Pen Dual TV
On Fri, Aug 21, 2009 at 3:27 PM, Giuseppe Bagnatobagg...@gmail.com wrote: As of latest v4l-dvb trunk installed, detection of Pen Dual TV isn't correct: Aug 21 20:26:55 box [ 2534.584239] usb 2-1: new high speed USB device using ehci_hcd and address 7 Aug 21 20:26:55 box [ 2534.701630] usb 2-1: New USB device found, idVendor=eb1a, idProduct=e310 Aug 21 20:26:55 box [ 2534.701635] usb 2-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 Aug 21 20:26:55 box [ 2534.701639] usb 2-1: Product: USB 2881 Device Aug 21 20:26:55 box [ 2534.702254] usb 2-1: configuration #1 chosen from 1 choice Aug 21 20:26:55 box [ 2534.720606] em28xx: New device USB 2881 Device @ 480 Mbps (eb1a:e310, interface 0, class 0) Aug 21 20:26:55 box [ 2534.720712] em28xx #0: chip ID is em2882/em2883 Aug 21 20:26:55 box [ 2534.849865] em28xx #0: i2c eeprom 00: 1a eb 67 95 1a eb 10 e3 d0 12 5c 03 6a 22 00 00 Aug 21 20:26:55 box [ 2534.849872] em28xx #0: i2c eeprom 10: 00 00 04 57 4e 07 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849878] em28xx #0: i2c eeprom 20: 46 00 01 00 f0 10 01 00 00 00 00 00 5b 1e 00 00 Aug 21 20:26:55 box [ 2534.849884] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849889] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849895] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849901] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 22 03 55 00 53 00 Aug 21 20:26:55 box [ 2534.849906] em28xx #0: i2c eeprom 70: 42 00 20 00 32 00 38 00 38 00 31 00 20 00 44 00 Aug 21 20:26:55 box [ 2534.849912] em28xx #0: i2c eeprom 80: 65 00 76 00 69 00 63 00 65 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849918] em28xx #0: i2c eeprom 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849923] em28xx #0: i2c eeprom a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849929] em28xx #0: i2c eeprom b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849934] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849940] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849946] em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849951] em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 21 20:26:55 box [ 2534.849958] em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0x166a0441 Aug 21 20:26:55 box [ 2534.849959] em28xx #0: EEPROM info: Aug 21 20:26:55 box [ 2534.849960] em28xx #0: AC97 audio (5 sample rates) Aug 21 20:26:55 box [ 2534.849962] em28xx #0: 500mA max power Aug 21 20:26:55 box [ 2534.849963] em28xx #0: Table at 0x04, strings=0x226a, 0x, 0x Aug 21 20:26:55 box [ 2534.849965] em28xx #0: Identified as MSI DigiVox A/D (card=49) Aug 21 20:26:55 box [ 2534.849967] em28xx #0: Your board has no unique USB ID. Aug 21 20:26:55 box [ 2534.849968] em28xx #0: A hint were successfully done, based on eeprom hash. Aug 21 20:26:55 box [ 2534.849970] em28xx #0: This method is not 100% failproof. Aug 21 20:26:55 box [ 2534.849971] em28xx #0: If the board were missdetected, please email this log to: Aug 21 20:26:55 box [ 2534.849973] em28xx #0: V4L Mailing List linux-media@vger.kernel.org Aug 21 20:26:55 box [ 2534.849974] em28xx #0: Board detected as Empire dual TV Aug 21 20:26:55 box [ 2534.905501] tvp5150 4-005c: chip found @ 0xb8 (em28xx #0) Aug 21 20:26:55 box [ 2534.910109] tuner 4-0061: chip found @ 0xc2 (em28xx #0) The identified card still is a MSI DigiVox A/D (card=49), but as you can see at http://www.reghardware.co.uk/2006/06/07/review_kworld_310u/ and http://www.empiremedia.it/site/prodotto.asp?idprodotto=231 Empire Media Pen Dual TV is a Kworld 310U based usb pen analogtv+dvbt+audio/video_in device. You can check downloads on 2nd link to get drivers, info, layouts and manual also. -- 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 Hello Giuseppe, Your email is a bit confusing - are you saying that you have the MSI DigiVox board and it is detecting as an Empire Dual TV? It's possible that they are the exact same hardware design, and that the board gets identified with the name of the first product we added support for. If you could please clarify which product you own (and what components it contains), we can probably help here. Thanks, Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More
Re: detection of Empire Media Pen Dual TV
Hello Giuseppe, Your email is a bit confusing - are you saying that you have the MSI DigiVox board and it is detecting as an Empire Dual TV? It's possible that they are the exact same hardware design, and that the board gets identified with the name of the first product we added support for. If you could please clarify which product you own (and what components it contains), we can probably help here. Thanks, Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com Hello Devin, I have an Empire Media Pen Dual TV and it has same layout as Kworld dvb-t 310u. while MSI Digivox A/D has similar layout and supports 1080i extra resolution, as http://www.msi.com/index.php?func=proddescmaincat_no=132prod_no=626 If you want I can capture usb device startup log using Usbsnoop/SniffUSB ... Giuseppe -- 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: detection of Empire Media Pen Dual TV
On Fri, Aug 21, 2009 at 4:05 PM, Baggiusbagg...@gmail.com wrote: Hello Devin, I have an Empire Media Pen Dual TV and it has same layout as Kworld dvb-t 310u. while MSI Digivox A/D has similar layout and supports 1080i extra resolution, as http://www.msi.com/index.php?func=proddescmaincat_no=132prod_no=626 If you want I can capture usb device startup log using Usbsnoop/SniffUSB ... Giuseppe Hmmm... Let's hold off on a usb capture for now. Now that I understand that you have the Empire board, I am looking at the dmesg trace again and am a bit confused. Do you happen to have a card=49 parameter in your modprobe configuration? However, the code does appear to also recognize the board as the Empire board (see the Board detected as Empire dual TV). I agree that something appears to be wrong. I will have to take a look at the code and see where the Identified as messages comes from. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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: [cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: ERRORS
On Friday 21 August 2009 20:17:18 Hans Verkuil wrote: This message is generated daily by a cron job that builds v4l-dvb for the kernels and architectures in the list below. Guys, I'm providing this service for a reason: please take a look at the detailed log when you see errors or warnings. This time round we have a compat error with DIV_ROUND_CLOSEST: v4l/stb6100.c: In function 'stb6100_set_frequency': v4l/stb6100.c:377: error: implicit declaration of function 'DIV_ROUND_CLOSEST' Should be simple to fix. This macro appeared in 2.6.29 and so should be made available in compat.h. I also get a large amount of errors on smssdio.c for kernels pre-2.6.24: v4l/smssdio.c:39:33: error: linux/mmc/sdio_func.h: No such file or directory v4l/smssdio.c:51: error: array type has incomplete element type v4l/smssdio.c:52: warning: implicit declaration of function 'SDIO_DEVICE' v4l/smssdio.c:53: error: field name not in record or union initializer v4l/smssdio.c:53: error: (near initialization for 'smssdio_ids') This header appeared in 2.6.24 for the first time, so this driver shouldn't be build on older kernel versions. There is also a warning here: v4l/smssdio.c: In function 'smssdio_sendrequest': v4l/smssdio.c:81: warning: 'ret' may be used uninitialized in this function The bttv driver has been broken for a lng time for kernels = 2.6.19: v4l/bttv-driver.c:4635: warning: implicit declaration of function 'PCI_VDEVICE' v4l/bttv-driver.c:4635: error: 'BROOKTREE' undeclared here (not in a function) I don't care about anything pre-2.6.22, but since some people wanted it I've kept compiling against these old kernels. But if nobody fixes this soon, then I'm going to kill that off since I have better uses for those CPU cycles. Bottom line: if you know that a change of yours was merged in v4l-dvb, and you see errors or warnings appearing in the daily build, then take a look if your change caused it, and if so, then please fix it asap. Regards, Hans Results of the daily build of v4l-dvb: date:Fri Aug 21 19:00:07 CEST 2009 path:http://www.linuxtv.org/hg/v4l-dvb changeset: 12492:d0ec20a376fe gcc version: gcc (GCC) 4.3.1 hardware:x86_64 host os: 2.6.26 linux-2.6.22.19-armv5: OK linux-2.6.23.12-armv5: OK linux-2.6.24.7-armv5: OK linux-2.6.25.11-armv5: OK linux-2.6.26-armv5: OK linux-2.6.27-armv5: OK linux-2.6.28-armv5: OK linux-2.6.29.1-armv5: OK linux-2.6.30-armv5: OK linux-2.6.31-rc5-armv5: OK linux-2.6.27-armv5-ixp: ERRORS linux-2.6.28-armv5-ixp: ERRORS linux-2.6.29.1-armv5-ixp: OK linux-2.6.30-armv5-ixp: OK linux-2.6.31-rc5-armv5-ixp: OK linux-2.6.28-armv5-omap2: ERRORS linux-2.6.29.1-armv5-omap2: OK linux-2.6.30-armv5-omap2: OK linux-2.6.31-rc5-armv5-omap2: OK linux-2.6.22.19-i686: ERRORS linux-2.6.23.12-i686: ERRORS linux-2.6.24.7-i686: ERRORS linux-2.6.25.11-i686: ERRORS linux-2.6.26-i686: ERRORS linux-2.6.27-i686: ERRORS linux-2.6.28-i686: ERRORS linux-2.6.29.1-i686: WARNINGS linux-2.6.30-i686: WARNINGS linux-2.6.31-rc5-i686: OK linux-2.6.23.12-m32r: ERRORS linux-2.6.24.7-m32r: OK linux-2.6.25.11-m32r: OK linux-2.6.26-m32r: OK linux-2.6.27-m32r: OK linux-2.6.28-m32r: OK linux-2.6.29.1-m32r: OK linux-2.6.30-m32r: OK linux-2.6.31-rc5-m32r: OK linux-2.6.30-mips: WARNINGS linux-2.6.31-rc5-mips: OK linux-2.6.27-powerpc64: ERRORS linux-2.6.28-powerpc64: ERRORS linux-2.6.29.1-powerpc64: WARNINGS linux-2.6.30-powerpc64: WARNINGS linux-2.6.31-rc5-powerpc64: OK linux-2.6.22.19-x86_64: ERRORS linux-2.6.23.12-x86_64: ERRORS linux-2.6.24.7-x86_64: ERRORS linux-2.6.25.11-x86_64: ERRORS linux-2.6.26-x86_64: ERRORS linux-2.6.27-x86_64: ERRORS linux-2.6.28-x86_64: ERRORS linux-2.6.29.1-x86_64: WARNINGS linux-2.6.30-x86_64: WARNINGS linux-2.6.31-rc5-x86_64: OK sparse (linux-2.6.30): OK sparse (linux-2.6.31-rc5): OK linux-2.6.16.61-i686: ERRORS linux-2.6.17.14-i686: ERRORS linux-2.6.18.8-i686: ERRORS linux-2.6.19.5-i686: ERRORS linux-2.6.20.21-i686: ERRORS linux-2.6.21.7-i686: ERRORS linux-2.6.16.61-x86_64: ERRORS linux-2.6.17.14-x86_64: ERRORS linux-2.6.18.8-x86_64: ERRORS linux-2.6.19.5-x86_64: ERRORS linux-2.6.20.21-x86_64: ERRORS linux-2.6.21.7-x86_64: ERRORS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Friday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Friday.tar.bz2 The V4L2 specification from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/v4l2.html The DVB API specification from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/dvbapi.pdf -- 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 -- Hans Verkuil - video4linux developer - sponsored by TANDBERG -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to
Re: [cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: ERRORS
On Fri, 2009-08-21 at 22:45 +0200, Hans Verkuil wrote: On Friday 21 August 2009 20:17:18 Hans Verkuil wrote: This message is generated daily by a cron job that builds v4l-dvb for the kernels and architectures in the list below. Guys, I'm providing this service for a reason: please take a look at the detailed log when you see errors or warnings. This time round we have a compat error with DIV_ROUND_CLOSEST: v4l/stb6100.c: In function 'stb6100_set_frequency': v4l/stb6100.c:377: error: implicit declaration of function 'DIV_ROUND_CLOSEST' Should be simple to fix. This macro appeared in 2.6.29 and so should be made available in compat.h. A patch for this one was submitted to the list earlier today: http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/9142 (though not because I saw it in the logs). I do usually scan the logs for cx18, ivtv, and cx25840 problems. Maybe I should expand my scope a little. Regards, Andy I also get a large amount of errors on smssdio.c for kernels pre-2.6.24: v4l/smssdio.c:39:33: error: linux/mmc/sdio_func.h: No such file or directory v4l/smssdio.c:51: error: array type has incomplete element type v4l/smssdio.c:52: warning: implicit declaration of function 'SDIO_DEVICE' v4l/smssdio.c:53: error: field name not in record or union initializer v4l/smssdio.c:53: error: (near initialization for 'smssdio_ids') This header appeared in 2.6.24 for the first time, so this driver shouldn't be build on older kernel versions. There is also a warning here: v4l/smssdio.c: In function 'smssdio_sendrequest': v4l/smssdio.c:81: warning: 'ret' may be used uninitialized in this function The bttv driver has been broken for a lng time for kernels = 2.6.19: v4l/bttv-driver.c:4635: warning: implicit declaration of function 'PCI_VDEVICE' v4l/bttv-driver.c:4635: error: 'BROOKTREE' undeclared here (not in a function) I don't care about anything pre-2.6.22, but since some people wanted it I've kept compiling against these old kernels. But if nobody fixes this soon, then I'm going to kill that off since I have better uses for those CPU cycles. Bottom line: if you know that a change of yours was merged in v4l-dvb, and you see errors or warnings appearing in the daily build, then take a look if your change caused it, and if so, then please fix it asap. Regards, Hans Results of the daily build of v4l-dvb: date:Fri Aug 21 19:00:07 CEST 2009 path:http://www.linuxtv.org/hg/v4l-dvb changeset: 12492:d0ec20a376fe gcc version: gcc (GCC) 4.3.1 hardware:x86_64 host os: 2.6.26 linux-2.6.22.19-armv5: OK linux-2.6.23.12-armv5: OK linux-2.6.24.7-armv5: OK linux-2.6.25.11-armv5: OK linux-2.6.26-armv5: OK linux-2.6.27-armv5: OK linux-2.6.28-armv5: OK linux-2.6.29.1-armv5: OK linux-2.6.30-armv5: OK linux-2.6.31-rc5-armv5: OK linux-2.6.27-armv5-ixp: ERRORS linux-2.6.28-armv5-ixp: ERRORS linux-2.6.29.1-armv5-ixp: OK linux-2.6.30-armv5-ixp: OK linux-2.6.31-rc5-armv5-ixp: OK linux-2.6.28-armv5-omap2: ERRORS linux-2.6.29.1-armv5-omap2: OK linux-2.6.30-armv5-omap2: OK linux-2.6.31-rc5-armv5-omap2: OK linux-2.6.22.19-i686: ERRORS linux-2.6.23.12-i686: ERRORS linux-2.6.24.7-i686: ERRORS linux-2.6.25.11-i686: ERRORS linux-2.6.26-i686: ERRORS linux-2.6.27-i686: ERRORS linux-2.6.28-i686: ERRORS linux-2.6.29.1-i686: WARNINGS linux-2.6.30-i686: WARNINGS linux-2.6.31-rc5-i686: OK linux-2.6.23.12-m32r: ERRORS linux-2.6.24.7-m32r: OK linux-2.6.25.11-m32r: OK linux-2.6.26-m32r: OK linux-2.6.27-m32r: OK linux-2.6.28-m32r: OK linux-2.6.29.1-m32r: OK linux-2.6.30-m32r: OK linux-2.6.31-rc5-m32r: OK linux-2.6.30-mips: WARNINGS linux-2.6.31-rc5-mips: OK linux-2.6.27-powerpc64: ERRORS linux-2.6.28-powerpc64: ERRORS linux-2.6.29.1-powerpc64: WARNINGS linux-2.6.30-powerpc64: WARNINGS linux-2.6.31-rc5-powerpc64: OK linux-2.6.22.19-x86_64: ERRORS linux-2.6.23.12-x86_64: ERRORS linux-2.6.24.7-x86_64: ERRORS linux-2.6.25.11-x86_64: ERRORS linux-2.6.26-x86_64: ERRORS linux-2.6.27-x86_64: ERRORS linux-2.6.28-x86_64: ERRORS linux-2.6.29.1-x86_64: WARNINGS linux-2.6.30-x86_64: WARNINGS linux-2.6.31-rc5-x86_64: OK sparse (linux-2.6.30): OK sparse (linux-2.6.31-rc5): OK linux-2.6.16.61-i686: ERRORS linux-2.6.17.14-i686: ERRORS linux-2.6.18.8-i686: ERRORS linux-2.6.19.5-i686: ERRORS linux-2.6.20.21-i686: ERRORS linux-2.6.21.7-i686: ERRORS linux-2.6.16.61-x86_64: ERRORS linux-2.6.17.14-x86_64: ERRORS linux-2.6.18.8-x86_64: ERRORS linux-2.6.19.5-x86_64: ERRORS linux-2.6.20.21-x86_64: ERRORS linux-2.6.21.7-x86_64: ERRORS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Friday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Friday.tar.bz2 The V4L2 specification from this daily build is here:
Re: [cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: ERRORS
Em Fri, 21 Aug 2009 18:10:45 -0400 Andy Walls awa...@radix.net escreveu: Guys, I'm providing this service for a reason: please take a look at the detailed log when you see errors or warnings. This time round we have a compat error with DIV_ROUND_CLOSEST: v4l/stb6100.c: In function 'stb6100_set_frequency': v4l/stb6100.c:377: error: implicit declaration of function 'DIV_ROUND_CLOSEST' Should be simple to fix. This macro appeared in 2.6.29 and so should be made available in compat.h. At the days I'm preparing some upstream patches, it is not rare to have some backport breakage, since lots of patches are merged, including, on some cases, some upstream patches that need extra backport. I intend to finish sync -hg and -git this weekend, so, I'll be fixing the remaining backport issues. A patch for this one was submitted to the list earlier today: http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/9142 (though not because I saw it in the logs). I saw that. It will be merged as well. 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
