All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@nokia.com>
To: John Sarman <johnsarman@gmail.com>
Cc: Sergio Aguirre <saaguirre@ti.com>,
	"Toivonen Tuukka.O (Nokia-D/Oulu)" <tuukka.o.toivonen@nokia.com>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: Help bringing up a sensor driver for isp omap34xx.c
Date: Mon, 20 Jul 2009 12:08:24 +0300	[thread overview]
Message-ID: <4A643408.2020408@nokia.com> (raw)
In-Reply-To: <bb2708720907151444l3a93bcb3y75d227c4828ec311@mail.gmail.com>

(Dropped Sameer and Mohit from Cc.)

John Sarman wrote:
> Hello,

Hi,

>    I am having a problem deciphering what is wrong with my sensor
> driver.  It seems that everything operates on the driver but that I am
> getting buffer overflows.  I have fully tested the image sensor and it
> is set to operate in 640x480 mode. currently it is like 648x 487 for
> the dummy pixels and lines.  I have enabled all the debugging #defines
> in the latest code from the gitorious repository.  I also had to edit
> a few debug statements because they cause the compile to fail. Those
> failures were due to the resizer rewrite and since the #defines were
> commented out that code was never compiled.  Anyways here is my dmesg
> after I open and select the /dev/video0.
> 
> I have been banging my head against a wall for 2 weeks now.
> 
> Thanks,

...

ISPSBL_PCR_CCDCPRV_2_RSZ_OVF very often without any ill effects (AFAIR) 
which consequently causes OVF_IRQ to be triggered. It can be ignored.

How are your images? :) Printing things that big from the interrupt 
handler might hamper with your image captuting efforts, too.

Cheers,

-- 
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com

  parent reply	other threads:[~2009-07-20  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 21:44 Help bringing up a sensor driver for isp omap34xx.c John Sarman
2009-07-15 21:51 ` Aguirre Rodriguez, Sergio Alberto
2009-07-20  9:08 ` Sakari Ailus [this message]
2009-07-20 10:53   ` John Sarman

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=4A643408.2020408@nokia.com \
    --to=sakari.ailus@nokia.com \
    --cc=johnsarman@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=saaguirre@ti.com \
    --cc=sakari.ailus@maxwell.research.nokia.com \
    --cc=tuukka.o.toivonen@nokia.com \
    /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.