All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: Jim Paris <jim@jtan.com>
Cc: video4linux-list@redhat.com
Subject: Re: [PATCH 0 of 4] ov534 patches
Date: Thu, 04 Dec 2008 09:14:02 +0100	[thread overview]
Message-ID: <1228378442.1733.17.camel@localhost> (raw)
In-Reply-To: <patchbomb.1228337219@hypnosis.jim>

On Wed, 2008-12-03 at 15:46 -0500, Jim Paris wrote:
> Hi,

Hi Jim,

> Here are some ov534 patches I've been working on.
> 
> ov534: don't check status twice
> ov534: initialization cleanup
> ov534: Fix frame size so we don't miss the last pixel
> ov534: frame transfer improvements

Thank you for these patchs. Some changes were already done in my
repository. I merged them and pushed. May you check if everything is
correct?

Also, I moved the last fid and pts to the sd structure. This allows many
webcams to work simultaneously. I was wondering about the reset of these
variables: last_fid is never reset and last_pts is reset on
UVC_STREAM_EOF. Shouldn't they also be reset on streaming start?

Cheers.

-- 
Ken ar c'hentañ |             ** Breizh ha Linux atav! **
Jef             |               http://moinejf.free.fr/


--
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-12-04  8:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 20:46 [PATCH 0 of 4] ov534 patches Jim Paris
2008-12-03 20:47 ` [PATCH 1 of 4] ov534: don't check status twice Jim Paris
2008-12-03 20:47 ` [PATCH 2 of 4] ov534: initialization cleanup Jim Paris
2008-12-03 20:47 ` [PATCH 3 of 4] ov534: Fix frame size so we don't miss the last pixel Jim Paris
2008-12-03 20:47 ` [PATCH 4 of 4] ov534: frame transfer improvements Jim Paris
2008-12-04  8:14 ` Jean-Francois Moine [this message]
2008-12-04 12:05   ` [PATCH 0 of 4] ov534 patches Antonio Ospite
2008-12-09 21:12     ` Jim Paris
2008-12-04 17:15   ` Jim Paris
2008-12-06 17:42     ` Antonio Ospite
2008-12-09 21:21       ` Jim Paris
2008-12-10 16:07         ` Antonio Ospite

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=1228378442.1733.17.camel@localhost \
    --to=moinejf@free.fr \
    --cc=jim@jtan.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.