Yan Seiner wrote:
Yan Seiner wrote:
Andy Walls wrote:
800 MB for 320x420 frames? It sounds like your app has gooned its
requested buffer size.
That's an understatement. :-)
This might be due to endianess differences between MIPS abd x86 and
your app only being written and tested on x8
Yan Seiner wrote:
Andy Walls wrote:
800 MB for 320x420 frames? It sounds like your app has gooned its
requested buffer size.
That's an understatement. :-)
This might be due to endianess differences between MIPS abd x86 and
your app only being written and tested on x86.
My specul
On Mon, December 12, 2011 8:22 am, Devin Heitmueller wrote:
> On Mon, Dec 12, 2011 at 10:58 AM, Yan Seiner wrote:
>>> Also, just to be clear, the USB Live 2 doesn't have any onboard
>>> hardware compression. It has comparable requirements related to USB
>>> bus utilization as any other USB frame
On Mon, Dec 12, 2011 at 10:58 AM, Yan Seiner wrote:
>> Also, just to be clear, the USB Live 2 doesn't have any onboard
>> hardware compression. It has comparable requirements related to USB
>> bus utilization as any other USB framegrabber. The only possible
>> advantage you might get is that it
On Mon, December 12, 2011 6:23 am, Devin Heitmueller wrote:
>
> For what it's worth, I did do quite a bit of work on cx231xx,
> including work for mips and arm platforms. That said, all the work
> done was on the control interfaces rather than the buffer management
> (my particular use case didn
On Mon, Dec 12, 2011 at 7:46 AM, Yan Seiner wrote:
> Andy Walls wrote:
>>
>> 800 MB for 320x420 frames? It sounds like your app has gooned its
>> requested buffer size.
>>
>
>
> That's an understatement. :-)
>
>
>>
>> This might be due to endianess differences between MIPS abd x86 and your
>> ap
Andy Walls wrote:
800 MB for 320x420 frames? It sounds like your app has gooned its requested
buffer size.
That's an understatement. :-)
This might be due to endianess differences between MIPS abd x86 and your app
only being written and tested on x86.
My speculation too. I don't
Yan Seiner wrote:
>I'm resurrecting an older thread. I have a Hauppage USB Live2
>connected
>to a MIPS box running openWRT. I tried this earlier on a older
>hardware
>running the 3.0.3 kernel. This is with newer hardware running
>2.6.39.4. The driver attempts to allocate 800MB (!!!) of mem
I'm resurrecting an older thread. I have a Hauppage USB Live2 connected
to a MIPS box running openWRT. I tried this earlier on a older hardware
running the 3.0.3 kernel. This is with newer hardware running
2.6.39.4. The driver attempts to allocate 800MB (!!!) of memory for the
buffer and fa
On Mon, December 5, 2011 7:18 am, Andy Walls wrote:
> Yan Seiner wrote:
>>ehci_hcd :00:02.2: fatal error
>>ehci_hcd :00:02.2: HC died; cleaning up
>>ehci_hcd :00:02.2: force halt; handshake c0350024 4000 4000
>
> Well, you probably have figured out you have a USB stack probl
Yan Seiner wrote:
>I'm still seeing a kernel oops on use.
>
>Module Size Used byNot tainted
>cx231xx 124608 0
>cx2341x13552 1 cx231xx
>cx2584035568 1
>rc_core12640 1 cx231xx
>videobuf_vmalloc
Yan Seiner wrote:
>Yan Seiner wrote:
>> 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 acc
Yan Seiner wrote:
I'm still seeing a kernel oops on use.
One more minor point:
Before the kernel oops, I have /dev/video0. After the oops, I have
/dev/video0 and /dev/video1 - probably related to the ehci crash.
--
Few people are capable of expressing with equanimity opinions which differ f
I'm still seeing a kernel oops on use.
Module Size Used byNot tainted
cx231xx 124608 0
cx2341x13552 1 cx231xx
cx2584035568 1
rc_core12640 1 cx231xx
videobuf_vmalloc3168 1 cx231xx
videobu
Yan Seiner wrote:
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:/# un
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
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
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
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
19 matches
Mail list logo
