public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "B. Bogart" <ben@ekran.org>
Cc: video4linux-list@redhat.com, gem-dev@iem.at
Subject: Re: Re: V4l2 :: Debugging an issue with cx8800 card.
Date: Fri, 12 Sep 2008 12:19:33 -0700	[thread overview]
Message-ID: <48CAC0C5.905@ekran.org> (raw)
In-Reply-To: <1220568687.2736.12.camel@morgan.walls.org>

I have made progress.

I've managed to get my card working in Gem with some minor changes to
the code. I'm not sure what this code does though, so I'm not sure what
the longer term effect will be.

I'm sending this to the v4l list as you all are the best to advice on a
proper solution to this issue.

I've attached the original, and the hacked version.

Basically the hacked version ignores all errors when running the
following command:

xioctl (m_tvfd, VIDIOC_DQBUF, &buf)

What does this command actually do? Why are there two instances in the
capture function?

I can use the card at 640x480.

The result is the frame-rate is horrid compared to mplayer (which I
suppose makes sense based on those removed error reports) and also using
the V4L1 w/ a bt8x8 card.

Does this change give a hint as to what is causing the problem?

What is the proper way to fix the issue, rather than commenting out
error codes?

Thanks all,
B. Bogart

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  parent reply	other threads:[~2008-09-12 19:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04 22:14 V4l2 :: Debugging an issue with cx8800 card B. Bogart
2008-09-04 22:51 ` Andy Walls
2008-09-04 23:16   ` B. Bogart
2008-09-05  6:01     ` Jean-Francois Moine
2008-09-05 15:29       ` B. Bogart
2008-09-12 19:19   ` B. Bogart [this message]
2008-09-12 19:22   ` B. Bogart
2008-09-12  0:44 ` Broken gem support for UYVY V4L capture? WAS " B. Bogart
2008-09-12  0:46 ` Sorry! B. Bogart

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=48CAC0C5.905@ekran.org \
    --to=ben@ekran.org \
    --cc=gem-dev@iem.at \
    --cc=video4linux-list@redhat.com \
    /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