- 26 Feb, 2010 40 commits
-
-
Jean-Francois Moine authored
The USB video interface was checked as having the number zero, but some webcams have other values. The test is now done on the interface class which may be either 255 (vendor spec) or 0 (class per interface). Signed-off-by:
Jean-Francois Moine <moinejf@free.fr> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
Jean-Francois Moine authored
- adapt the start sequences from the info file of the ms-win driver of the webcams 046d:08a2/046d:08aa (lvWIMv.inf) - disable the brightness for this sensor Signed-off-by:
-
Jean-Francois Moine authored
The previous calculation gave bad gamma tables. Signed-off-by:
-
Jean-Francois Moine authored
- sharpness - brightness for adcm1700 - adjust brightness/exposure for adcm1700 - add some comments Signed-off-by:
-
Jean-Francois Moine authored
- new sensor POxxxx (unknown ID) - no probe - new controls - table for the disabled controls Signed-off-by:
-
Jean-Francois Moine authored
Signed-off-by:
-
Jean-Francois Moine authored
- have 2 tables for sensor probe - with the same ID, the sensor mi1320 is found with the bridge vc0321, the sensor mi1320_soc with the bridge vc0323 - add some comments Signed-off-by: -
Antoine Jacquet authored
Added a new initialization method for Aiptek DV T300. Addresses http://bugzilla.kernel.org/show_bug.cgi?id=13708Tested-by:
Hámorszky Balázs <balihb@gmail.com> Signed-off-by:
Antoine Jacquet <royale@zerezo.com> Signed-off-by:
-
Erik Andrén authored
Currently all probed sensor types are emitted in the kernel log, generating unnecessary noise. Be less verbose and only report what sensor is found (if any) Signed-off-by:
Erik Andrén <erik.andren@gmail.com> Signed-off-by:
-
Erik Andrén authored
Signed-off-by:
-
Mauro Carvalho Chehab authored
When printing that an iocl were called, report the ioctl number. Signed-off-by: -
Mauro Carvalho Chehab authored
Signed-off-by: -
Jean-Francois Moine authored
Signed-off-by:
-
Jean-Francois Moine authored
Tested-by:
Francesco Lavra <francescolavra@interfree.it> Signed-off-by:
-
Jean-Francois Moine authored
The webcam 0ac8:303b may have the sensors HV7131B or HV7131R(c). This changeset checks the HV7131 type. Signed-off-by:
-
Luis Maia authored
This ID was found in a webcam 0ac8:301b. Signed-off-by:
Luis Maia <lmaia@royalhat.org> Signed-off-by:
-
Jean-Francois Moine authored
This flag permits subdrivers to create specific transfer URBs. Signed-off-by:
-
Jean-Francois Moine authored
Signed-off-by:
-
Mauro Carvalho Chehab authored
/home/v4l/buildtest/v4l-dvb-master/v4l/ir-keytable.c: In function 'ir_setkeycode': /home/v4l/buildtest/v4l-dvb-master/v4l/ir-keytable.c:190: warning: 'newkeymap' may be used uninitialized in this function Signed-off-by: -
Mauro Carvalho Chehab authored
Now, if RF is locked but demod is not locked, it will report: >>> tuning status == 0x03 This happens, for example, if the device is on DVB-T, and the video standard is ISDB-T. Signed-off-by: -
Mauro Carvalho Chehab authored
Signed-off-by: -
Mauro Carvalho Chehab authored
After taking a look at the driver's history and doing some tests with DVB and ISDB-T, it was noticed that the stats were incomplete, for ISDB-T, and weren't working for DVB. Fixed the code and added a debug code to print the complete stats at dmesg. This debug is useful to improve the stats of this driver. Signed-off-by: -
Mauro Carvalho Chehab authored
Bandwidth is in Hz, not in kHz. Signed-off-by: -
Mauro Carvalho Chehab authored
Signed-off-by: -
Mauro Carvalho Chehab authored
Cc: Patrick Boettcher <pboettcher@kernellabs.com> Signed-off-by: -
Mauro Carvalho Chehab authored
Based on a patch originally written by Michael Krufky <mkrufky@linuxtv.org> for a preliminar S2API spec. The patch were ported to the S2API and had the ISDB-T API additions to honor the auto mode, while keep allowing manual tuning. Tested with both the original dvb-apps and the new dvb-apps-isdbt scan, that uses a different channel.conf and uses S2API with ISDB-T extensions. Thanks-to: Michael Krufky <mkrufky@linuxtv.org> for his first version Signed-off-by: -
Mauro Carvalho Chehab authored
Siano series of patches seemed to cause a regression on reporting DTV statistics. Due to that, signal indication weren't received, preventing applications like scan to work. Tested with ISDB-T signals and got the same scan result as with a dib0700/dib8000 device. Signed-off-by: -
Michael Krufky authored
Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
-
Michael Krufky authored
Activate ISDB-T mode using module option default_mode=6. hack: use 4 lower bits in frequency for segment number [mchehab@redhat.com: fix merge conflicts and CodingStyle] Signed-off-by:
-
David Wong authored
Improves ATBM8830 reception by using per card AGC configuration rather than register default. Signed-off-by:
David T. L. Wong <davidtlwong@gmail.com> Signed-off-by:
-
Mauro Carvalho Chehab authored
Signed-off-by: -
Daniel Ritz authored
For some unknown reason, on a MacBookPro5,3 the iSight sometimes report a different video format GUID. This patch add the other (wrong) GUID to the format table, making the iSight work always w/o other problems. What it should report: 32595559-0000-0010-8000-00aa00389b71 What it often reports: 32595559-0000-0010-8000-000000389b71 Signed-off-by:
Daniel Ritz <daniel.ritz@gmx.ch> Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by:
-
Laurent Pinchart authored
The quirks module parameter is or'ed with the built-in quirks for the device being probed. This make it impossible to disable a built-in quirk without recompiling the driver. Replace the built-in quirks with the quirks module parameter instead of or'ing the values. Signed-off-by:
-
Laurent Pinchart authored
The realtime clock provided by do_gettimeofday() is affected by time jumps caused by NTP or DST. Furthermore, preliminary investigation showed that SMP systems the realtime clock is based on the CPU TSC, and those could get slightly out of sync, resulting in jitter in the timestamps depending on which processor handles the USB interrupts. Instead of the realtime clock, use a monotonic high resolution clock to timestamp the buffer. As this could in theory introduce a regression with some userspace applications expecting a realtime clock timestamp, add a module parameter to switch back to the realtime clock. Thanks to Paulo Assis for pointing out and investigating the issue. Signed-off-by:
-
Mauro Carvalho Chehab authored
As currently most drivers don't define ir_dev->props, we shouldn't assume that this field is defined. Signed-off-by: -
Igor M. Liplianin authored
The card based on stv0903 demod, stb6100 tuner. Signed-off-by:
Igor M. Liplianin <liplianin@me.by> Signed-off-by:
-
Jean-Francois Moine authored
Signed-off-by:
-
Mauro Carvalho Chehab authored
When preparing the linux-next patches, I got those errors: include/media/ir-core.h:29: warning: left shift count >= width of type In file included from include/media/ir-common.h:29, from drivers/media/video/ir-kbd-i2c.c:50: drivers/media/video/ir-kbd-i2c.c: In function ‘ir_probe’: drivers/media/video/ir-kbd-i2c.c:324: warning: left shift count >= width of type Unfortunately, enum is 32 bits on i386. As we define IR_TYPE_OTHER as 1<<63, it won't work on non 64 bits arch. Signed-off-by: -
Mauro Carvalho Chehab authored
Signed-off-by: -
Mauro Carvalho Chehab authored
Signed-off-by:
-
