- 21 Oct, 2010 40 commits
-
-
Hans Verkuil authored
Signed-off-by:
Hans Verkuil <hverkuil@xs4all.nl> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Remove the V4L1 API from this driver, making it fully V4L2. Also fix a bug where the /dev/videoX device was created too early, which led to initialization problems of the camera, making it unable to capture video. Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
The VIDIOC_QUERYMENU documentation was not correct. EINVAL can be returned if the driver does not support some of the menu items. I.e. in a list of MPEG bitrates a driver generally supports only a subset of these. This behavior has been in place for years, but was never properly documented. Signed-off-by:
-
Hans Verkuil authored
We forgot to add this capability to the QUERYCAP documentation. Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Andy Walls authored
The illuminator controls should only be available to the user for the Intel Play QX3 microscope. The implementation to inhibit the controls is intended to be consistent with the other gspca driver implementations. Signed-off-by:
Andy Walls <awalls@md.metrocast.net> Signed-off-by:
Jean-François Moine <moinejf@free.fr> Signed-off-by:
-
Andy Walls authored
Turn the lights of the QX3 on (or off) as needed when resuming and at module load. Signed-off-by:
-
Andy Walls authored
This patch adds basic V4L2 controls for the illuminators on the Intel Play QX3 microscope. Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Signed-off-by:
-
Jean-François Moine authored
Some media devices (microscopes) may have one or many illuminators. This patch makes them controlable by the applications. Acked-by:
-
Alexander Goncharov authored
Signed-off-by:
Alexander Goncharov <alexzandersss@gmail.com> Signed-off-by:
-
Jean-François Moine authored
Tested-by:
Simon Danner <simon@danner-urloffen.de> Signed-off-by:
-
Jean-François Moine authored
When compressed, the images take less than one byte per pixel. Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Antti Palosaari authored
Replace 2nd demod default address 0x3a with value got from eeprom config. Signed-off-by:
Antti Palosaari <crope@iki.fi> Signed-off-by:
-
Antti Palosaari authored
Optimize af9013_set_coeff(). Move configuration values to own table. Signed-off-by:
-
Antti Palosaari authored
Remove HID and polling via firmware API. Implement direct access to remote codes via memory read and write. HID and polling via firmware api never worked 100% well and there was also some limitations which tied used remote and device together. After that it is possible to use upcoming kernel remote controller core. Signed-off-by:
-
Antti Palosaari authored
Detect TerraTec Cinergy T Stick Dual RC remote config using device USB ID instead of device EEPROM hash. It was found that there is devices with slightly different EEPROM content... Signed-off-by:
-
Antti Palosaari authored
Thanks to the TerraTec! Signed-off-by:
-
Antti Palosaari authored
Add USB ID [0ccd:0099] for TerraTec Cinergy T Stick Dual RC. Device is based for AF9015 + AF9013 + 2 x MxL5007T chips. Thanks to the TerraTec! Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Commit 490ade7e3f4474f626a8f5d778ead4e599b94fbc merge conflict fix leads situation where last nine device definitions were overridden mistakenly. Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Mats Randgaard authored
Signed-off-by:
Mats Randgaard <mats.randgaard@tandberg.com> Signed-off-by:
Hans Verkuil <hans.verkuil@tandberg.com> Signed-off-by:
-
Mats Randgaard authored
Signed-off-by:
-
Mats Randgaard authored
Signed-off-by:
-
Mauro Carvalho Chehab authored
Teletext interface is provided via VBI interface for a long time. There's no need nor is there any known program using those old /dev/vtx nodes. Signed-off-by: -
Hans Verkuil authored
Remove all references to /dev/vtx in the documentation, except for some historical comments in dev-teletext.xml. Documentation/devices.txt is not updated, this will go through Alan Cox who maintains this file. Signed-off-by:
-
Hans Verkuil authored
Remove the vtx (aka videotext aka teletext) API from the v4l2 core. This API was scheduled for removal in kernel 2.6.35. The vtx device nodes have been superseded by vbi device nodes for many years. No applications exist that use the vtx support. Of the two i2c drivers that actually support this API the saa5249 has been impossible to use for a year now and no known hardware that supports this device exists. The saa5246a is theoretically supported by the old mxb boards, but it never actually worked. In summary: there is no hardware that can use this API and there are no applications actually implementing this API. The vtx support still reserves minors 192-223 and we would really like to reuse those for upcoming new functionality. In the unlikely event that new hardware appears that wants to use the functionality provided by the vtx API, then that functionality should be build around the sliced VBI API instead. Signed-off-by:
-
Hans Verkuil authored
These old i2c teletext drivers are not supported by any hardware and cannot be tested anymore. Note that while the mxb board seemingly used the saa5246a driver, in reality this teletext driver never worked. These drivers are removed as part of the vtx feature removal, originally scheduled for 2.6.35. Signed-off-by:
-
