public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
* v4l-utils-0.8.3 and KVDR
@ 2011-02-19 23:48 Mike Booth
  2011-02-20  8:14 ` Hans de Goede
  0 siblings, 1 reply; 4+ messages in thread
From: Mike Booth @ 2011-02-19 23:48 UTC (permalink / raw)
  To: linux-media

My understanding of the "wrappers"contained in this library is that v4l 
applications should work with kernels from 2.6.36 onwards if the compat.so is 
preloaded.

I use KVDR for watching and controlling VDR on my TV.

Xine and Xineliboutput or not options as they don't provide TV out and TV out 
fronm the video card is also not an option because of where things are in the 
house.

KVDR fails with 


Xv-VIDIOCGCAP: Invalid argument
Xv-VIDIOCGMBUF: Invalid argument

works perfectly fine on linux-2.6.35


Anyone have any ideas


Mike


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: v4l-utils-0.8.3 and KVDR
  2011-02-19 23:48 Mike Booth
@ 2011-02-20  8:14 ` Hans de Goede
  0 siblings, 0 replies; 4+ messages in thread
From: Hans de Goede @ 2011-02-20  8:14 UTC (permalink / raw)
  To: Mike Booth; +Cc: linux-media

Hi,

On 02/20/2011 12:48 AM, Mike Booth wrote:
> My understanding of the "wrappers"contained in this library is that v4l
> applications should work with kernels from 2.6.36 onwards if the compat.so is
> preloaded.
>
> I use KVDR for watching and controlling VDR on my TV.
>
> Xine and Xineliboutput or not options as they don't provide TV out and TV out
> fronm the video card is also not an option because of where things are in the
> house.
>
> KVDR fails with
>
>
> Xv-VIDIOCGCAP: Invalid argument
> Xv-VIDIOCGMBUF: Invalid argument
>
> works perfectly fine on linux-2.6.35
>
>
> Anyone have any ideas

First of all make sure you load kdvr with the appropriote LD_PRELOAD, ie:
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so kvdr

If that does not help, do the following before launching kvdr:
export LIBV4L1_LOG_FILENAME=/tmp/log

So the total sequence of commands becomes:
export LIBV4L1_LOG_FILENAME=/tmp/log
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so kvdr

Then do what ever you want to do and fails, and send another mail
with /tmp/log attached.

Regards,

