From: Yan Seiner <yan@seiner.com>
To: Andy Walls <awalls@md.metrocast.net>
Cc: linux-media@vger.kernel.org
Subject: Re: cx231xx kernel oops
Date: Sun, 04 Dec 2011 20:21:40 -0800 [thread overview]
Message-ID: <4EDC46D4.6060708@seiner.com> (raw)
In-Reply-To: <1323058527.12343.3.camel@palomino.walls.org>
Andy Walls wrote:
> On Sun, 2011-12-04 at 18:01 -0800, Yan Seiner wrote:
>
>> I am experiencing a kernel oops when trying to use a Hauppage USB Live 2
>> frame grabber. The oops is below.
>>
>> The system is a SOC 260Mhz Broadcom BCM47XX access point running OpenWRT.
>>
>> root@anchor:/# uname -a
>> Linux anchor 3.0.3 #13 Sun Dec 4 08:04:41 PST 2011 mips GNU/Linux
>>
>> The OOPS could be due to the limited hardware or something else. I'd
>> appreciate any suggestions for making this work. I was hoping with
>> hardware compression I could make it work on this platform. I am
>> currently using a Hauppage USB Live (saa7115 based) with no problems but
>> with limited resolution.
>>
>> cx231xx v4l2 driver loaded.
>> cx231xx #0: New device Hauppauge Hauppauge Device @ 480 Mbps (2040:c200) with 5 interfaces
>> cx231xx #0: registering interface 1
>> cx231xx #0: can't change interface 3 alt no. to 3: Max. Pkt size = 0
>> cx231xx #0: can't change interface 4 alt no. to 1: Max. Pkt size = 0
>> cx231xx #0: Identified as Hauppauge USB Live 2 (card=9)
>> cx231xx #0: cx231xx_dif_set_standard: setStandard to ffffffff
>> cx231xx #0: Changing the i2c master port to 3
>> cx231xx #0: cx25840 subdev registration failure
>>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> The cx231xx driver requires the cx25840 module. I'll wager you didn't
> install it on your router.
>
>
Right in one. I did not because it didn't seem to be required - no
missing symbols or error messages. Would a warning to syslog be possible?
With 8MB of flash, I remove everything that is not required.
--Yan
--
Few people are capable of expressing with equanimity opinions which differ from the prejudices of their social environment. Most people are even incapable of forming such opinions.
Albert Einstein
next prev parent reply other threads:[~2011-12-05 4:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 2:01 cx231xx kernel oops Yan Seiner
2011-12-05 4:15 ` Andy Walls
2011-12-05 4:21 ` Yan Seiner [this message]
2011-12-05 4:45 ` Yan Seiner
2011-12-05 4:54 ` Yan Seiner
2011-12-05 12:19 ` Yan Seiner
2011-12-05 12:31 ` Yan Seiner
2011-12-05 15:18 ` Andy Walls
2011-12-05 15:28 ` Yan Seiner
2011-12-12 1:04 ` Yan Seiner
2011-12-12 12:34 ` Andy Walls
2011-12-12 12:46 ` Yan Seiner
2011-12-12 14:23 ` Devin Heitmueller
2011-12-12 15:58 ` Yan Seiner
2011-12-12 16:22 ` Devin Heitmueller
2011-12-12 16:29 ` Yan Seiner
2011-12-13 4:42 ` Yan Seiner
2011-12-13 14:47 ` Yan Seiner
2011-12-05 15:06 ` Andy Walls
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=4EDC46D4.6060708@seiner.com \
--to=yan@seiner.com \
--cc=awalls@md.metrocast.net \
--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 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.