Re: HD-PVR fails consistently on Linux, works on Windows

2012-10-13 Thread Keith Pyle
On 10/13/12 14:17, David Röthlisberger wrote: On Wed, 26 Sep 2012 21:42:32 -0500 Keith Pyle wrote: I recently purchased a Hauppauge HD-PVR (the 1212 version, label on bottom 49001LF, Rev F2). I have consistent capture failures on Linux where data from the device simply stops, generally within

Re: [RFC] Processing context in the V4L2 subdev and V4L2 controls API ?

2012-10-13 Thread Sylwester Nawrocki
Hi Hans, On 09/21/2012 02:26 PM, Hans Verkuil wrote: > On Tue September 18 2012 17:06:54 Sylwester Nawrocki wrote: >> Hi All, >> >> I'm trying to fulfil following requirements with V4L2 API that are specific >> to most of Samsung camera sensors with embedded SoC ISP and also for local >> SoC camer

cron job: media_tree daily build: WARNINGS

2012-10-13 Thread Hans Verkuil
This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date:Sat Oct 13 19:00:23 CEST 2012 git hash:d92462401dde1effa04a51d0a15000e6246d2a43 gcc version: i686-linux-gcc (GC

Re: HD-PVR fails consistently on Linux, works on Windows

2012-10-13 Thread David Röthlisberger
On Wed, 26 Sep 2012 21:42:32 -0500 Keith Pyle wrote: > I recently purchased a Hauppauge HD-PVR (the 1212 version, label on > bottom 49001LF, Rev F2). I have consistent capture failures on Linux > where data from the device simply stops, generally within a few minutes > of starting a capture. >

Re: [RFC/PATCH] v4l: Add V4L2_CID_FLASH_HW_STROBE_MODE control

2012-10-13 Thread Sylwester Nawrocki
Hi Sakari, My apologies for reviving so old thread ;) It unfortunately didn't end with any conclusion but we need a functionality similar to the provided by the $subject patch for multiple different {camera sensor + ISP} devices. On 12/10/2011 02:55 PM, Sylwester Nawrocki wrote: > Hi Sakari, >

Re: HD-PVR fails consistently on Linux, works on Windows

2012-10-13 Thread Jonathan
On Wed, 26 Sep 2012 21:42:32 -0500 Keith Pyle wrote: > I recently purchased a Hauppauge HD-PVR (the 1212 version, label on > bottom 49001LF, Rev F2). I have consistent capture failures on Linux > where data from the device simply stops, generally within a few minutes > of starting a capture.

[PATCH 1/1] [media] s5p-fimc: Fix potential NULL pointer dereference

2012-10-13 Thread Sachin Kamat
'fimc' was being dereferenced before the NULL check. Moved it to after the check. Signed-off-by: Sachin Kamat --- drivers/media/platform/s5p-fimc/fimc-mdevice.c |6 -- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/media/platform/s5p-fimc/fimc-mdevice.c b/drivers

[PATCH 1/1] [media] s5p-mfc: Fix compilation warning

2012-10-13 Thread Sachin Kamat
Added missing const qualifier. Without this patch compiler gives the following warning: drivers/media/platform/s5p-mfc/s5p_mfc_enc.c:1576:2: warning: initialization from incompatible pointer type [enabled by default] drivers/media/platform/s5p-mfc/s5p_mfc_enc.c:1576:2: warning: (near initializatio

Re: [PATCH v4 2/3] omap3isp: Add PHY routing configuration

2012-10-13 Thread Sakari Ailus
Hi Laurent, On Thu, Oct 11, 2012 at 01:48:12AM +0200, Laurent Pinchart wrote: > On Wednesday 10 October 2012 23:01:41 Sakari Ailus wrote: > > Add PHY routing configuration for both 3430 and 3630. Also add register bit > > definitions of CSIRXFE and CAMERA_PHY_CTRL registers on OMAP 3430 and 3630,

Re: [PATCH v4 3/3] omap3isp: Configure CSI-2 phy based on platform data

2012-10-13 Thread Sakari Ailus
On Thu, Oct 11, 2012 at 01:34:30AM +0200, Laurent Pinchart wrote: > On Wednesday 10 October 2012 23:01:42 Sakari Ailus wrote: > > Configure CSI-2 phy based on platform data in the ISP driver. For that, the > > new V4L2_CID_IMAGE_SOURCE_PIXEL_RATE control is used. Previously the same > > was configu

Re: [PATCH 0/3] Miscellaneous OMAP3 ISP fixes

2012-10-13 Thread Sakari Ailus
Laurent Pinchart wrote: Hi everybody, The subject line says it all, there's not much to add. I'll push those patches for v3.8. Laurent Pinchart (3): omap3isp: Remove unneeded module memory address definitions omap3isp: video: Fix warning caused by bad vidioc_s_crop prototype omap3isp:

Re: [PATCH v3] omap3isp: Use monotonic timestamps for statistics buffers

2012-10-13 Thread Sakari Ailus
Hi Laurent, Thanks for the update! Laurent Pinchart wrote: V4L2 buffers use the monotonic clock, while statistics buffers use wall time. This makes it difficult to correlate video frames and statistics. Switch statistics buffers to the monotonic clock to fix this. Reported-by: Antoine Reversa