An error occurred fetching the project authors.
- 20 Jul, 2008 5 commits
-
-
Hans Verkuil authored
Signed-off-by:
Hans Verkuil <hverkuil@xs4all.nl> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Based on an initial conversion patch from Douglas Landgraf. Signed-off-by:
Douglas Schilling Landgraf <dougsland@gmail.com> Signed-off-by:
-
- 14 May, 2008 1 commit
-
-
Hans Verkuil authored
Fix conflict with cx18 driver. Signed-off-by:
-
- 29 Apr, 2008 2 commits
-
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
- 24 Apr, 2008 4 commits
-
-
Alan Cox authored
Frank Bennett reported that ivtv was causing skype to crash. With help from one of their developers he showed it was a kernel problem. VIDIOCGCAP copies a name into a fixed length buffer - ivtv uses names that are too long and does not truncate them so corrupts a few bytes of the app data area. Possibly the names also want trimming but for now this should fix the corruption case. Signed-off-by:
Alan Cox <alan@redhat.com> Signed-off-by:
-
Mauro Carvalho Chehab authored
Signed-off-by: -
Hans Verkuil authored
CROPCAP suggests that video capture supports cropping, but this is not the case. Signed-off-by:
-
Ian Armstrong authored
The existing yuv code limits output to the display area occupied by the framebuffer. This patch allows the yuv output to be 'detached' via V4L2_FBUF_FLAG_OVERLAY. By default, the yuv output window will be restricted to the framebuffer dimensions and the output position is relative to the top left corner of the framebuffer. This matches the behaviour of previous versions. If V4L2_FBUF_FLAG_OVERLAY is cleared, the yuv output will no longer be linked to the framebuffer. The maximum dimensions are either 720x576 or 720x480 depending on the current broadcast standard, with the output position relative to the top left corner of the display. The framebuffer itself can be resized, moved and panned without affecting the yuv output. Signed-off-by:
Ian Armstrong <ian@iarmst.demon.co.uk> Signed-off-by:
-
- 25 Jan, 2008 4 commits
-
-
Richard Knutsson authored
Fix "warning: Using plain integer as NULL pointer". Convert 'x < y ? x : y' to use min() instead. Signed-off-by:
Richard Knutsson <ricknu-0@student.ltu.se> Signed-off-by:
-
Richard Knutsson authored
Remove the shadowing 'struct v4l2_chip_ident *chip', since it already exists and makes the if-statement useless. Signed-off-by:
-
Ian Armstrong authored
The driver was incorrectly reporting that it supported YUV 4:2:2 output, when it is actually YUV 4:2:0. Though I believe the hardware can be pushed to 4:2:2, we don't currently support that. Signed-off-by:
-
Ian Armstrong authored
Previously, all yuv data written to /dev/video48 had only basic support with no double buffering to avoid display tearing. With this patch, yuv frames written to video48 are now handled by the existing IVTV_IOC_DMA_FRAME framework. As such, the frames are hardware buffered to avoid tearing, and honour scaling mode & field order options. Unlike the proprietary IVTV_IOC_DMA_FRAME ioctl, all parameters are controlled by the V4L2 API. Due to mpeg & yuv output restrictions being different, their V4L2 output controls have been separated. To control the yuv output, the V4L2 calls must be done via video48. If the ivtvfb module is loaded, there will be one side effect to this merge. The yuv output window will be constrained to the visible framebuffer area. In the event that a virtual framebuffer size is being used, the limit to the output size will be the virtual dimensions, but only the portion that falls within the currently visible area of the framebuffer will be shown. Like the IVTV_IOC_DMA_FRAME ioctl, the supplied frames must be padded to 720 pixels wide. However the height must only be padded up the nearest multiple of 32. This would mean an image of 102 lines must be padded to 128. As long as the true source image size is given, the padding will not be visible in the final output. Signed-off-by:
-
- 22 Oct, 2007 1 commit
-
-
Hans Verkuil authored
Resizing an MPEG 1 stream would cut off the right half of the image due to a missing divide by 2 in VIDIOC_S_FMT. Also did some minor cleanup in this part of the code. Signed-off-by:
-
- 10 Oct, 2007 14 commits
-
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
ivtv: set correct pixel format and alpha properties in VIDIOC_G_FBUF Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Changing the VBI format requires a CX2341X_ENC_INITIALIZE_INPUT firmware call. This can only be done if no capture is in progress. So return -EBUSY if the encoder is busy. Signed-off-by:
-
Hans Verkuil authored
- Always clear when stopping the decoder - Clear if the filehandle that is being close was used for UDMA_YUV output. Signed-off-by:
-
Hans Verkuil authored
Add VIDIOC_OVERLAY to enable/disable the OSD. Also add the OSD state to the log status report. Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
Serialization is now done on the open/close/ioctl level and also when the read/write/poll start an encoder/decoder stream. Signed-off-by:
-
Hans Verkuil authored
- add FILE debug flag for open/close/read/write/poll. - show cmd for encoder/decoder command ioctl. Signed-off-by:
-
Hans Verkuil authored
The CX2341X_ENC_INITIALIZE_INPUT firmware call requires careful handling, otherwise the computer can freeze or the top-third of the screen can start flickering. This patch ensures that CX2341X_ENC_INITIALIZE_INPUT is called at the right time and in the right way. In addition the stop capture handling was improved so that the last pending DMA transfer is also processed. Otherwise this would be the first data that arrived when a new capture was started which is not what you want. Signed-off-by:
-
Hans Verkuil authored
Add support to optionally reset the IR and/or the video digitizer. Signed-off-by:
-
Hans Verkuil authored
Signed-off-by:
-
- 14 Sep, 2007 1 commit
-
-
Hans Verkuil authored
Due to a documentation bug (the type mask is 3 bits long, not 2) the wrong frame types were filled in: the B and P frame types were swapped. This bug also hid a second bug: when a capture is stopped a last entry is written into the pgm index buffer with internal type 0, denoting the end of the program. This entry wasn't ignored, instead it was accidentally returned to the caller as a P frame. Signed-off-by:
-
- 20 Aug, 2007 2 commits
-
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
ivtv: fix VIDIOC_S_FBUF support: new OSD values where never actually set. The values set with VIDIOC_S_FBUF were not actually used until the next VIDIOC_S_FMT. Fixed. Signed-off-by:
-
- 30 Jul, 2007 1 commit
-
-
Hans Verkuil authored
Pausing a decoder followed by a Play command would do nothing. Fixed. Pausing a decoder running at non-standard speed following by a Continue would reset the speed to 100%. Fixed. Signed-off-by:
-
- 18 Jul, 2007 1 commit
-
-
Hans Verkuil authored
Signed-off-by:
-
- 08 Jun, 2007 2 commits
-
-
Hans Verkuil authored
Signed-off-by:
-
Hans Verkuil authored
The VIDIOC_CROPCAP ioctl was missing in ivtv. The handling of output video cropping was wrong. This has now been fixed. Signed-off-by:
-
- 22 May, 2007 1 commit
-
-
Hans Verkuil authored
Reverted the change to struct v4l2_pix_format. I completely missed that this struct was used by existing ioctls so that changing it broke the ABI. I will have to think of another way of setting the top/left coordinates but for now this change is reverted to preserve compatibility. Signed-off-by:
-
- 27 Apr, 2007 1 commit
-
-
Hans Verkuil authored
Signed-off-by:
-