Hans


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: v4l-utils-0.8.3 and KVDR
@ 2011-02-22  9:03 Mike Booth
  2011-02-22 10:46 ` Hans de Goede
  0 siblings, 1 reply; 4+ messages in thread
From: Mike Booth @ 2011-02-22  9:03 UTC (permalink / raw)
  To: linux-media

KVDR has a number of different parameters including

-x                        force xv-mode on startup and disable overlay-mod

-d                        dont switch modeline during xv
 with kernel 2.6.35 I run KVDR with -x as I have an NVIDIA graphics. Running 
on 2.6.38 KVDR -x doesn't produce any log. The display appears and immediately 
disappears although there is a process running.

With KVDR -d I get a display window but no picture but the attached log is 
produced. 

I hope this helps


Mike

libv4l2: open: 4
request == VIDIOC_G_FMT
  pixelformat: BGR3 384x288
  field: 0 bytesperline: 0 imagesize331776
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 0, description: RGB-8 (3-3-2)
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: RGB1 48x32
  field: 3 bytesperline: 48 imagesize1536
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: RGB1 768x288
  field: 3 bytesperline: 768 imagesize221184
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 1, description: RGB-16 (5/B-6/G-5/R)
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: RGBP 48x32
  field: 3 bytesperline: 768 imagesize24576
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: RGBP 768x288
  field: 3 bytesperline: 1536 imagesize442368
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 2, description: RGB-24 (B-G-R)
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: BGR3 48x32
  field: 3 bytesperline: 1536 imagesize49152
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: BGR3 768x288
  field: 3 bytesperline: 2304 imagesize663552
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 3, description: RGB-32 (B-G-R)
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: BGR4 48x32
  field: 3 bytesperline: 2304 imagesize73728
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: BGR4 768x288
  field: 3 bytesperline: 3072 imagesize884736
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 4, description: RGB-32 (R-G-B)
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: RGB4 48x32
  field: 3 bytesperline: 3072 imagesize98304
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: RGB4 768x288
  field: 3 bytesperline: 3072 imagesize884736
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 5, description: Greyscale-8
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: GREY 48x32
  field: 3 bytesperline: 3072 imagesize98304
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: GREY 768x288
  field: 3 bytesperline: 3072 imagesize884736
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 6, description: YUV 4:2:2 planar (Y-Cb-Cr)
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: 422P 48x32
  field: 3 bytesperline: 3072 imagesize98304
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: 422P 768x288
  field: 3 bytesperline: 3072 imagesize884736
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 7, description: YVU 4:2:0 planar (Y-Cb-Cr)
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: YV12 48x32
  field: 3 bytesperline: 3072 imagesize98304
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: YV12 768x288
  field: 3 bytesperline: 3072 imagesize884736
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 8, description: YUV 4:2:0 planar (Y-Cb-Cr)
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: YU12 48x32
  field: 3 bytesperline: 3072 imagesize98304
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: YU12 768x288
  field: 3 bytesperline: 3072 imagesize884736
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 9, description: YUV 4:2:2 (U-Y-V-Y)
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: UYVY 48x32
  field: 3 bytesperline: 3072 imagesize98304
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: UYVY 768x288
  field: 3 bytesperline: 3072 imagesize884736
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 10, description: RGB3
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: RGB3 48x32
  field: 3 bytesperline: 144 imagesize4608
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_TRY_FMT
  pixelformat: RGB3 768x288
  field: 3 bytesperline: 2304 imagesize663552
  colorspace: 0, priv: 0
result == 0
request == VIDIOC_ENUM_FMT
  index: 11, description: 
result == -1 (Invalid argument)
request == VIDIOC_ENUMINPUT
result == 0
request == VIDIOC_ENUMSTD
result == 0
libv4l1: open: 4
request == VIDIOC_QUERYCAP
result == 0
request == VIDIOC_G_FBUF
result == 0
request == VIDIOC_S_FBUF
result == 0
libv4l2: close: 4
libv4l1: close: 4


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: v4l-utils-0.8.3 and KVDR
  2011-02-22  9:03 v4l-utils-0.8.3 and KVDR Mike Booth
@ 2011-02-22 10:46 ` Hans de Goede
  0 siblings, 0 replies; 4+ messages in thread
From: Hans de Goede @ 2011-02-22 10:46 UTC (permalink / raw)
  To: Mike Booth; +Cc: linux-media

Hi,

On 02/22/2011 10:03 AM, Mike Booth wrote:
> KVDR has a number of different parameters including
>
> -x                        force xv-mode on startup and disable overlay-mod
>
> -d                        dont switch modeline during xv
>   with kernel 2.6.35 I run KVDR with -x as I have an NVIDIA graphics. Running
> on 2.6.38 KVDR -x doesn't produce any log. The display appears and immediately
> disappears although there is a process running.
>

So with 2.6.35 and v4l-utils-0.8.3 things work ? Then this is not a libv4l
problem, as libv4l will no longer use the kernels v4l1 compat independent of
the kernels version.

Also in the log I see nothing indicating this is a v4l1 app (I'm not familiar
with kvdr), so I think something else may have changed in the new
kernel causing your issue.

Regards,

Hans

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-02-22 10:46 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-02-22  9:03 v4l-utils-0.8.3 and KVDR Mike Booth
2011-02-22 10:46 ` Hans de Goede
  -- strict thread matches above, loose matches on Subject: below --
2011-02-19 23:48 Mike Booth
2011-02-20  8:14 ` Hans de Goede

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox