All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Trimarchi <michael@panicking.kicks-ass.org>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	Hans de Goede <j.w.r.degoede@hhs.nl>
Subject: Re: ov538-ov7690
Date: Wed, 11 Nov 2009 11:27:27 +0100	[thread overview]
Message-ID: <4AFA918F.10708@panicking.kicks-ass.org> (raw)
In-Reply-To: <20091110165747.35d31687@pedra.chehab.org>

Mauro Carvalho Chehab wrote:
> Em Tue, 10 Nov 2009 09:09:10 -0800
> Randy Dunlap <rdunlap@xenotime.net> escreveu:
> 
>>>> (**) This is also one of several codes that different kinds of host
>>>> controller use to indicate a transfer has failed because of device
>>>> disconnect.  In the interval before the hub driver starts disconnect
>>>> processing, devices may receive such fault reports for every request.
>>>>
>>>>
>>>>> Ok, this is not a big issue because I can use vlc to test the camera. But anybody
>>>>> knows why camorama, camstream, cheese crash during test. is it driver depend? or not?
>>>> Could be driver.  Easily could be a device problem too.
>>> I think that it can be a vl2 vl1 problem. Because now I can manage in skype too using
>>> the v4l1-compat library. Maybe my 2.6.32-rc5 is too new :(
>> I don't even know what vl2 vl1 means. ;)
> 
> He is probably referring to V4L1 x V4L2 API calls. Very unlikely. What libv4l

Yes

> does is to convert userspace calls via V4L1 to a V4L2 call to kernel. So,
> you're basically using the same API to communicate to userspace.

Ugly but very usefull in such application like skype, and people want it :(

> 
> It should be noticed that, if you're not using libv4l for the other
> applications, then you may be using a different format at the driver, since
> libv4l has the capability of doing format conversions.
> 
> So, it could be possible that the device firmware for some formats are broken.
> 
> Another possibility is that maybe libv4l is just discarding such errors.
> 
> Or, as Randy mentioned, it can be just a cable or a connector with bad contact.

Change the connector fix the packet problem. So at least the version ov538-ov7690
seems ok.

Thanks

      reply	other threads:[~2009-11-11 10:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 22:15 ov538-ov7690 Michael Trimarchi
2009-11-10 10:18 ` ov538-ov7690 Michael Trimarchi
2009-11-10 16:10   ` ov538-ov7690 Randy Dunlap
2009-11-10 16:51     ` ov538-ov7690 Michael Trimarchi
2009-11-10 17:09       ` ov538-ov7690 Randy Dunlap
2009-11-10 18:57         ` ov538-ov7690 Mauro Carvalho Chehab
2009-11-11 10:27           ` Michael Trimarchi [this message]

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=4AFA918F.10708@panicking.kicks-ass.org \
    --to=michael@panicking.kicks-ass.org \
    --cc=j.w.r.degoede@hhs.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=rdunlap@xenotime.net \
    /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.