From: Daniel Toussaint <daniel@dmhome.net>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 3/4] Add support for DEVKIT8000 LCD
Date: Fri, 13 Nov 2009 00:28:33 +0800 [thread overview]
Message-ID: <4AFC37B1.7060801@dmhome.net> (raw)
In-Reply-To: <1258026396.20378.106.camel@tubuntu.research.nokia.com>
On Thu, Nov 12, 2009 at 7:46 PM, Tomi Valkeinen
<tomi.valkeinen@nokia.com <mailto:tomi.valkeinen@nokia.com>> wrote:
On Thu, 2009-11-12 at 11:23 +0100, ext Kim Botherway wrote:
> This patch add support for the Timll DEVKIT8000 LCD panel
I don't handle old omapfb patches. I think you should contact Imre Deak
for those, although my advise would be to use the new display subsystem
driver.
Question more or less related to this thread : when submitting new
boards, it is better to work with DSS2 directly right ? I am also
preparing a new board patch at this point, so I would like to know what
is the sanest way to work ? Patch the linux-omap-2.6 tree with DSS2
patches , and then diff from there ? Or is is wiser to first submit
without display related items, and wait for linux-omap-2.6 tree to have
DSS2 support - which is going to happen soon I guess.
Thanks
Tomi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
<mailto:majordomo@vger.kernel.org>
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-12 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 10:23 [PATCH 3/4] Add support for DEVKIT8000 LCD Kim Botherway
2009-11-12 10:58 ` Vimal Singh
2009-11-12 11:46 ` Tomi Valkeinen
2009-11-12 16:28 ` Daniel Toussaint [this message]
[not found] ` <6cb69d4a0911120814i4a29e896g2436aea9670d193c@mail.gmail.com>
2009-11-13 11:50 ` Tomi Valkeinen
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=4AFC37B1.7060801@dmhome.net \
--to=daniel@dmhome.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