From: Yan Seiner <yan@seiner.com>
To: linux-media@vger.kernel.org
Subject: saa7115: black image
Date: Sun, 11 Mar 2012 10:42:36 -0700 [thread overview]
Message-ID: <4F5CE40C.6040706@seiner.com> (raw)
I have an embedded platform with a Hauppage USB Live video capture
dongle. I recently upgraded to 3.0.12 and now I get no image at all - a
nice pure black is all I get.
I am sure that the dongle is getting a signal. This same hardware used
to work with an older 2.6 kernel.
Partial lsmod:
root@anchor:/etc# lsmod
Module Size Used by Not tainted
saa7115 11296 0
usbvision 48704 0
v4l2_common 4336 2 saa7115,usbvision
videodev 62768 3 saa7115,usbvision,v4l2_common
i2c_core 12240 5
saa7115,usbvision,v4l2_common,videodev,i2c_dev
[ 33.640000] usbcore: registered new interface driver usb-storage
[ 33.644000] USB Mass Storage support registered.
[ 33.708000] Linux video capture interface: v2.00
[ 34.084000] usbvision_probe: Hauppauge WinTV USB Live Pro (NTSC M/N)
found
[ 34.092000] USBVision[0]: registered USBVision Video device video0 [v4l2]
[ 34.100000] usbcore: registered new interface driver usbvision
[ 34.104000] USBVision USB Video Device Driver for Linux : 0.9.10
and this shows up every time the device is opened:
[ 219.772000] saa7115 0-0025: saa7113 found (1f7113d0e100000) @ 0x4a
(usbvision-3-1)
I can't help but think I am missing a module, or firmware, or
something.... But with no messages to go on it's a bit of a mystery.
And yes, I've tried different inputs on the dongle; 0 is the composite
in and 1 is the s-video. I'm using input 0.
--
Honoring our vets.
http://www.bataanmarch.com/
next reply other threads:[~2012-03-11 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 17:42 Yan Seiner [this message]
2012-03-11 18:10 ` saa7115: black image Yan Seiner
2012-03-12 1:01 ` Yan Seiner
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=4F5CE40C.6040706@seiner.com \
--to=yan@seiner.com \
--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