From: Tony Lindgren <tony@atomide.com>
To: Trilok Soni <soni.trilok@gmail.com>
Cc: Sakari Ailus <sakari.ailus@nokia.com>,
Linux OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] OMAP: Add OmniVision ov9640 sensor driver with new v4l2 interface.
Date: Mon, 17 Sep 2007 11:33:39 -0700 [thread overview]
Message-ID: <20070917183338.GI21226@atomide.com> (raw)
In-Reply-To: <5d5443650709060541q5112eb7ei5132efbcc6be7d13@mail.gmail.com>
* Trilok Soni <soni.trilok@gmail.com> [070906 05:44]:
> Hi All,
>
> Copying the commit message:
>
> -------------------------------snip-----------------------
> Subject: [PATCH] OMAP: Add OmniVision ov9640 sensor driver with new
> v4l2 interface.
>
> - Add OmniVision ov9640 sensor driver with new I2C style bindings,
> converted to use new v4l2 sensor interface and moved
> platform specific data to board files.
>
> - Sensor used with H4 omap2420 doesn't give the correct capture
> output and need to be investigated.
>
> - Sensor detection works.
> -------------------------------snip-------------------------
>
> So, it would be great if people having H4 can test and report the
> problem we might have in existing sensor/camera controller driver to
> get the correct capture output. Thanx.
>
> Please not that this driver is added in "drivers/media/video"
> directory instead of the "omap" one, as we are not planning to take
> extra directory to upstream for camera.
Pushing this too. Are there files under drivers/media/video/omap that
we can remove now?
Regards,
Tony
next prev parent reply other threads:[~2007-09-17 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 12:41 [PATCH] OMAP: Add OmniVision ov9640 sensor driver with new v4l2 interface Trilok Soni
2007-09-17 18:33 ` Tony Lindgren [this message]
2007-09-18 6:17 ` Trilok Soni
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=20070917183338.GI21226@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=sakari.ailus@nokia.com \
--cc=soni.trilok@gmail.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.