public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: Video 4 Linux <video4linux-list@redhat.com>
Subject: Re: [PATCH] Add support for OmniVision OV534 based USB cameras.
Date: Thu, 13 Nov 2008 12:33:58 +0100	[thread overview]
Message-ID: <1226576038.2040.42.camel@localhost> (raw)
In-Reply-To: <20081112191736.bcbc1e37.ospite@studenti.unina.it>

On Wed, 2008-11-12 at 19:17 +0100, Antonio Ospite wrote:
> Well, with my hacks to gspca.c the ov534 driver has become really
> trivial. The source has shrunk from 33K to 13K. But these hacks could
> not be accepted though :) But, yes, the opinion on gspca is positive.

Hello Antonio,

Thank you for your opinion.

I looked again at your subdriver, and it seems good to me. So forget
about mine which is too buggy.

About your hacks to gspca, there are good and bad ideas. The good idea
is to have the bulk_nurbs parameter. The bad idea is to force it to one
when no set. To preserve the compatibility, the bulk_nurbs may be set to
some value for webcams which accept permanent bulk read, the submit
being done by gspca. For the other webcams, as those in finepix, a null
bulk_nurbs will indicate that the bulk read requests are done by the
subdriver. Is it OK for you?

Also, I saw a little problem in your subdriver: in pkt_scan, you use a
static variable (count). This does not work with many active webcams and
also after stop / restart streaming. Instead, you may know the current
byte count using the frame values data and data_end.

> The improvement that I always dream to see is to have bridge and
> sensor
> drivers split, so sensor drivers can be shared, a-la soc_camera, I
> mean.

There were many threads about this subject, but I could not find many
common values for a same sensor with different bridges in gspca...

> Bringing that idea to the extreme, one could think even to share
> sensor
> drivers with the soc_camera framework itself, but I only have this
> abstract suggestion, no idea at all about how it can be done, sorry.
> Could it be a GSoC project for next summer?

Why not?

-- 
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

  reply	other threads:[~2008-11-13 11:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-16  5:00 [PATCH] Add support for OmniVision OV534 based USB cameras majortrips
2008-08-16  6:58 ` Hans de Goede
2008-08-16  7:46   ` Mark Ferrell
2008-08-16  8:03     ` Hans de Goede
2008-08-16 11:47       ` Mauro Carvalho Chehab
2008-08-17  7:03         ` Jean-Francois Moine
2008-08-16 11:36 ` Mauro Carvalho Chehab
2008-08-16 12:13   ` Mark Ferrell
2008-11-05 22:31     ` Mauro Carvalho Chehab
2008-11-11 17:42       ` Antonio Ospite
2008-11-11 18:15         ` Antonio Ospite
2008-11-11 20:01           ` Hans de Goede
2008-11-12 18:17             ` Antonio Ospite
2008-11-13 11:33               ` Jean-Francois Moine [this message]
2008-11-13 17:04                 ` Antonio Ospite
2008-11-13 18:30                   ` Jean-Francois Moine
2008-11-13 22:35                     ` Antonio Ospite
2008-11-14 10:55                       ` Jean-Francois Moine
2008-11-14 14:04                         ` Antonio Ospite
  -- strict thread matches above, loose matches on Subject: below --
2008-08-17 19:48 Theou Jean-Baptiste
2008-08-17 19:58 ` Theou Jean-Baptiste
2008-08-17 20:13   ` Theou Jean-Baptiste
2008-08-18  0:34   ` Mark Ferrell
2008-08-18 12:08     ` Theou Jean-Baptiste
2008-08-18 16:24       ` Mark Ferrell
2008-08-18 16:53         ` Theou Jean-Baptiste
2008-08-20 10:35           ` Theou Jean-Baptiste
2008-08-22 11:18             ` Mark Ferrell
2008-08-18  0:29 ` Mark Ferrell

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=1226576038.2040.42.camel@localhost \
    --to=moinejf@free.fr \
    --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