- 21 Mar, 2011 40 commits
-
-
Igor M. Liplianin authored
An Altera FPGA CI module for NetUP Dual DVB-T/C RF CI card. Signed-off-by:
Igor M. Liplianin <liplianin@netup.ru> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
Igor M. Liplianin authored
It uses STAPL files and programs Altera FPGA through JTAG. Interface to JTAG must be provided from main device module, for example through cx23885 GPIO. Signed-off-by:
-
Peter Huewe authored
This patch fixes the warning "Using plain integer as NULL pointer", generated by sparse, by replacing the offending 0s with NULL. Signed-off-by:
Peter Huewe <peterhuewe@gmx.de> Reviewed-by:
Devin Heitmueller <dheitmueller@hauppauge.com> Signed-off-by:
-
Andrew Chew authored
This soc_camera driver is for Omnivision's OV9740 sensor. This initial submission provides support for YUV422 output at 1280x720 (720p), which is the sensor's native resolution. 640x480 (VGA) is also supported, with cropping and scaling performed by the sensor's ISP. This driver is heavily based off of the existing OV9640 driver. Signed-off-by:
Andrew Chew <achew@nvidia.com> Signed-off-by:
Guennadi Liakhovetski <g.liakhovetski@gmx.de> Signed-off-by:
-
Guennadi Liakhovetski authored
Use the correct scales to calculate cropping offsets. Signed-off-by:
-
Guennadi Liakhovetski authored
Now that soc-camera supports videobuf API v1 and v2, camera-host drivers can be converted to videobuf2 individually. This patch converts the mx3_camera driver. Signed-off-by:
-
Guennadi Liakhovetski authored
Convert the sh_mobile_ceu_camera driver to the videobuf2 API. Signed-off-by:
-
Guennadi Liakhovetski authored
Add two helper inline functions to retrieve soc-camera device context from videobuf and videobuf2 queue pointers. Signed-off-by:
-
Guennadi Liakhovetski authored
Extend soc-camera core to also support the videobuf2 API. Signed-off-by:
-
Guennadi Liakhovetski authored
videobuf2-memops and videobuf2-core can be compiled as modules, in which case 3 more symbols from videobuf2-memops.c have to be exported. Signed-off-by:
-
Guennadi Liakhovetski authored
Signed-off-by:
-
Alberto Panizzo authored
If the camera was set to output formats like RGB565 YUYV or SBGGR10, the resulting image was scrambled due to erroneous interpretations of horizontal parameter's units. This patch in fourcc_to_ipu_pix, eliminate also the pixel formats mappings that, first are not used within mainline code and second, standing at the datasheets, they will not work properly: The IPU internal bus support only the following data formatting (44.1.1.3 Data Flows and Formats): 1 YUV 4:4:4 or RGB-8 bits per color component 2 YUV 4:4:4 or RGB-10 bits per color component 3 Generic data (from sensor to the system memory only) And format conversions are done: - from memory: unpacking from other formats to IPU supported ones - to memory: packing in the inverse order. So, assigning a packing/unpacking strategy to the IPU for those formats will produce a packing to memory and not the inverse. Signed-off-by:
Alberto Panizzo <maramaopercheseimorto@gmail.com> Signed-off-by:
-
Anatolij Gustschin authored
The 'pix->width' field may be updated in mx3_camera_set_fmt() to fulfill the IPU stride line alignment requirements. If this update takes place, the 'fmt.pix.sizeimage' field in the struct v4l2_format stucture returned by VIDIOC_S_FMT is wrong. We need to update the 'pix->sizeimage' field in the mx3_camera_set_fmt() function to fix this issue. Signed-off-by:
Anatolij Gustschin <agust@denx.de> Signed-off-by:
-
Mathias Krause authored
Even though clk_put() is a no-op on most architectures it is not for some ARM implementations. To not fail on those, release the clock timer before freeing the surrounding structure. This bug was spotted by the semantic patch tool coccinelle using the script found at scripts/coccinelle/free/kfree.cocci. More information about semantic patching is available at http://coccinelle.lip6.fr/Signed-off-by:
Mathias Krause <minipli@googlemail.com> Signed-off-by:
-
Alberto Panizzo authored
Add a function to calculate the number of samples on the media-bus, required to retrieve one pixel of a certain format. Signed-off-by:
-
Anatolij Gustschin authored
Some camera systems have strong requirement for capturing an exact number of frames after starting the stream and do not tolerate losing captured frames. By starting the stream after the videobuf has queued the buffers, we ensure that no frame will be lost. Signed-off-by:
-
Qing Xu authored
add vidioc_enum_framesizes implementation, follow default_g_parm() and g_mbus_fmt() method Signed-off-by:
Qing Xu <qingx@marvell.com> Signed-off-by:
-
Qing Xu authored
Add enum_mbus_fsizes V4L2 subdevice video operation. Signed-off-by:
-
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:
-
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:
-
