IR port on TechniSat CableStar HD 2
I read [1] that you were working on adding support for the IR port on the TechniSat CableStar HD 2 card. However, when I tried to compile the drivers from http://linuxtv.org/hg/v4l-dvb as instructed on http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers#If_the_Modules_did_not_load_correctly_or_the_device_is_still_not_configured_correctly_for_use it did not work. The device is not listed in /proc/bus/input/devices I am using Debian testing which has the 2.6.32 kernel and here are some of the modules I have loaded: b...@bob:~$ lsmod | grep mantis mantis 14872 0 mantis_core23989 6 mantis ir_common 3621 1 mantis_core ir_core10193 7 ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,mantis_core,ir_nec_decoder,ir_common tda665x 2679 1 mantis lnbp21 1740 1 mantis mb86a1616566 1 mantis stb6100 5525 1 mantis tda100214774 1 mantis tda100235823 1 mantis zl10353 5861 1 mantis stb089928713 1 mantis stv0299 7812 1 mantis dvb_core 74866 3 b2c2_flexcop,mantis_core,stv0299 i2c_core 15712 20 b2c2_flexcop,cx24123,cx24113,s5h1420,mantis,mantis_core,tda665x,lnbp21,mb86a16,stb6100,tda10021,tda10023,zl10353,stb0899,stv0299,nouveau,drm_kms_helper,drm,i2c_algo_bit,i2c_nforce2 I also tried to build the drivers from http://jusst.de/hg/mantis-v4l-dvb/ but the build failed. Could you please let me know what is the current status? Thanks, Debarshi [1] http://www.mail-archive.com/linux-media@vger.kernel.org/msg14620.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
CI-Module not working on Technisat Cablestar HD2
Hi, I am trying to get the CI module of a Technisat Cablestar HD2 to work since about a week now. I tried multiple x64 kernelbuilds (s2-liplianin, straight 2.6.35-rc3 kernel, 2.6.32-22 ubuntu kernel, 2.6.34, .) and could not get the cam module on the mantis-based card to work. After looking into it in detail, it seems that my card is not using the tda10021 frontend (as outlined in http://www.linuxtv.org/wiki/index.php/Technisat_CableStar_HD2) but the tda10023 frontend. I had a brief look through the code and also tried to use the tda10021 frontend manually but the detection will fail. My dmesg looks like this: [ 19.821945] IR NEC protocol handler initialized [ 19.832912] IR RC5(x) protocol handler initialized [ 19.835154] IR RC6 protocol handler initialized [ 19.838766] IR JVC protocol handler initialized [ 19.843647] found a VP-2040 PCI DVB-C device on (04:01.0), [ 19.843657] Mantis :04:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 19.843698] Mantis Rev 1 [1ae4:0002], irq: 16, latency: 64 [ 19.843700] memory: 0x0, mmio: 0xc900057ca000 [ 19.843917] IR Sony protocol handler initialized [ 19.844666] MAC Address=[00:08:c9:d0:37:37] [ 19.844677] mantis_alloc_buffers (0): DMA=0x379e cpu=0x8800379e size=65536 [ 19.844681] mantis_alloc_buffers (0): RISC=0x3799e000 cpu=0x88003799e000 size=1000 [ 19.844683] DVB: registering new adapter (Mantis DVB adapter) [ 19.873668] r8169 :02:00.0: eth0: link up [ 19.873704] r8169 :02:00.0: eth0: link up [ 20.213418] alloc irq_desc for 22 on node -1 [ 20.213421] alloc kstat_irqs on node -1 [ 20.213427] HDA Intel :00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [ 20.213519] alloc irq_desc for 45 on node -1 [ 20.213521] alloc kstat_irqs on node -1 [ 20.213529] HDA Intel :00:1b.0: irq 45 for MSI/MSI-X [ 20.213553] HDA Intel :00:1b.0: setting latency timer to 64 [ 20.393010] hda_codec: ALC887: BIOS auto-probing. [ 20.394885] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input3 [ 20.768259] vp2040_frontend_init (0): Probing for CU1216 (DVB-C) [ 20.770271] vp2040_frontend_init (0): found Philips CU1216 DVB-C frontend (TDA10023) @ 0x0c [ 20.770273] vp2040_frontend_init (0): Mantis DVB-C Philips CU1216 frontend attach success [ 20.770276] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... I can't see any of the expected mantis_ca_init but couldn't figure out in the code where that gets called. Here's some pci information for the card: 04:01.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) lspci -vv -s 04:01.0 04:01.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) Subsystem: Device 1ae4:0002 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- http://vger.kernel.org/majordomo-info.html
Update to tuning file frequencies for au-Brisbane location to include a new channel
Good morning, I would like to include an update in the auto tune file for the /dvb/dvb-t/au-Brisbane file as there has recently been an additional channel added to the area. If you can please add the following 2 lines to the file that would be appreciated. # 31 Digital T 59950 7MHz 2/3 NONE QAM64 8k 1/8 NONE It is appropriate for it to be at the end of the list so the whole file would look like (just in case it makes it easier for you than a single line in isolation): # Australia / Brisbane (Mt Coot-tha transmitters) # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy # ABC T 22650 7MHz 3/4 NONE QAM64 8k 1/16 NONE # Seven T 17750 7MHz 3/4 NONE QAM64 8k 1/16 NONE # Nine T 191625000 7MHz 3/4 NONE QAM64 8k 1/16 NONE # Ten T 21950 7MHz 3/4 NONE QAM64 8k 1/16 NONE # SBS T 585625000 7MHz 2/3 NONE QAM64 8k 1/8 NONE # 31 Digital T 59950 7MHz 2/3 NONE QAM64 8k 1/8 NONE I hope this is enough information for your requirements. I have tested this on several devices under several dvb applications and from what I can see the options are all correct. If further information or testing is required please let me know and I will happily help out. Thanks for your time. Regards, Jared Norris -- 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
[cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: ERRORS
This message is generated daily by a cron job that builds v4l-dvb for the kernels and architectures in the list below. Results of the daily build of v4l-dvb: date:Wed Jun 23 19:00:09 CEST 2010 path:http://www.linuxtv.org/hg/v4l-dvb changeset: 14993:9652f85e688a git master: f6760aa024199cfbce564311dc4bc4d47b6fb349 git media-master: 41c5f984b67b331064e69acc9fca5e99bf73d400 gcc version: i686-linux-gcc (GCC) 4.4.3 host hardware:x86_64 host os: 2.6.32.5 linux-2.6.32.6-armv5: OK linux-2.6.33-armv5: OK linux-2.6.34-armv5: WARNINGS linux-2.6.35-rc1-armv5: ERRORS linux-2.6.32.6-armv5-davinci: OK linux-2.6.33-armv5-davinci: OK linux-2.6.34-armv5-davinci: WARNINGS linux-2.6.35-rc1-armv5-davinci: ERRORS linux-2.6.32.6-armv5-ixp: WARNINGS linux-2.6.33-armv5-ixp: WARNINGS linux-2.6.34-armv5-ixp: WARNINGS linux-2.6.35-rc1-armv5-ixp: ERRORS linux-2.6.32.6-armv5-omap2: OK linux-2.6.33-armv5-omap2: OK linux-2.6.34-armv5-omap2: WARNINGS linux-2.6.35-rc1-armv5-omap2: ERRORS linux-2.6.22.19-i686: ERRORS linux-2.6.23.17-i686: ERRORS linux-2.6.24.7-i686: WARNINGS linux-2.6.25.20-i686: WARNINGS linux-2.6.26.8-i686: WARNINGS linux-2.6.27.44-i686: WARNINGS linux-2.6.28.10-i686: WARNINGS linux-2.6.29.1-i686: WARNINGS linux-2.6.30.10-i686: WARNINGS linux-2.6.31.12-i686: OK linux-2.6.32.6-i686: OK linux-2.6.33-i686: OK linux-2.6.34-i686: WARNINGS linux-2.6.35-rc1-i686: ERRORS linux-2.6.32.6-m32r: OK linux-2.6.33-m32r: OK linux-2.6.34-m32r: WARNINGS linux-2.6.35-rc1-m32r: ERRORS linux-2.6.32.6-mips: OK linux-2.6.33-mips: OK linux-2.6.34-mips: WARNINGS linux-2.6.35-rc1-mips: ERRORS linux-2.6.32.6-powerpc64: OK linux-2.6.33-powerpc64: OK linux-2.6.34-powerpc64: WARNINGS linux-2.6.35-rc1-powerpc64: ERRORS linux-2.6.22.19-x86_64: ERRORS linux-2.6.23.17-x86_64: ERRORS linux-2.6.24.7-x86_64: WARNINGS linux-2.6.25.20-x86_64: WARNINGS linux-2.6.26.8-x86_64: WARNINGS linux-2.6.27.44-x86_64: WARNINGS linux-2.6.28.10-x86_64: WARNINGS linux-2.6.29.1-x86_64: WARNINGS linux-2.6.30.10-x86_64: WARNINGS linux-2.6.31.12-x86_64: OK linux-2.6.32.6-x86_64: OK linux-2.6.33-x86_64: OK linux-2.6.34-x86_64: WARNINGS linux-2.6.35-rc1-x86_64: ERRORS linux-git-armv5: WARNINGS linux-git-armv5-davinci: WARNINGS linux-git-armv5-ixp: WARNINGS linux-git-armv5-omap2: WARNINGS linux-git-i686: WARNINGS linux-git-m32r: OK linux-git-mips: OK linux-git-powerpc64: OK linux-git-x86_64: WARNINGS spec: ERRORS spec-git: OK sparse: ERRORS linux-2.6.16.62-i686: ERRORS linux-2.6.17.14-i686: ERRORS linux-2.6.18.8-i686: ERRORS linux-2.6.19.7-i686: ERRORS linux-2.6.20.21-i686: ERRORS linux-2.6.21.7-i686: ERRORS linux-2.6.16.62-x86_64: ERRORS linux-2.6.17.14-x86_64: ERRORS linux-2.6.18.8-x86_64: ERRORS linux-2.6.19.7-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/Wednesday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Wednesday.tar.bz2 The V4L-DVB specification from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/media.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
Please send an email with this log to: V4L Mailing List
( this with UBUNTU 10.04 AMD64, maybe some firmware problem on 64 bit architecture ? ) This is the product : http://www.magnex.it/magnex/prodotti/video_processing/index.htm [ 14.037770] w83627ehf: Found W83627DHG-P chip at 0x290 [ 14.097263] Linux video capture interface: v2.00 [ 14.157699] em28xx: New device USB 2881 Video @ 480 Mbps (eb1a:2881, interface 0, class 0) [ 14.157874] em28xx #0: chip ID is em2882/em2883 [ 14.196847] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 18 [ 14.196851] alloc irq_desc for 18 on node 0 [ 14.196853] alloc kstat_irqs on node 0 [ 14.196860] rt61pci :01:08.0: PCI INT A -> Link[LNKA] -> GSI 18 (level, low) -> IRQ 18 [ 14.206641] phy0: Selected rate control algorithm 'minstrel' [ 14.207037] Registered led device: rt61pci-phy0::radio [ 14.207050] Registered led device: rt61pci-phy0::assoc [ 14.237128] em28xx #0: i2c eeprom 00: 1a eb 67 95 1a eb 81 28 58 12 5c 00 6a 20 6a 00 [ 14.237134] em28xx #0: i2c eeprom 10: 00 00 04 57 64 56 00 00 60 f4 00 00 02 02 00 00 [ 14.237138] em28xx #0: i2c eeprom 20: 56 00 01 00 00 00 01 00 b8 00 00 00 5b 1e 00 00 [ 14.237142] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 10 02 00 00 00 00 00 00 [ 14.237146] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 14.237150] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 14.237154] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 20 03 55 00 53 00 [ 14.237158] em28xx #0: i2c eeprom 70: 42 00 20 00 32 00 38 00 38 00 31 00 20 00 56 00 [ 14.237162] em28xx #0: i2c eeprom 80: 69 00 64 00 65 00 6f 00 00 00 00 00 00 00 00 00 [ 14.237166] em28xx #0: i2c eeprom 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 14.237170] em28xx #0: i2c eeprom a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 14.237174] em28xx #0: i2c eeprom b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 14.237177] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 14.237181] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 14.237185] em28xx #0: i2c eeprom e0: 5a 00 55 aa 87 ed 53 03 00 17 08 01 00 00 00 00 [ 14.237189] em28xx #0: i2c eeprom f0: 07 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 [ 14.237194] em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0x4e17ff20 [ 14.237195] em28xx #0: EEPROM info: [ 14.237196] em28xx #0: AC97 audio (5 sample rates) [ 14.237196] em28xx #0: USB Remote wakeup capable [ 14.237197] em28xx #0: 500mA max power [ 14.237199] em28xx #0: Table at 0x04, strings=0x206a, 0x006a, 0x [ 14.238503] em28xx #0: Identified as Unknown EM2750/28xx video grabber (card=1) [ 14.270503] em28xx #0: found i2c device @ 0xa0 [eeprom] [ 14.275127] em28xx #0: found i2c device @ 0xb8 [tvp5150a] [ 14.277003] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] [ 14.288252] em28xx #0: Your board has no unique USB ID and thus need a hint to be detected. [ 14.288256] em28xx #0: You may try to use card= insmod option to workaround that. [ 14.288257] em28xx #0: Please send an email with this log to: [ 14.288258] em28xx #0: V4L Mailing List [ 14.288259] em28xx #0: Board eeprom hash is 0x4e17ff20 [ 14.288260] em28xx #0: Board i2c devicelist hash is 0x27e10080 [ 14.288261] em28xx #0: Here is a list of valid choices for the card= insmod option: [ 14.288263] em28xx #0: card=0 -> Unknown EM2800 video grabber [ 14.288264] em28xx #0: card=1 -> Unknown EM2750/28xx video grabber [ 14.288265] em28xx #0: card=2 -> Terratec Cinergy 250 USB [ 14.288266] em28xx #0: card=3 -> Pinnacle PCTV USB 2 [ 14.288267] em28xx #0: card=4 -> Hauppauge WinTV USB 2 [ 14.288268] em28xx #0: card=5 -> MSI VOX USB 2.0 [ 14.288269] em28xx #0: card=6 -> Terratec Cinergy 200 USB [ 14.288270] em28xx #0: card=7 -> Leadtek Winfast USB II [ 14.288271] em28xx #0: card=8 -> Kworld USB2800 [ 14.288273] em28xx #0: card=9 -> Pinnacle Dazzle DVC 90/100/101/107 / Kaiser Baas Video to DVD maker / Kworld DVD Maker 2 [ 14.288274] em28xx #0: card=10 -> Hauppauge WinTV HVR 900 [ 14.288275] em28xx #0: card=11 -> Terratec Hybrid XS [ 14.288276] em28xx #0: card=12 -> Kworld PVR TV 2800 RF [ 14.288277] em28xx #0: card=13 -> Terratec Prodigy XS [ 14.288278] em28xx #0: card=14 -> SIIG AVTuner-PVR / Pixelview Prolink PlayTV USB 2.0 [ 14.288279] em28xx #0: card=15 -> V-Gear PocketTV [ 14.288280] em28xx #0: card=16 -> Hauppauge WinTV HVR 950 [ 14.288281] em28xx #0: card=17 -> Pinnacle PCTV HD Pro Stick [ 14.288283] em28xx #0: card=18 -> Hauppauge WinTV HVR 900 (R2) [ 14.288284] em28xx #0: card=19 -> EM2860/SAA711X Reference Design [ 14.288285] em28xx #0: card=20 -> AMD ATI TV Wonder HD 600 [ 14.288286] em28xx #0: card=21 -> eMPIA Technology, Inc. GrabBeeX+ Video Encoder [ 14.288287] em28xx #0: card=22 -> EM2710/E
Record from DVB tuner
Depending how you want to use it you may like getstream. http://silicon-verl.de/home/flo/projects/streaming/ You set up a config file that specifies the adapter the channels and the output (can be streamed or saved to file. Or dvbstreamer http://sourceforge.net/apps/mediawiki/dvbstreamer/index.php?title=Main_Page This can have a config file but can also have its operation changed while running. Si. On 23 June 2010 17:06, shacky wrote: > > Hi. > > I need to record some DVB channels from the command line using a > supported DVB tuner PCI card on Linux Debian. > I know I can tune the DVB adapter using dvbtools and record the raw > input using cat from /dev/dvb/adapter0, but what about recording two > or more different channels from the same multiplex? > How I can do this from the command line? > Could you help me please? > > Thank you very much! > Bye. > -- > 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: [linux-dvb] Record from DVB tuner
Hi, I think the best it's using dvbstream with -o parameter with pipes, tee and ts_filter For example: dvbstream -o 8192 | tee pids > file | tee >(ts_filter pids > file) \ > (ts_filter another_pids > file) I hope this can help you. On Miércoles, 23 de Junio de 2010 18:02:36 shacky escribió: > Hi. > > I need to record some DVB channels from the command line using a > supported DVB tuner PCI card on Linux Debian. > I know I can tune the DVB adapter using dvbtools and record the raw > input using cat from /dev/dvb/adapter0, but what about recording two > or more different channels from the same multiplex? > How I can do this from the command line? > Could you help me please? > > Thank you very much! > Bye. > > ___ > 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 > -- 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: buffer management
23.06.2010 15:43, Steven Toth kirjoitti: Now, on each video interrupt, I know which SG list i need to read from. At this stage i do need to copy the buffers associated with each of the SG lists at once. In this scenario, I don't see how videobuf could be used, while I keep getting this feeling that a simple copy_to_user of the entire buffer could do the whole job in a better way, since the buffers themselves are already managed and initialized already. Am I correct in thinking so, or is it that I am overlooking something ? How to activate DMA transfers only if there is empty space for the DMA transfer? Regards, Marko Manu, SAA7164 suffers from this. If you find a solution I'd love to hear it. Regards, - Steve -- 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
Record from DVB tuner
Hi. I need to record some DVB channels from the command line using a supported DVB tuner PCI card on Linux Debian. I know I can tune the DVB adapter using dvbtools and record the raw input using cat from /dev/dvb/adapter0, but what about recording two or more different channels from the same multiplex? How I can do this from the command line? Could you help me please? Thank you very much! Bye. -- 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
Record from DVB tuner
Hi. I need to record some DVB channels from the command line using a supported DVB tuner PCI card on Linux Debian. I know I can tune the DVB adapter using dvbtools and record the raw input using cat from /dev/dvb/adapter0, but what about recording two or more different channels from the same multiplex? How I can do this from the command line? Could you help me please? Thank you very much! Bye. -- 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: [2.6.33.4 PATCH] V4L/uvcvideo: Add support for Suyin Corp. Lenovo Webcam
Hi Nils, On Wednesday 23 June 2010 11:23:16 Nils Radtke wrote: > From: Nils Radtke > > This patch adds support for the Suyin Corp. Lenovo Webcam. > lsusb: ID 064e:a102 Suyin Corp. Lenovo Webcam > > It is available as built-in webcam i.e. in ACER timeline 1810t > notebooks. > > The note in uvc_driver.c about Logitech cameras applies the same > to the Suyin web cam: it doesn't announce itself as UVC devices > but is compliant. > > Signed-off-by: Nils Radtke Thanks for the patch. Could you please send me the output of lsusb -v for your camera, as well as the raw binary descriptors ? You can retrieve the later with cat /proc/bus/usb/xxx/yyy Replace xxx with the device bus number, and yyy with the device number. Both can be retrieved from /proc/bus/usb/devices. -- 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: buffer management
Now, on each video interrupt, I know which SG list i need to read from. At this stage i do need to copy the buffers associated with each of the SG lists at once. In this scenario, I don't see how videobuf could be used, while I keep getting this feeling that a simple copy_to_user of the entire buffer could do the whole job in a better way, since the buffers themselves are already managed and initialized already. Am I correct in thinking so, or is it that I am overlooking something ? Manu, SAA7164 suffers from this. If you find a solution I'd love to hear it. Regards, - Steve -- Steven Toth - 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
[2.6.33.4 PATCH] V4L/uvcvideo: Add support for Suyin Corp. Lenovo Webcam
From: Nils Radtke
This patch adds support for the Suyin Corp. Lenovo Webcam.
lsusb: ID 064e:a102 Suyin Corp. Lenovo Webcam
It is available as built-in webcam i.e. in ACER timeline 1810t
notebooks.
The note in uvc_driver.c about Logitech cameras applies the same
to the Suyin web cam: it doesn't announce itself as UVC devices
but is compliant.
Signed-off-by: Nils Radtke
---
Thank you,
Nils
uvc_driver.c |8
1 file changed, 8 insertions(+)
Index: linux/drivers/media/video/uvc/uvc_driver.c
===
--- linux.orig/drivers/media/video/uvc/uvc_driver.c 2010-06-23
10:37:03.0 +0200
+++ linux/drivers/media/video/uvc/uvc_driver.c 2010-06-23 10:37:07.0
+0200
@@ -2153,6 +2153,14 @@
.bInterfaceProtocol = 0,
.driver_info = UVC_QUIRK_PROBE_MINMAX
| UVC_QUIRK_IGNORE_SELECTOR_UNIT },
+ /* Suyin Corp. Lenovo Webcam */
+ { .match_flags = USB_DEVICE_ID_MATCH_DEVICE
+ | USB_DEVICE_ID_MATCH_INT_INFO,
+ .idVendor = 0x064e,
+ .idProduct= 0xa102,
+ .bInterfaceClass = USB_CLASS_VENDOR_SPEC,
+ .bInterfaceSubClass = 1,
+ .bInterfaceProtocol = 0 },
/* Generic USB Video Class */
{ USB_INTERFACE_INFO(USB_CLASS_VIDEO, 1, 0) },
{}
--
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
