From: Michael Trimarchi <michael@panicking.kicks-ass.org>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: ov538-ov7690
Date: Tue, 10 Nov 2009 11:18:13 +0100 [thread overview]
Message-ID: <4AF93DE5.6060901@panicking.kicks-ass.org> (raw)
In-Reply-To: <4AF89498.3000103@panicking.kicks-ass.org>
Hi,
Michael Trimarchi wrote:
> Hi all
>
> I'm working on the ov538 bridge with the ov7690 camera connected.
> Somentimes I receive
>
> [ 1268.146705] gspca: ISOC data error: [110] len=1020, status=-71
> [ 1270.946739] gspca: ISOC data error: [114] len=1020, status=-71
> [ 1271.426689] gspca: ISOC data error: [82] len=1020, status=-71
> [ 1273.314640] gspca: ISOC data error: [1] len=1020, status=-71
> [ 1274.114661] gspca: ISOC data error: [17] len=1020, status=-71
> [ 1274.658718] gspca: ISOC data error: [125] len=1020, status=-71
> [ 1274.834666] gspca: ISOC data error: [21] len=1020, status=-71
> [ 1275.666684] gspca: ISOC data error: [94] len=1020, status=-71
> [ 1275.826645] gspca: ISOC data error: [40] len=1020, status=-71
> [ 1276.226721] gspca: ISOC data error: [100] len=1020, status=-71
>
> This error from the usb, how are they related to the camera?
>
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?
Michael
> Michael
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-11-10 10:22 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 ` Michael Trimarchi [this message]
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 ` ov538-ov7690 Michael Trimarchi
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=4AF93DE5.6060901@panicking.kicks-ass.org \
--to=michael@panicking.kicks-ass.org \
--cc=linux-media@vger.kernel.org \
/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