- 21 Mar, 2011 40 commits
-
-
Hans Verkuil authored
Reported by, and based on a patch from, Martin Dauskardt. The AUDIO_AC3_BITRATE control is still missing from this list, but such optional controls are a bit hard to handle. This will be fixed automatically when we switch to the control framework. Signed-off-by:
Hans Verkuil <hverkuil@xs4all.nl> Reported-by:
Martin Dauskardt <martin.dauskardt@gmx.de> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
Hans Verkuil authored
drivers/ieee1394/ has been removed in Linux 2.6.37. The corresponding backend code in firedtv is no longer built in now and can be deleted. Firedtv continues to work with drivers/firewire/. Also, fix a Kconfig menu comment: Removal of CONFIG_IEEE1394 made the "Supported FireWire (IEEE 1394) Adapters" comment disappear; bring it back with corrected dependency. Signed-off-by:
Stefan Richter <stefanr@s5r6.in-berlin.de> Signed-off-by:
-
Hans Verkuil authored
Some ioctl's were defined wrong on 2.6.2 and 2.6.6, using the wrong type of R/W arguments. They were fixed, but the old ioctl names are still there, maintained to avoid breaking binary compatibility: There's no sense on preserving those forever, as it is very doubtful that someone would try to use a such old binary with a modern kernel. Removing them will allow us to remove some magic done at the V4L ioctl handler. Note that any application compiled with a videodev2.h from 2.6.7 or later will be using the correct ioctls. Signed-off-by:
-
Hans Verkuil authored
The dabusb driver was conceived as an experimental driver for a test device. The driver never supported any shipped product, and, while there were some updates for it in 2003, for an ancient product, those changes were never submitted upstream. Also, there's no DocBook for its API, nor any upstream discussion. So it was decided to remove it in 2.6.39. Future support for a DAB API should be discussed on the linux-media list first. Signed-off-by:
-
Hans Verkuil authored
This driver is for obsolete hardware that the old maintainer didn't care (or not have the hardware anymore), and that no other developer could find any hardware to buy. The V4L1 API is no longer supported, and since nobody stepped in to convert them to V4L2 the decision was made to remove them. Signed-off-by:
-
Hans de Goede authored
With the new gspca v4l2 vicam driver, there is no more reason to keep the old v4l1 usbvideo vicam driver around, and since that is the last usbvideo framework using driver, the old usbvideo framework itself can go too. Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Signed-off-by:
-
Hans de Goede authored
Having a framerate divisor of 3 is not really necesarry and leads to various troubles (frames going missing, compression issues) when allowed. Signed-off-by:
-
Hans de Goede authored
This is a complete rewrite of the old v4l1 vicam subdriver, featuring multiple resolutions, gain + exposure control and still has less code. Oh and it is a v4l2 driver rather then v4l1 ofcourse :) Many thanks to Devin Heitmueller <dheitmueller@kernellabs.com> for donating his 3com homeconnect to me, which made this rewrite possible. Signed-off-by:
-
Hans de Goede authored
Signed-off-by:
-
Hans de Goede authored
In good lighting conditions (lots of details visible) the current buffers are sometimes too small. Signed-off-by:
-
Hans de Goede authored
This fixes the led not working on this camera Signed-off-by:
-
Hans de Goede authored
Tested with a camera with usb-id: 0c45:62bb Also enable dmi based flopped laptop detection for the 0c45:627b ov7660 model. Some of the MSI laptops with upside down camera have this one instead of the 0c45:624f. Signed-off-by:
-
Hans de Goede authored
Tested with a camera with usb-id: 0c45:62bb Signed-off-by:
-
Stefan Ringel authored
relabeling any registers Signed-off-by:
Stefan Ringel <stefan.ringel@arcor.de> Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
Jean-François Moine <moinejf@free.fr> 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:
-
Jean-François Moine authored
Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Jean-François Moine authored
This avoids to define the webcam model. Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Jean-François Moine authored
The gain/expo adjustment was too long. Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Jean-François Moine authored
During image capture, the filling rate of the isoc packets is computed. It is then used by a work queue to update the current JPEG quality. Tested-by:
Franck Bourdonnec <fbourdonnec@chez.com> Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Jean-François Moine authored
A marker 'ff ff 00 c4 c4 96' indicates an end of frame. It is 62 bytes long and may be splitted on 2 packets. It contains a flag 'USB full' which indicates that the frame is truncated. Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Pawel Osciak authored
This feature will probably be moved to libv4l2. Signed-off-by:
Pawel Osciak <pawel@osciak.com> Signed-off-by:
-
Hans Verkuil authored
v4l2-ctl and qv4l2 enumerate controls using V4L2_CTRL_FLAG_NEXT_CTRL, falling back to the old method if the flag isn't supported. The v4l2_subdev_queryctrl function will currently handle that flag, but for the controls of the subdev only. This isn't right, it should refuse this flag, otherwise v4l2-ctl will only see the controls of the first subdev. Signed-off-by:
-
Mauro Carvalho Chehab authored
Subdev controls return codes are evil, as they return -EINVAL to mean both unsupported and invalid arguments. Due to that, we need to use a trick to identify what controls are supported by a subdev. Signed-off-by: -
Mauro Carvalho Chehab authored
On some cases, driver returns 1. This should be OK, but qv4l2 is too strict about return values. Signed-off-by: -
Mauro Carvalho Chehab authored
Having the device detection happening at reset is bad, as every time, it will produce a message like: tvp5150 2-005c: tvp5150am1 detected. This only polutes the log and for an accidental kernel hacker, it looks like a real problem. So, move those printk's to happen during device probe. Signed-off-by: -
Mauro Carvalho Chehab authored
A few places used T_DIGITAL_TV internally. Remove the usage of this obsolete mode mask. Signed-off-by: -
Mauro Carvalho Chehab authored
It makes no sense that tuner_lookup would touch at the standby state. Remove it. Thanks-to: Hans Verkuil <hverkuil@xs4all.nl> Signed-off-by: -
Mauro Carvalho Chehab authored
Group a few functions together and add/fix comments for each block of the driver. This is just a cleanup patch meant to improve driver readability. No functional changes in this patch. Signed-off-by: -
Mauro Carvalho Chehab authored
This driver is complex, and used by everyone. Better to have it properly documented. No functional changes are done in this patch. Signed-off-by: -
Mauro Carvalho Chehab authored
tuner-core has no business to do with digital TV. So, don't use T_DIGITAL_TV on it, as it has no code to distinguish between them, and nobody fills T_DIGITAL_TV right. Signed-off-by:
-
