From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: DongSoo Kim <dongsoo.kim@gmail.com>
Cc: "Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Nagalla, Hari" <hnagalla@ti.com>,
"Ailus Sakari (Nokia-D/Helsinki)" <Sakari.Ailus@nokia.com>,
"Toivonen Tuukka.O (Nokia-D/Oulu)" <tuukka.o.toivonen@nokia.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"kyungmin.park@samsung.com" <kyungmin.park@samsung.com>,
"형준 김" <riverful.kim@samsung.com>,
"jongse.won@samsung.com" <jongse.won@samsung.com>
Subject: Re: [REVIEW PATCH 11/14] OMAP34XXCAM: Add driver
Date: Fri, 13 Feb 2009 12:02:26 +0200 [thread overview]
Message-ID: <49954532.2070502@maxwell.research.nokia.com> (raw)
In-Reply-To: <5e9665e10902112352i57177f20r9022a7cb8a66fa0@mail.gmail.com>
DongSoo Kim wrote:
> Thank you for your comment.
>
> BTW, what should I do if I would rather use external ISP device than
> OMAP3 internal ISP feature?
>
> You said that you just have raw sensors by now, so you mean this patch
> is not verified working with some ISP modules?
I haven't verified it myself. Others might be using it.
> I'm testing your patch on my own omap3 target board with NEC ISP...but
> unfortunately not working yet ;(
NEC ISP? A sensor with NEC ISP integrated?
> I should try more harder. more research is needed :)
Thanks for the interest. :-)
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
next prev parent reply other threads:[~2009-02-13 10:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Acl1IyQQvIDQejCAQ5O/QnkHIBmt3w==>
2009-01-13 2:03 ` [REVIEW PATCH 11/14] OMAP34XXCAM: Add driver Aguirre Rodriguez, Sergio Alberto
2009-01-13 7:24 ` Hans Verkuil
2009-02-06 2:26 ` DongSoo Kim
2009-02-11 4:00 ` DongSoo Kim
2009-02-12 7:09 ` Sakari Ailus
2009-02-12 7:52 ` DongSoo Kim
2009-02-13 9:31 ` Arun KS
2009-02-13 10:04 ` DongSoo(Nathaniel) Kim
2009-02-13 10:02 ` Sakari Ailus [this message]
2009-02-13 10:11 ` DongSoo(Nathaniel) Kim
2009-03-10 13:34 Hans Verkuil
-- strict thread matches above, loose matches on Subject: below --
2009-03-04 8:12 Hans Verkuil
[not found] <5e9665e10903021848u328e0cd4m5186344be15b817@mail.gmail.com>
[not found] ` <19F8576C6E063C45BE387C64729E73940427BC9B86@dbde02.ent.ti.com>
2009-03-03 5:13 ` DongSoo(Nathaniel) Kim
2009-03-03 7:36 ` Hans Verkuil
2009-03-04 0:42 ` DongSoo(Nathaniel) Kim
2009-03-04 7:39 ` Hans Verkuil
2009-03-04 7:49 ` Tuukka.O Toivonen
2009-03-04 19:22 ` Sakari Ailus
2009-03-04 21:05 ` Hans Verkuil
2009-03-04 21:46 ` Aguirre Rodriguez, Sergio Alberto
2009-03-04 22:44 ` Hans Verkuil
2009-03-04 23:30 ` Aguirre Rodriguez, Sergio Alberto
2009-03-05 7:39 ` Hans Verkuil
2009-03-05 20:11 ` Sakari Ailus
2009-03-05 21:24 ` Hans Verkuil
2009-03-10 12:14 ` Sakari Ailus
2009-03-04 23:42 ` Trent Piepho
2009-03-05 2:25 ` hermann pitton
2009-03-03 7:38 ` Sakari Ailus
[not found] <Aclb0Ghhhph2tRyARSuubB27tGfovg==>
2008-12-11 20:38 ` Aguirre Rodriguez, Sergio Alberto
2009-02-23 8:26 ` DongSoo(Nathaniel) Kim
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=49954532.2070502@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=Sakari.Ailus@nokia.com \
--cc=dongsoo.kim@gmail.com \
--cc=hnagalla@ti.com \
--cc=jongse.won@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=riverful.kim@samsung.com \
--cc=saaguirre@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox