Re: [git:media_tree/master] media: uvcvideo: Add KSMedia 8-bit IR format support
Dear Mauro, On 07/26/18 17:03, Mauro Carvalho Chehab wrote: > This is an automatic generated email to let you know that the following patch > were queued: > > Subject: media: uvcvideo: Add KSMedia 8-bit IR format support > Author: Laurent Pinchart > Date:Wed Mar 21 05:16:40 2018 -0400 > > Add support for the 8-bit IR format GUID defined in the Microsoft Kernel > Streaming Media API. > > Reported-by: Paul Menzel > Signed-off-by: Laurent Pinchart > Tested-by: Paul Menzel > Signed-off-by: Mauro Carvalho Chehab > > drivers/media/usb/uvc/uvc_driver.c | 5 + > drivers/media/usb/uvc/uvcvideo.h | 3 +++ > 2 files changed, 8 insertions(+) […] Thank you very much for accepting Laurent’s patch. Could you please tag this for the stable series (Cc: sta...@vger.kernel.org)? Kind regards, Paul smime.p7s Description: S/MIME Cryptographic Signature
Logitech QuickCam USB detected by Linux, but not user space applications
Dear Linux folks, I tried to get a Logitech QuickCam USB camera working, but unfortunately, it is not detected by user space (Cheese, MPlayer). It’s an old device, so it could be broken, but as it’s detected by the Linux kernel, I wanted to check with you first. Linux 4.18.10 from Debian Sid/unstable is used. ``` $ dmesg […] [ 2891.404361] usb 3-3: new full-speed USB device number 4 using ohci-pci [ 2891.626934] usb 3-3: New USB device found, idVendor=046d, idProduct=092e, bcdDevice= 0.00 [ 2891.626945] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2891.626951] usb 3-3: Product: Camera [ 2891.626957] usb 3-3: Manufacturer: [ 2893.110249] calling media_devnode_init+0x0/0x1000 [media] @ 11704 [ 2893.110256] media: Linux media interface: v0.10 [ 2893.110329] initcall media_devnode_init+0x0/0x1000 [media] returned 0 after 56 usecs [ 2893.210078] calling videodev_init+0x0/0x79 [videodev] @ 11704 [ 2893.210084] videodev: Linux video capture interface: v2.00 [ 2893.210123] initcall videodev_init+0x0/0x79 [videodev] returned 0 after 21 usecs [ 2893.333140] calling gspca_init+0x0/0x1000 [gspca_main] @ 11704 [ 2893.333148] gspca_main: v2.14.0 registered [ 2893.333161] initcall gspca_init+0x0/0x1000 [gspca_main] returned 0 after 3 usecs [ 2893.370672] calling sd_driver_init+0x0/0x1000 [gspca_spca561] @ 11704 [ 2893.370751] gspca_main: spca561-2.14.0 probing 046d:092e [ 2893.482675] input: spca561 as /devices/pci:00/:00:12.0/usb3/3-3/input/input17 [ 2893.485415] usbcore: registered new interface driver spca561 [ 2893.485434] initcall sd_driver_init+0x0/0x1000 [gspca_spca561] returned 0 after 112054 usecs […] $ ls -l /dev/video* crw-rw+ 1 root video 81, 0 Nov 15 09:26 /dev/video0 $ mplayer tv:// -tv driver=v4l2:device=/dev/video0 MPlayer 1.3.0 (Debian), built with gcc-8 (C) 2000-2016 MPlayer Team do_connect: could not connect to socket connect: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing tv://. TV file format detected. Selected driver: v4l2 name: Video 4 Linux 2 input author: Martin Olschewski comment: first try, more to come ;-) v4l2: your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM was used instead. Selected device: Camera Capabilities: video capture read/write streaming supported norms: inputs: 0 = spca561; Current input: 0 Current format: unknown (0x31363553) tv.c: norm_from_string(pal): Bogus norm parameter, setting default. v4l2: ioctl enum norm failed: Inappropriate ioctl for device Error: Cannot set norm! Selected input hasn't got a tuner! v4l2: ioctl set mute failed: Invalid argument v4l2: ioctl query control failed: Invalid argument v4l2: ioctl query control failed: Invalid argument == Cannot find codec matching selected -vo and video format 0x31363553. == No stream found. v4l2: ioctl set mute failed: Invalid argument v4l2: 0 frames successfully processed, 0 frames dropped. Exiting... (End of file) ``` Do you have an idea, what the issue. I know it worked fine several years ago. Kind regards, Paul smime.p7s Description: S/MIME Cryptographic Signature
Re: Logitech QuickCam USB detected by Linux, but not user space applications
Dear Mauro, Thank you very much for the quick reply. On 11/15/18 12:38, Mauro Carvalho Chehab wrote: > Em Thu, 15 Nov 2018 11:42:32 +0100 Paul Menzel escreveu: >> I tried to get a Logitech QuickCam USB camera working, but unfortunately, it >> is >> not detected by user space (Cheese, MPlayer). > > Could you please try it with Camorama? > > https://github.com/alessio/camorama Thank you for the suggestion. At first, I only saw a black image, but changing the resolution made it work. See the status below. 1. does *not* work a) 160x120 b) 176x144 2. works a) 320x240 b) 352x288 >> It’s an old device, so it could be broken, but as it’s detected by the Linux >> kernel, I wanted to check with you first. >> >> Linux 4.18.10 from Debian Sid/unstable is used. >> >> ``` >> $ dmesg >> […] >> [ 2891.404361] usb 3-3: new full-speed USB device number 4 using ohci-pci >> [ 2891.626934] usb 3-3: New USB device found, idVendor=046d, idProduct=092e, >> bcdDevice= 0.00 >> [ 2891.626945] usb 3-3: New USB device strings: Mfr=1, Product=2, >> SerialNumber=0 >> [ 2891.626951] usb 3-3: Product: Camera >> [ 2891.626957] usb 3-3: Manufacturer: >> [ 2893.110249] calling media_devnode_init+0x0/0x1000 [media] @ 11704 >> [ 2893.110256] media: Linux media interface: v0.10 >> [ 2893.110329] initcall media_devnode_init+0x0/0x1000 [media] returned 0 >> after 56 usecs >> [ 2893.210078] calling videodev_init+0x0/0x79 [videodev] @ 11704 >> [ 2893.210084] videodev: Linux video capture interface: v2.00 >> [ 2893.210123] initcall videodev_init+0x0/0x79 [videodev] returned 0 after >> 21 usecs >> [ 2893.333140] calling gspca_init+0x0/0x1000 [gspca_main] @ 11704 >> [ 2893.333148] gspca_main: v2.14.0 registered >> [ 2893.333161] initcall gspca_init+0x0/0x1000 [gspca_main] returned 0 after >> 3 usecs >> [ 2893.370672] calling sd_driver_init+0x0/0x1000 [gspca_spca561] @ 11704 >> [ 2893.370751] gspca_main: spca561-2.14.0 probing 046d:092e >> [ 2893.482675] input: spca561 as >> /devices/pci:00/:00:12.0/usb3/3-3/input/input17 >> [ 2893.485415] usbcore: registered new interface driver spca561 >> [ 2893.485434] initcall sd_driver_init+0x0/0x1000 [gspca_spca561] returned 0 >> after 112054 usecs >> […] >> $ ls -l /dev/video* >> crw-rw+ 1 root video 81, 0 Nov 15 09:26 /dev/video0 >> >> $ mplayer tv:// -tv driver=v4l2:device=/dev/video0 >> MPlayer 1.3.0 (Debian), built with gcc-8 (C) 2000-2016 MPlayer Team >> do_connect: could not connect to socket >> connect: No such file or directory >> Failed to open LIRC support. You will not be able to use your remote control. >> >> Playing tv://. >> TV file format detected. >> Selected driver: v4l2 >> name: Video 4 Linux 2 input >> author: Martin Olschewski >> comment: first try, more to come ;-) >> v4l2: your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM >> was used instead. >> Selected device: Camera >> Capabilities: video capture read/write streaming >> supported norms: >> inputs: 0 = spca561; >> Current input: 0 >> Current format: unknown (0x31363553) > > The problem is likely here: mplayer is probably not using libv4l2. Without > that, it can't decode the spca561 specific output format. It is probably > due to some option used when mplayer was built. I’ll try to look more into that in the next weeks. > In the case of Cheese, it uses Gstreamer, with defaults to not use libv4l2 > either. On newest versions of it, there is an environment var that would > allow enabling it (I don't remember what var). Thank you for the details. I’ll test that next week. […] Kind regards, Paul smime.p7s Description: S/MIME Cryptographic Signature
Re: Logitech QuickCam USB detected by Linux, but not user space applications
Dear Hans, Am 22.11.18 um 13:43 schrieb Hans Verkuil: On 11/16/2018 03:39 PM, Paul Menzel wrote: On 11/15/18 12:38, Mauro Carvalho Chehab wrote: Em Thu, 15 Nov 2018 11:42:32 +0100 Paul Menzel escreveu: I tried to get a Logitech QuickCam USB camera working, but unfortunately, it is not detected by user space (Cheese, MPlayer). Could you please try it with Camorama? https://github.com/alessio/camorama Thank you for the suggestion. At first, I only saw a black image, but changing the resolution made it work. See the status below. 1. does *not* work a) 160x120 b) 176x144 2. works a) 320x240 b) 352x288 Try this patch: https://patchwork.linuxtv.org/patch/53043/ It probably fixes the same problem you are experiencing. It indeed does. I cherry picked it to Linus’ master branch, and it fixed the problem. Tested-by: Paul Menzel (Logitech QuickCam 046d:092e) […] Kind regards, Paul
Supportive (TV) hardware manufactures/companies
Dear list, I am planning on buying (USB) DVB-T hardware. One of my criteria is to buy a product from a company supporting GNU/Linux or free driver development (code, hardware, etc.). I did only find this message [1] about TechnoTrend Görler GmbH and Terratec has an extra URL for GNU/Linux [2]. There were no information about manufacturers supporting free drivers in the German article about hardware support in the Linux kernel in the Linux Magazin 8/2008 [3 »Webcams und DVB-Empfänger«, not yet freely available]. Could you please give me some information about this, what buying decision would most profit your goals/free drivers. Thanks, Paul [1] http://www.mail-archive.com/linux-media@vger.kernel.org/msg05625.html [2] http://linux.terratec.de/ [3] http://www.linux-magazin.de/Heft-Abo/Ausgaben/2008/08 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
dib0700 diversity support
Dear DVB hackers, (please CC) I traded an unsupported Terratec Cinergy HTC USB XS HD with a TerraTec Cinergy DT USB XS Diversity [1]. As written in [1] it has a bad reception. It uses the dib0700 driver and the DiB0700 seems to support a diversity feature which supposedly improves the signal quality by combining both tuner(?). This feature is not supported yet by the dib0700 driver [2]. Will this feature ever be supported? Is documentation available? Is somebody working on it? Thanks a lot, Paul [1] http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_DT_USB_XS_Diversity [2] http://www.linuxtv.org/pipermail/linux-dvb/2007-July/019375.html signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: dib0700 diversity support
Dear Patrick, Am Freitag, den 14.08.2009, 09:56 +0200 schrieb Patrick Boettcher: > On Thu, 13 Aug 2009, Paul Menzel wrote: > > I traded an unsupported Terratec Cinergy HTC USB XS HD with a TerraTec > > Cinergy DT USB XS Diversity [1]. > > > > As written in [1] it has a bad reception. [Patrick’s explanation of diversity feature] > The cut things short, what is stated on the wiki is unfortunately correct, > the sensitivity of the used tuner is not very good; but this is due to an > outdated-driver. Thanks for your answer and explanation. > I have an update for the dib0070-tuner-driver ready, which hopefully > improves reception quality for low-sensitivity channels. > > I'll post a request for testing soon. I am looking forward to it. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: dib0700 diversity support
Dear Patrick, Am Dienstag, den 18.08.2009, 10:54 +0200 schrieb Patrick Boettcher: > On Fri, 14 Aug 2009, Paul Menzel wrote: > >> I'll post a request for testing soon. > > > > I am looking forward to it. > > Can you please try the drivers from here: > http://linuxtv.org/hg/~pb/v4l-dvb/ I installed it as described in [1]. # clone make sudo make install sudo make unload # insert stick again [1] http://sidux.com/module-Wikula-history-tag-TerraTec.html Thanks for your work. Do I also need to update the firmware file? > In the best case they improve the situation for you. In the worst case > (not wanted :) ) it will degrade. Ok, I do not know how to test this objectively. Not knowing what how to do this, I just insert the console output of Kaffeine while scanning for channels. See the end of this message. In summary I would they I did not see any difference in quality between the two versions at a bad reception spot. I thought the signal bar showed values increased by 2–4 %, so a little bit better. I will test later at a better reception point. Thanks for your work, Paul ### Old Version 2.6.30.4, amd64 ### • tested channel between 40 and 44 % signal shown by Kaffeine /dev/dvb/adapter0/frontend0 : opened ( DiBcom 7000PC ) /dev/dvb/adapter1/frontend0 : opened ( DiBcom 7000PC ) 0 EPG plugins loaded for device 0:0. 0 EPG plugins loaded for device 1:0. Loaded epg data : 0 events (0 msecs) Tuning to: TSID:769-SID:16408 / autocount: 0 DvbCam::probe(): /dev/dvb/adapter0/ca0: : Datei oder Verzeichnis nicht gefunden Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 65800 Hz inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 . LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 850 ms pipe opened demux_wavpack: (open_wv_file:127) open_wv_file: non-seekable inputs aren't supported yet. xine pipe opened /home/paul/.kaxtv.ts DvbCam::probe(): /dev/dvb/adapter1/ca0: : Datei oder Verzeichnis nicht gefunden Invalid section length or timeout: pid=17 Invalid section length or timeout: pid=0 dvbsi: The end :) Channels found: 0 Asked to stop pipe closed Live stopped dvbstream::run() end dvbEvents 0:0 ended fdDvr closed Frontend closed Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 17750 Hz inv:2 bw:1 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 ... LOCKED. Transponders: 1/57 scanMode=0 it's dvb 2! Invalid section length or timeout: pid=17 Invalid section length or timeout: pid=0 Frontend closed Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 18450 Hz inv:2 bw:1 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 ... Not able to lock to the signal on the given frequency Frontend closed dvbsi: Cant tune DVB Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 19150 Hz inv:2 bw:1 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 ... Not able to lock to the signal on the given frequency Frontend closed dvbsi: Cant tune DVB Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 19850 Hz inv:2 bw:1 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 ... Not able to lock to the signal on the given frequency Frontend closed dvbsi: Cant tune DVB Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 20550 Hz inv:2 bw:1 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 ... Not able to lock to the signal on the given frequency Frontend closed dvbsi: Cant tune DVB Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 21250 Hz inv:2 bw:1 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 ... Not able to lock to the signal on the given frequency Frontend closed dvbsi: Cant tune DVB Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 21950 Hz inv:2 bw:1 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 ... Not able to lock to the signal on the given frequency Frontend closed dvbsi: Cant tune DVB Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 22650 Hz inv:2 bw:1 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 ... Not able to lock to the signal on the given frequency Frontend closed dvbsi: Cant tune DVB Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 47400 Hz inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 ... Not able to lock to the signal on the given frequency Frontend closed dvbsi: Cant tune DVB Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 48200 Hz inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 ... Not able to lock to the signal on the given frequency Frontend closed dvbsi: Cant tune DVB Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 49000 Hz inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4 ... Not able to lock to the signal on the given frequency Frontend closed dvbsi: Cant tune DVB Using DVB device 0:0 "DiBcom 7000PC" tuning DVB-T to 49800 Hz inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 g
[Request for testing] new dib0700 code (was: Re: dib0700 diversity support)
Dear Patrick, Am Dienstag, den 18.08.2009, 12:27 +0200 schrieb Patrick Boettcher: > On Tue, 18 Aug 2009, Paul Menzel wrote: > > Am Dienstag, den 18.08.2009, 10:54 +0200 schrieb Patrick Boettcher: > >> On Fri, 14 Aug 2009, Paul Menzel wrote: > >>>> I'll post a request for testing soon. > >>> > >>> I am looking forward to it. > >> > >> Can you please try the drivers from here: > >> http://linuxtv.org/hg/~pb/v4l-dvb/ > > > > I installed it as described in [1]. > > > ># clone > >make > >sudo make install > >sudo make unload > ># insert stick again > > > > [1] http://sidux.com/module-Wikula-history-tag-TerraTec.html […] > > Ok, I do not know how to test this objectively. Not knowing what how to > > do this, I just insert the console output of Kaffeine while scanning for > > channels. See the end of this message. Are those values showing the signal strength? > > In summary I would they I did not see any difference in quality between > > the two versions at a bad reception spot. I thought the signal bar > > showed values increased by 2?4 %, so a little bit better. > > Can be weather conditions I tested both version in a 30 minutes time frame. > The SNR could give a clue how far you are away from receiving, but it is > currently not implemented. > > I hate to request it, but can you try the windows driver with the device > without touching the antenna at that point. Like that we can exclude any Well, I cannot do it right now. But I can test it the Wednesday next week. I hope this is alright. Maybe some other people can test it sooner. (I therefore changed the subject.) Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Compile modules on 64-bit Linux kernel system for 686 Linux kernel
Hi guys, ( please CC ) I am running Debian Sid/unstable with a 32-bit userspace with a 64-bit kernel [1]. I want to compile the v4l-dvb modules for a 686 kernel [2] on this system. I installed the header files for the 686 kernel [3], but running $ ARCH=686 make make -C /tmp/v4l-dvb/v4l make[1]: Entering directory `/tmp/v4l-dvb/v4l' perl scripts/make_config_compat.pl /lib/modules/2.6.30-1-amd64/source ./.myconfig ./config-compat.h creating symbolic links... make -C firmware prep make[2]: Entering directory `/tmp/v4l-dvb/v4l/firmware' make[2]: Leaving directory `/tmp/v4l-dvb/v4l/firmware' make -C firmware make[2]: Entering directory `/tmp/v4l-dvb/v4l/firmware' CC ihex2fw Generating vicam/firmware.fw Generating dabusb/firmware.fw Generating dabusb/bitstream.bin Generating ttusb-budget/dspbootcode.bin Generating cpia2/stv0672_vp4.bin Generating av7110/bootcode.bin make[2]: Leaving directory `/tmp/v4l-dvb/v4l/firmware' Kernel build directory is /lib/modules/2.6.30-1-amd64/build make -C /lib/modules/2.6.30-1-amd64/build SUBDIRS=/tmp/v4l-dvb/v4l modules make[2]: Entering directory `/usr/src/linux-headers-2.6.30-1-amd64' […] still uses the 64-bit modules in /lib/modules/2.6.30-1-amd64 and the files in /usr/src/linux-headers-2.6.30-1-amd64. I do not even know if this is the correct way. Can someone of you please enlighten me? Thanks, Paul [1] http://packages.debian.org/de/sid/linux-image-2.6.30-1-amd64 [2] http://packages.debian.org/de/sid/linux-image-2.6.30-1-686 [3] http://packages.debian.org/de/sid/linux-headers-2.6.30-1-686 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Compile modules on 64-bit Linux kernel system for 686 Linux kernel
Dear Mauro, Am Donnerstag, den 27.08.2009, 08:58 -0300 schrieb Mauro Carvalho Chehab: > Em Thu, 27 Aug 2009 13:28:57 +0200 Paul Menzel > escreveu: > > I am running Debian Sid/unstable with a 32-bit userspace with a 64-bit > > kernel [1]. I want to compile the v4l-dvb modules for a 686 kernel [2] > > on this system. > > > > I installed the header files for the 686 kernel [3], but running > > > > $ ARCH=686 make […] > > I do not even know if this is the correct way. > > > > Can someone of you please enlighten me? > > This is not the correct way. You'll need to also point where do you expect it > to get the headers: > This should do the trick: > make ARCH=i386 release DIR= > make ARCH=i386 allmodconfig > make ARCH=i386 Thanks, I should have read INSTALL more carefully. I did $ make ARCH=i686 release VER=2.6.30-1-686 $ make ARCH=i686 allmodconfig $ make ARCH=i686 which worked like a charm. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
[Request for testing] new dib0700 code (was: Re: dib0700 diversity support)
Dear Patrick, Am Dienstag, den 18.08.2009, 12:27 +0200 schrieb Patrick Boettcher: > On Tue, 18 Aug 2009, Paul Menzel wrote: > > Am Dienstag, den 18.08.2009, 10:54 +0200 schrieb Patrick Boettcher: > >> On Fri, 14 Aug 2009, Paul Menzel wrote: > >>>> I'll post a request for testing soon. > >>> > >>> I am looking forward to it. > >> > >> Can you please try the drivers from here: > >> http://linuxtv.org/hg/~pb/v4l-dvb/ > > > > I installed it as described in [1]. > > > ># clone > >make > >sudo make install > >sudo make unload > ># insert stick again > > > > [1] http://sidux.com/module-Wikula-history-tag-TerraTec.html > > > > Thanks for your work. Do I also need to update the firmware file? > > No. > > > Ok, I do not know how to test this objectively. Not knowing what how to > > do this, I just insert the console output of Kaffeine while scanning for > > channels. See the end of this message. > > > > In summary I would they I did not see any difference in quality between > > the two versions at a bad reception spot. I thought the signal bar > > showed values increased by 2?4 %, so a little bit better. > > Can be weather conditions > > The SNR could give a clue how far you are away from receiving, but it is > currently not implemented. > > I hate to request it, but can you try the windows driver with the device > without touching the antenna at that point. Like that we can exclude any Ok, today I was able to test both setups. Do you know how I can output the signal quality under Windows? I downloaded the TerraTec BDA driver version 3.12.0.0 [1] and used Power Cinema [2], where the UI frooze every minute for over two minutes. ;-) On the bad reception spot the picture is pretty bad too and scanning for channels failed for both systems. Using an existing channel configuration every four or five seconds it stops and makes a high pitch noise under windows. I tried ScanChannelsBDA_UK to measure the quality under Windows [3] but did not get any results before it crashed. ;-) Testing on a better spot, the picture under Windows was quite perfect and trying this on Linux sometimes there were some green blocks but very rarely. I noticed though that playing VOX was (for my eyes) perfect under Windows and also in the beginning with Kaffeine, but after 10 or 15 seconds it really got worse and even the audio was not vanished and bad artifacts were shown. I hope you can see that from the logs. To make it clear, this did not happen under Windows. Is there an easy way to install the standard modules so I can test if that also happens with the distributed modules? Leafing the degrading quality over time with VOX out my subjective opinion is that your new driver improves the situation. Both log files are from your version of the module. I first tested under GNU/Linux (1st), then unplugged it and tested under Windows, unplugged it and tested it under GNU/Linux again (2nd). The antenna was not moved in this timeframe. Please tell me if I should provide other information. Thanks, Paul [1] http://www.terratec.net/de/treiber-und-support/treiber_21178.html?selectproduct=Cinergy%20DT%20USB%20XS%20Diversity [2] http://de.cyberlink.com/products/powercinema/overview_de_DE.html [3] http://www.xpmediacentre.com.au/community/tuners-windows-7/38177-tuner-quality-signal-strength-app.html $ dmesg | less [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.30-1-686 (Debian 2.6.30-6) (wa...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-1) ) #1 SMP Sat Aug 15 19:11:58 UTC 2009 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] NSC Geode by NSC [0.00] Cyrix CyrixInstead [0.00] Centaur CentaurHauls [0.00] Transmeta GenuineTMx86 [0.00] Transmeta TransmetaCPU [0.00] UMC UMC UMC UMC [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e4000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 1f78 (usable) [0.00] BIOS-e820: 1f78 - 1f79 (ACPI data) [0.00] BIOS-e820: 1f79 - 1f7d (ACPI NVS) [0.00] BIOS-e820: 1f7d - 1f7de000 (reserved) [0.00] BIOS-e820: 1f7e - 1f80 (reserved) ...skipping... [ 3083.285158] usb 1-4: configuration #1 chosen from 1 choice [ 3083.582253] dib0700: loaded with support for 11 different device-types [ 308
uvcvideo: Unknown video format,00000032-0002-0010-8000-00aa00389b71
Dear Linux folks, On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below. ``` [2.338094] calling uvc_init+0x0/0x1000 [uvcvideo] @ 295 [2.338569] calling iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @ 280 [2.338570] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [2.338713] iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400) [2.338755] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:58f4) [2.338827] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [2.338851] initcall iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] returned 0 after 271 usecs [2.340669] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized! [2.340670] uvcvideo 1-5:1.0: Entity type for entity Extension 7 was not initialized! [2.340672] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized! [2.340673] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized! [2.340736] input: Integrated_Webcam_HD: Integrate as /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input9 [2.341447] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 [2.341450] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:58f4) [2.343371] uvcvideo: Unable to create debugfs 1-2 directory. [2.343420] uvcvideo 1-5:1.2: Entity type for entity Extension 10 was not initialized! [2.343422] uvcvideo 1-5:1.2: Entity type for entity Extension 12 was not initialized! [2.343423] uvcvideo 1-5:1.2: Entity type for entity Processing 9 was not initialized! [2.343424] uvcvideo 1-5:1.2: Entity type for entity Camera 11 was not initialized! [2.343472] input: Integrated_Webcam_HD: Integrate as /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.2/input/input10 [2.343496] usbcore: registered new interface driver uvcvideo [2.343496] USB Video Class driver (1.1.1) [2.343501] initcall uvc_init+0x0/0x1000 [uvcvideo] returned 0 after 5275 usecs ``` Please tell me, what I can do to improve the situation. Kind regards, Paul smime.p7s Description: S/MIME Cryptographic Signature
Re: uvcvideo: Unknown video format,00000032-0002-0010-8000-00aa00389b71
Dear Laurent, On 03/20/18 14:30, Laurent Pinchart wrote: On Tuesday, 20 March 2018 14:20:14 EET Paul Menzel wrote: On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below. ``` […] [2.340736] input: Integrated_Webcam_HD: Integrate as /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input9 [2.341447] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 >> [2.341450] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:58f4) […] ``` Please tell me, what I can do to improve the situation. Some vendors routinely implement new formats without bothering to send a patch for the uvcvideo driver. It would be easy to do so, but it requires knowing which format is meant by the GUID. Most format GUIDs are of the form 32595559--0010-8000-00aa00389b71 that starts with a 4CC, but that's not the case here. I am adding Mario to the receiver list, though he is currently on vacation. Could you send me the output of lsusb -v -d 0bda:58f4 running as root if possible ? Sure, please find it attached. Kind regards, Paul Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 76.05 iManufacturer 3 CN0FFMHCLOG0081JBA49A00 iProduct1 Integrated_Webcam_HD iSerial 2 200901010001 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 1047 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 4 USB Camera bmAttributes 0x80 (Bus Powered) MaxPower 500mA ** UNRECOGNIZED: 28 ff 42 49 53 54 00 01 06 07 10 00 00 00 00 00 01 08 f4 01 02 09 f4 01 03 0a f4 01 04 0b f4 01 05 0c f4 01 06 0d e8 03 Interface Association: bLength 8 bDescriptorType11 bFirstInterface 0 bInterfaceCount 2 bFunctionClass 14 Video bFunctionSubClass 3 Video Interface Collection bFunctionProtocol 0 iFunction 5 Integrated Webcam Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass14 Video bInterfaceSubClass 1 Video Control bInterfaceProtocol 0 iInterface 5 Integrated Webcam VideoControl Interface Descriptor: bLength13 bDescriptorType36 bDescriptorSubtype 1 (HEADER) bcdUVC 1.00 wTotalLength 107 dwClockFrequency 15.00MHz bInCollection 1 baInterfaceNr( 0) 1 VideoControl Interface Descriptor: bLength18 bDescriptorType36 bDescriptorSubtype 2 (INPUT_TERMINAL) bTerminalID 1 wTerminalType 0x0201 Camera Sensor bAssocTerminal 0 iTerminal 0 wObjectiveFocalLengthMin 0 wObjectiveFocalLengthMax 0 wOcularFocalLength0 bControlSize 3 bmControls 0x000e Auto-Exposure Mode Auto-Exposure Priority Exposure Time (Absolute) VideoControl Interface Descriptor: bLength11 bDescriptorType36 bDescriptorSubtype 5 (PROCESSING_UNIT) Warning: Descriptor too short bUnitID 2 bSourceID 1 wMaxMultiplier 0 bControlSize2 bmControls 0x177f Brightness Contrast Hue Saturation Sharpness Gamma White Balance Temperature Backlight Compensation Gain Power Line Frequency White Balance Temperature, Auto iProcessing 0 bmVideoStandards 0x 9 None SECAM - 625/50 VideoControl Interface Descriptor: bLength 9 bDescriptorType36 bDescriptorSubtype 3 (OUTPUT_TERMINAL) bTerminalID 3 wTerminalType 0x0101 USB Streaming bAssocTerminal 0 bSourceID 4 iTerminal 0 VideoControl Interface Descriptor: bLength27 bDescriptorTyp
Re: uvcvideo: Unknown video format,00000032-0002-0010-8000-00aa00389b71
Dear Laurent,
On 03/21/2018 10:25 AM, Laurent Pinchart wrote:
On Tuesday, 20 March 2018 18:46:24 EET Paul Menzel wrote:
On 03/20/18 14:30, Laurent Pinchart wrote:
On Tuesday, 20 March 2018 14:20:14 EET Paul Menzel wrote:
On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
```
[…]
[2.340736] input: Integrated_Webcam_HD: Integrate as
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input9
[2.341447] uvcvideo: Unknown video format
0032-0002-0010-8000-00aa00389b71 >> [2.341450] uvcvideo: Found
UVC 1.00 device Integrated_Webcam_HD (0bda:58f4)
[…]
```
Please tell me, what I can do to improve the situation.
Some vendors routinely implement new formats without bothering to send a
patch for the uvcvideo driver. It would be easy to do so, but it requires
knowing which format is meant by the GUID. Most format GUIDs are of the
form 32595559--0010-8000-00aa00389b71 that starts with a 4CC, but
that's not the case here.
I am adding Mario to the receiver list, though he is currently on vacation.
Could you send me the output of
lsusb -v -d 0bda:58f4
running as root if possible ?
Sure, please find it attached.
Thank you.
Could you please try the following patch ?
commit 7b3dea984b380f5b4b5c1956a9c6c23966af2149
Author: Laurent Pinchart
Date: Wed Mar 21 11:16:40 2018 +0200
media: uvcvideo: Add KSMedia 8-bit IR format support
Add support for the 8-bit IR format GUID defined in the Microsoft Kernel
Streaming Media API.
Reported-by: Paul Menzel
Signed-off-by: Laurent Pinchart
diff --git a/drivers/media/usb/uvc/uvc_driver.c
b/drivers/media/usb/uvc/uvc_driver.c
index 2469b49b2b30..3691d87ef869 100644
--- a/drivers/media/usb/uvc/uvc_driver.c
+++ b/drivers/media/usb/uvc/uvc_driver.c
@@ -99,6 +99,11 @@ static struct uvc_format_desc uvc_fmts[] = {
.guid = UVC_GUID_FORMAT_D3DFMT_L8,
.fcc= V4L2_PIX_FMT_GREY,
},
+ {
+ .name = "IR 8-bit (L8_IR)",
+ .guid = UVC_GUID_FORMAT_KSMEDIA_L8_IR,
+ .fcc= V4L2_PIX_FMT_GREY,
+ },
{
.name = "Greyscale 10-bit (Y10 )",
.guid = UVC_GUID_FORMAT_Y10,
diff --git a/drivers/media/usb/uvc/uvcvideo.h b/drivers/media/usb/uvc/uvcvideo.h
index be5cf179228b..6b955e0dd956 100644
--- a/drivers/media/usb/uvc/uvcvideo.h
+++ b/drivers/media/usb/uvc/uvcvideo.h
@@ -157,6 +157,9 @@
#define UVC_GUID_FORMAT_D3DFMT_L8 \
{0x32, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, \
0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}
+#define UVC_GUID_FORMAT_KSMEDIA_L8_IR \
+ {0x32, 0x00, 0x00, 0x00, 0x02, 0x00, 0x10, 0x00, \
+0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71}
/*
Sure. After fighting how to apply with Mozilla Thunderbird as my mailer
– hints are welcome –, the warning is gone.
```
[2.569788] calling uvc_init+0x0/0x1000 [uvcvideo] @ 297
[2.570011] calling cryptd_init+0x0/0x1000 [cryptd] @ 287
[2.570018] cryptd: max_cpu_qlen set to 1000
[2.570022] initcall cryptd_init+0x0/0x1000 [cryptd] returned 0 after
7 usecs
[2.570030] calling init_nls_cp437+0x0/0x1000 [nls_cp437] @ 332
[2.570033] initcall init_nls_cp437+0x0/0x1000 [nls_cp437] returned 0
after 0 usecs
[2.570502] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
(0bda:58f4)
[2.573583] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was
not initialized!
[2.573585] uvcvideo 1-5:1.0: Entity type for entity Extension 7 was
not initialized!
[2.573586] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was
not initialized!
[2.573587] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not
initialized!
[2.573652] input: Integrated_Webcam_HD: Integrate as
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input10
[2.574192] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
(0bda:58f4)
[2.575629] proc_thermal :00:04.0: enabling device ( -> 0002)
[2.576052] uvcvideo: Unable to create debugfs 1-2 directory.
[2.576118] uvcvideo 1-5:1.2: Entity type for entity Extension 10 was
not initialized!
[2.576119] uvcvideo 1-5:1.2: Entity type for entity Extension 12 was
not initialized!
[2.576120] uvcvideo 1-5:1.2: Entity type for entity Processing 9 was
not initialized!
[2.576121] uvcvideo 1-5:1.2: Entity type for entity Camera 11 was
not initialized!
[2.576184] input: Integrated_Webcam_HD: Integrate as
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.2/input/input11
[2.576229] usbcore: registered new interface driver uvcvideo
[2.576230] USB Video Class driver (1.1.1)
[2.576236] initcall uvc_init+0x0/0x1000 [uvcvideo] returned 0 after
6290 usecs
```
Tested-by: Paul Menzel
Kind regards,
Paul
Re: [PATCH v4 1/1] video: drm: exynos: Adds display-timing node parsing using video helper function
Dear Vikas,
thank you for the patch. Please send a fifth iteration with the
following changes to the commit message.
Am Dienstag, den 05.02.2013, 11:02 +0530 schrieb Vikas Sajjan:
The summary should not implicitly assume »patch« written before it. So
do not add third person s to »Add«.
video: drm: exynos: Add display-timing node parsing using video helper
function
> This patch adds display-timing node parsing using video helper function
As this is the same as the summary you should leave it out. Also it is
good style not to use »This/The patch« in the commit message.
Please use the commit message to explain your change. For example the if
statement. Why is the original code put into the else branch and is not
needed if the first condition is true?
> Signed-off-by: Leela Krishna Amudala
> Signed-off-by: Vikas Sajjan
> ---
> drivers/gpu/drm/exynos/exynos_drm_fimd.c | 41
> +++---
> 1 file changed, 37 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c
> b/drivers/gpu/drm/exynos/exynos_drm_fimd.c
> index bf0d9ba..978e866 100644
> --- a/drivers/gpu/drm/exynos/exynos_drm_fimd.c
> +++ b/drivers/gpu/drm/exynos/exynos_drm_fimd.c
> @@ -19,6 +19,7 @@
> #include
> #include
> #include
> +#include
>
> #include
> #include
> @@ -905,16 +906,48 @@ static int __devinit fimd_probe(struct platform_device
> *pdev)
> struct exynos_drm_subdrv *subdrv;
> struct exynos_drm_fimd_pdata *pdata;
> struct exynos_drm_panel_info *panel;
> + struct fb_videomode *fbmode;
> + struct pinctrl *pctrl;
> struct resource *res;
> int win;
> int ret = -EINVAL;
>
> DRM_DEBUG_KMS("%s\n", __FILE__);
>
> - pdata = pdev->dev.platform_data;
> - if (!pdata) {
> - dev_err(dev, "no platform data specified\n");
> - return -EINVAL;
> + if (pdev->dev.of_node) {
> + pdata = devm_kzalloc(dev, sizeof(*pdata), GFP_KERNEL);
> + if (!pdata) {
> + DRM_ERROR("memory allocation for pdata failed\n");
> + return -ENOMEM;
> + }
> +
> + fbmode = devm_kzalloc(dev, sizeof(*fbmode), GFP_KERNEL);
> + if (!fbmode) {
> + DRM_ERROR("memory allocation for fbmode failed\n");
> + return -ENOMEM;
> + }
> +
> + ret = of_get_fb_videomode(dev->of_node, fbmode, -1);
> + if (ret) {
> + DRM_ERROR("failed: of_get_fb_videomode() :"
> + "return value: %d\n", ret);
> + return ret;
> + }
> + pdata->panel.timing = (struct fb_videomode) *fbmode;
> +
> + pctrl = devm_pinctrl_get_select_default(dev);
> + if (IS_ERR_OR_NULL(pctrl)) {
> + DRM_ERROR("failed: devm_pinctrl_get_select_default()"
> + "return value: %d\n", PTR_RET(pctrl));
> + return PTR_RET(pctrl);
> + }
> +
> + } else {
> + pdata = pdev->dev.platform_data;
> + if (!pdata) {
> + DRM_ERROR("no platform data specified\n");
> + return -EINVAL;
> + }
> }
>
> panel = &pdata->panel;
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
