I'm working with a custom board based on an Overo WaterStorm com. The
processor is a DM3730. The kernel is 2.6.32 based.
I'm trying to stress test the camera ISP by rapidly opening and closing
the video device with ( while true; do gst-launch v4l2src
device=/dev/video0 !
I'm seeing weird read errors on a DM3730. Has anyone seen anything like
this before?
Environment:
factory images from
http://cumulus.gumstix.org/images/angstrom/factory/2011-08-30-1058/
loaded onto and MMC card on a
Gumstix WaterStorm on a Chestnut board
Commands:
dd if=/dev/urandom
No one can confirm this?
On 02/03/2011 08:31 AM, Adam Wozniak wrote:
I'm hoping I'm just not understanding something and this isn't as
broke as I fear it is.
I'm using the ISP on an OMAP3530, linux 2.6.32. I've got some kernel
code I want to lock in both the process context and the ISP
I'm hoping I'm just not understanding something and this isn't as broke
as I fear it is.
I'm using the ISP on an OMAP3530, linux 2.6.32. I've got some kernel
code I want to lock in both the process context and the ISP interrupt
context, so I'm using a spinlock. As I understand it, locking
Hello,
I'm working with an OMAP3530 based custom board. The board has 4
cameras attached to it, using the drivers/media/video/omap34xxcam.c and
.../ov3640.c and .../isp/isp*.c drivers. We've modified these drivers
slightly so we can mux an I2C bus to talk to each different camera.
When we
