From: "Justin P. Mattock" <justinmattock@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: uvcvideo: unknown event type 206.
Date: Sat, 18 Apr 2009 01:33:46 -0700 [thread overview]
Message-ID: <1240043626.12779.12.camel@unix> (raw)
When using mplayer to test isight Im getting
a long line of spew-edge:
(i.g. mplayer tv:// -vf mirror)
[39906.998002] uvcvideo: unknown event type 0.
[39907.054105] uvcvideo: unknown event type 0.
[39907.194102] uvcvideo: unknown event type 236.
[39907.262102] uvcvideo: unknown event type 119.
[39907.330197] uvcvideo: unknown event type 206.
[39907.397981] uvcvideo: unknown event type 206.
[39907.466102] uvcvideo: unknown event type 206.
[39907.530109] uvcvideo: unknown event type 206.
[39907.597981] uvcvideo: unknown event type 206.
[39907.666103] uvcvideo: unknown event type 206.
[39907.734116] uvcvideo: unknown event type 206.
[39907.802106] uvcvideo: unknown event type 206.
[39907.870196] uvcvideo: unknown event type 206.
[39907.937995] uvcvideo: unknown event type 206.
[39908.006120] uvcvideo: unknown event type 206.
[39908.070200] uvcvideo: unknown event type 206.
[39908.137981] uvcvideo: unknown event type 206.
[39908.206111] uvcvideo: unknown event type 206.
[39908.274102] uvcvideo: unknown event type 206.
[39908.342105] uvcvideo: unknown event type 206.
[39908.410197] uvcvideo: unknown event type 206.
[39908.477981] uvcvideo: unknown event type 206.
[39908.542105] uvcvideo: unknown event type 206.
[39908.610215] uvcvideo: unknown event type 206.
[39908.677982] uvcvideo: unknown event type 206.
[39908.746102] uvcvideo: unknown event type 206.
[39908.814096] uvcvideo: unknown event type 206.
continues with "type 206" until I hit ctrl C".
(as for images etc.. fine..
you would never expect anything wrong, just spam from dmesg);
regards;
Justin P. Mattock
reply other threads:[~2009-04-18 8:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1240043626.12779.12.camel@unix \
--to=justinmattock@gmail.com \
--cc=linux-kernel@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 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.