public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Agustin <gatoguan-os@yahoo.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Arm Kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 2/4] soc-camera: camera host driver for i.MX3x SoCs
Date: Thu, 19 Feb 2009 03:57:15 -0800 (PST)	[thread overview]
Message-ID: <900217.19195.qm@web32107.mail.mud.yahoo.com> (raw)

Hi Guennadi,
---- Mensaje original ----
> De: Sascha Hauer <s.hauer@pengutronix.de>
> On Wed, Feb 18, 2009 at 01:03:38AM +0100, Guennadi Liakhovetski wrote:
> > From: Guennadi Liakhovetski 
> > 
> > Tested with 8 bit Bayer and 8 bit monochrome video.
> > 
> > Signed-off-by: Guennadi Liakhovetski 
> > ---
> 
> Acked-by: Sascha Hauer 
> for the platform part. I can't say much to the driver itself.
> 
> Sascha
> 
> > 
> > This is how I expect this driver to appear in my pull request. So, please, 
> > review, test heavily :-)

I want to test it but while applying to mxc-master branch I observed that you use it on top of, at least, framebuffer stuff: #include <mach/mx3fb.h>.

Should I apply fb patchset in order to make this one work? (Otherwise, I can proceed with a minor merging effort.)

I am already using your drivers in their original version, I can get some new pictures with this one pretty soon.

--Agustín.

             reply	other threads:[~2009-02-19 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19 11:57 Agustin [this message]
2009-02-19 12:16 ` [PATCH 2/4] soc-camera: camera host driver for i.MX3x SoCs Guennadi Liakhovetski
  -- strict thread matches above, loose matches on Subject: below --
2009-02-17 18:36 Rv: mx3-camera on current mxc kernel tree Agustin
     [not found] ` <499B2A60.9080009@epfl.ch>
2009-02-18  0:02   ` [PATCH/RFC 0/4] i.MX31 camera host driver + IPU updates Guennadi Liakhovetski
2009-02-18  0:03     ` [PATCH 2/4] soc-camera: camera host driver for i.MX3x SoCs Guennadi Liakhovetski
2009-02-19 10:57       ` Sascha Hauer

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=900217.19195.qm@web32107.mail.mud.yahoo.com \
    --to=gatoguan-os@yahoo.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-media@vger.kernel.org \
    /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