public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Mike Booth <mike_booth76@iprimus.com.au>
Cc: linux-media@vger.kernel.org
Subject: Re: v4l-utils-0.8.3 and KVDR
Date: Sun, 20 Feb 2011 09:14:37 +0100	[thread overview]
Message-ID: <4D60CD6D.6000607@redhat.com> (raw)
In-Reply-To: <e05367$6mkr9m@smtp06.syd.iprimus.net.au>

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


  reply	other threads:[~2011-02-20  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-19 23:48 v4l-utils-0.8.3 and KVDR Mike Booth
2011-02-20  8:14 ` Hans de Goede [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-22  9:03 Mike Booth
2011-02-22 10:46 ` Hans de Goede

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D60CD6D.6000607@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mike_booth76@iprimus.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox