From: Tony Lindgren <tony@atomide.com>
To: Trilok Soni <soni.trilok@gmail.com>
Cc: Sakari Ailus <sakari.ailus@nokia.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
video4linux-list@redhat.com,
"linux-omap@vger.kernel.org Mailing List"
<linux-omap@vger.kernel.org>
Subject: Re: [PATCH] Add OMAP2 camera driver
Date: Fri, 28 Nov 2008 09:04:50 -0800 [thread overview]
Message-ID: <20081128170446.GE6640@atomide.com> (raw)
In-Reply-To: <5d5443650811270942n2421ea27v194e4c8aa1933dda@mail.gmail.com>
* Trilok Soni <soni.trilok@gmail.com> [081127 09:42]:
> Hi Sakari,
>
> >
> > It *might* be possible that the same camera block would be used in non-OMAP
> > CPUs as well but I guess it is safe to assume that it depends on ARCH_OMAP
> > now.
>
> Right, better to keep ARCH_OMAP as dependancy.
>
> >>
> >> Thanks for the review comments. I will resubmit the patch.
> >
> > Is this exactly the same code that was removed from linux-omap a while ago?
> >
> > ---
> > commit ebdae9abf598ae8a3ee1c8c477138f82b40e7809
> > Author: Tony Lindgren <tony@atomide.com>
> > Date: Mon Oct 27 13:33:13 2008 -0700
> >
> > REMOVE OMAP LEGACY CODE: Delete all old omap specific v4l drivers
> >
> > All v4l development must be done on the v4l mailing list with linux-omap
> > list cc'd.
> >
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
> >
>
> Yes, it the same commit from which I have based this patch.
>
> > ---
> >
> > Although I haven't had time to discuss this anywhere, I though a possible
> > reason of for the removal was that some parts of the code are not that
> > pretty (e.g. DMA) and those parts should be rewritten.
Well mostly the motivation for removal from linux-omap tree was to
send the camera development to v4l list. For the camera DMA issues, I guess
Sakari you know best how it should be handled.
> > But yes, the OMAP 2 camera driver does actually work and I would suppose it
> > has users, too (think N800/N810).
>
> Yes, I have both ;)
>
> >
> > I'm in if the aim is to get this back to linux-omap. :-) (Waiting for the
> > next patch from Trilok.)
>
> It will come down to linux-omap via mainline tree :)
I like that :)
Tony
next prev parent reply other threads:[~2008-11-28 17:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 18:44 [PATCH] Add OMAP2 camera driver Trilok Soni
2008-11-26 20:16 ` Hans Verkuil
2008-11-27 7:23 ` Trilok Soni
2008-11-27 9:35 ` Sakari Ailus
2008-11-27 17:42 ` Trilok Soni
2008-11-28 17:04 ` Tony Lindgren [this message]
2008-11-28 10:07 ` Trilok Soni
2008-12-01 12:57 ` Hans Verkuil
2008-12-01 13:32 ` Trilok Soni
2008-12-01 13:34 ` Sakari Ailus
2008-12-03 4:41 ` Hiremath, Vaibhav
2008-12-03 6:48 ` Trilok Soni
2008-12-03 7:05 ` Hiremath, Vaibhav
2008-12-03 7:32 ` Hans Verkuil
2008-12-03 9:34 ` Koen Kooi
2008-12-03 9:37 ` Hiremath, Vaibhav
2008-12-04 23:45 ` Tony Lindgren
2008-12-05 18:57 ` Hiremath, Vaibhav
2008-12-05 19:12 ` Tony Lindgren
2008-12-03 9:41 ` Trilok Soni
2008-12-03 12:47 ` Sakari Ailus
2008-12-04 18:28 ` Aguirre Rodriguez, Sergio Alberto
2008-12-08 12:05 ` Sakari Ailus
2008-12-08 21:37 ` Mauro Carvalho Chehab
2008-12-08 21:42 ` Mauro Carvalho Chehab
2008-12-08 21:58 ` Mauro Carvalho Chehab
2008-12-09 8:53 ` Sakari Ailus
2008-12-10 11:43 ` 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=20081128170446.GE6640@atomide.com \
--to=tony@atomide.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-omap@vger.kernel.org \
--cc=sakari.ailus@nokia.com \
--cc=soni.trilok@gmail.com \
--cc=video4linux-list@redhat.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