From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: "ext Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "linux-fbdev-devel@lists.sourceforge.net"
<linux-fbdev-devel@lists.sourceforge.net>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: [REVIEW PATCH] Added OMAP3EVM support on Tomis FBDEV/DSS Patches
Date: Mon, 17 Nov 2008 11:49:52 +0200 [thread overview]
Message-ID: <1226915392.6860.18.camel@tubuntu> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739403E5F2B75A@dbde02.ent.ti.com>
On Sat, 2008-11-15 at 14:12 +0530, ext Hiremath, Vaibhav wrote:
>
> Thanks,
> Vaibhav Hiremath
>
> > -----Original Message-----
> > From: Tomi Valkeinen [mailto:tomi.valkeinen@nokia.com]
> > Sent: Friday, November 14, 2008 9:24 PM
> > To: Hiremath, Vaibhav
> > Cc: linux-fbdev-devel@lists.sourceforge.net; linux-
> > omap@vger.kernel.org
> > Subject: RE: [REVIEW PATCH] Added OMAP3EVM support on Tomis
> > FBDEV/DSS Patches
> >
> > Hi,
> > On Fri, 2008-11-14 at 18:05 +0530, ext Hiremath, Vaibhav wrote:
> >
> > > >
> > > > I think the LCD panel on SDP and EVM boards are the same, so we
> > > > should
> > > > only have one driver. Do you have specifications about the LCD?
> > The
> > > > manufacturer, model etc?. I didn't find any proper information
> > about
> > > > the
> > > > LCD.
> > > >
> > > [Hiremath, Vaibhav] The LCD on OMAP3EVM is Sharp LCD (Model No. -
> > LS037V7DW01).
> > > Koen has already conformed that panel3430sdp.c is working with
> > OMAP3EVM, let me try at my end. If it works properly then we can
> > have same file to build for both SDP and EVM. But in that case it
> > make sense to rename file to panel-lcd.c.
> > >
> >
> > I took the liberty to add you EVM changes to my tree, with a comment
> > about the origin. I also changed the SDP panel name to sharp panel,
> > and
> > made both EVM and SDP use that. But I can't test the EVM, as I don't
> > have one.
> >
> [Hiremath, Vaibhav] It's ok; you can incorporate required changes from my patches, no issues at all. Please share the code base which you merged from my patch so that I can validate it on EVM, since you don't have EVM to test.
>
My current version is available in master branch on
http://www.bat.org/~tomba/git/linux-omap-dss.git/
I will be keeping the master branch up to date with my changes and
linux-omap. And I will be rebasing the branch.
pub1 branch has the version that I emailed to mailing lists some time
ago. You can diff master and pub1 branches to see what's changed.
Tomi
next prev parent reply other threads:[~2008-11-17 9:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 6:32 [REVIEW PATCH] Added OMAP3EVM support on Tomis FBDEV/DSS Patches hvaibhav
2008-11-14 10:54 ` Tomi Valkeinen
2008-11-14 12:35 ` Hiremath, Vaibhav
2008-11-14 13:53 ` Hiremath, Vaibhav
2008-11-14 15:53 ` Tomi Valkeinen
2008-11-14 19:44 ` Koen Kooi
2008-11-15 8:45 ` Hiremath, Vaibhav
2008-11-18 12:09 ` Hiremath, Vaibhav
2008-11-18 12:21 ` Koen Kooi
2008-11-15 8:42 ` Hiremath, Vaibhav
2008-11-17 9:49 ` Tomi Valkeinen [this message]
2008-11-14 11:38 ` Koen Kooi
2008-11-14 11:49 ` Shah, Hardik
2008-11-14 21:50 ` Tony Lindgren
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=1226915392.6860.18.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=hvaibhav@ti.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-omap@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;
as well as URLs for NNTP newsgroup(s).