From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: tony@atomide.com
Cc: linux-omap@vger.kernel.org, Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: [PATCH 0/6] OMAP: board file changes for DSS2 porting
Date: Mon, 9 May 2011 10:36:01 +0300 [thread overview]
Message-ID: <1304926567-26814-1-git-send-email-tomi.valkeinen@ti.com> (raw)
Hi Tony,
I posted last week a patch set porting most of the old omapfb OMAP2/3 drivers
to DSS2 (http://marc.info/?l=linux-fbdev&m=130451207802788&w=2). That patch set
contains changes to both the drivers and the board files, and it seems there is
already a minor conflict in them.
So I think it's simpler to divide the set into two parts, this one, which
contains the board file changes, and another containing the driver changes.
Merging will probably go easier if you can take this patch set via linux-omap,
and I'll take the driver changes via dss2 tree.
Applying this set without the driver changes will obviously disable the
displays of the affected boards until the drivers are also merged.
Tomi
Tomi Valkeinen (6):
OMAP: RX51: Remove unused old omapfb stuff
OMAP: omap3touchbook: Remove unused lcd stuff
OMAP: 2420SDP: Port the display driver to new DSS2
OMAP: LDP: Port the display driver to new DSS2
OMAP: H4: Port the display driver to new DSS2
OMAP: Apollon: Port the display driver to new DSS2
arch/arm/mach-omap2/board-2430sdp.c | 84 +++++++++++++++++++++++-----
arch/arm/mach-omap2/board-apollon.c | 34 +++++++----
arch/arm/mach-omap2/board-h4.c | 41 ++++++++-----
arch/arm/mach-omap2/board-ldp.c | 73 +++++++++++++++++++++---
arch/arm/mach-omap2/board-omap3touchbook.c | 18 ------
arch/arm/mach-omap2/board-rx51.c | 25 --------
6 files changed, 180 insertions(+), 95 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-05-09 7:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 7:36 Tomi Valkeinen [this message]
2011-05-09 7:36 ` [PATCH 1/6] OMAP: RX51: Remove unused old omapfb stuff Tomi Valkeinen
2011-05-09 7:36 ` [PATCH 2/6] OMAP: omap3touchbook: Remove unused lcd stuff Tomi Valkeinen
2011-05-09 7:36 ` [PATCH 3/6] OMAP: 2420SDP: Port the display driver to new DSS2 Tomi Valkeinen
2011-05-09 8:21 ` Igor Grinberg
2011-05-09 16:57 ` Tomi Valkeinen
2011-05-09 7:36 ` [PATCH 4/6] OMAP: LDP: " Tomi Valkeinen
2011-05-09 8:08 ` stanley.miao
2011-05-11 4:58 ` Janorkar, Mayuresh
2011-05-11 6:32 ` Tomi Valkeinen
2011-05-12 6:40 ` Igor Grinberg
2011-05-12 7:16 ` Igor Grinberg
2011-05-12 8:38 ` Igor Grinberg
2011-05-12 8:47 ` Janorkar, Mayuresh
2011-05-12 11:20 ` Igor Grinberg
2011-05-12 11:47 ` Tomi Valkeinen
2011-05-12 14:36 ` Janorkar, Mayuresh
2011-05-12 14:47 ` Tomi Valkeinen
2011-05-12 14:50 ` Janorkar, Mayuresh
2011-05-12 14:59 ` Tomi Valkeinen
2011-05-16 8:53 ` Tomi Valkeinen
2011-05-16 11:13 ` Igor Grinberg
2011-05-17 11:49 ` Tomi Valkeinen
2011-05-17 11:56 ` Tomi Valkeinen
2011-05-17 12:28 ` Igor Grinberg
2011-05-17 13:16 ` Tomi Valkeinen
2011-05-16 11:26 ` Janorkar, Mayuresh
2011-05-17 11:44 ` Tomi Valkeinen
2011-05-09 7:36 ` [PATCH 5/6] OMAP: H4: " Tomi Valkeinen
2011-05-09 7:36 ` [PATCH 6/6] OMAP: Apollon: " Tomi Valkeinen
2011-05-09 17:01 ` [PATCH 0/6] OMAP: board file changes for DSS2 porting Tomi Valkeinen
2011-05-10 13:35 ` Tony Lindgren
2011-05-10 14:03 ` Tomi Valkeinen
2011-05-11 7:08 ` 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=1304926567-26814-1-git-send-email-tomi.valkeinen@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).