From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Rob Clark <robdclark@gmail.com>
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH RFC 0/9] omapdrm/omapfb/omapdss split
Date: Thu, 10 Dec 2015 14:58:14 +0000 [thread overview]
Message-ID: <56699306.4070101@ti.com> (raw)
In-Reply-To: <CAF6AEGsCi_-YwQHYjfO_ao7Fg8QmQ=Gka1rG+OgkNqNaRsA5vw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
On 10/12/15 16:53, Rob Clark wrote:
> It would be nice to see omapdrm eventually using the panel framework,
> etc. But I think copy/paste to decouple omapdrm from omapfb/vout as
> the first step makes sense.
Yes, long term plans include getting rid of the omap specific
panel/encoder drivers. But I can't do that as long as omapfb/vout is
there, preventing any bigger refactorings.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-12-10 14:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 14:25 [PATCH RFC 0/9] omapdrm/omapfb/omapdss split Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 1/9] omapfb: allow compilation only if DRM_OMAP is disabled Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 3/9] omapdss: remove CONFIG_OMAP2_DSS_VENC from omapdss.h Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 4/9] omapfb/dss: change CONFIG_OMAP* to CONFIG_FB_OMAP* Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 5/9] omapfb/displays: change CONFIG_DISPLAY_* to CONFIG_FB_OMAP2_* Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 6/9] omapfb: take omapfb's prive omapdss into use Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 7/9] omapfb: move vrfb into omapfb Tomi Valkeinen
2015-12-13 19:13 ` Laurent Pinchart
2015-12-14 7:14 ` Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 8/9] drm/omap: move omapdss & displays under omapdrm Tomi Valkeinen
2015-12-13 19:08 ` Laurent Pinchart
2015-12-14 7:12 ` Tomi Valkeinen
2015-12-10 14:25 ` [PATCH RFC 9/9] drm/omap: make omapdrm select OMAP2_DSS Tomi Valkeinen
2015-12-10 14:53 ` [PATCH RFC 0/9] omapdrm/omapfb/omapdss split Rob Clark
2015-12-10 14:58 ` Tomi Valkeinen [this message]
2015-12-10 17:00 ` Emil Velikov
2015-12-10 17:15 ` Tomi Valkeinen
2015-12-11 6:26 ` Archit Taneja
2015-12-11 7:57 ` Tomi Valkeinen
2015-12-11 11:44 ` Archit Taneja
2015-12-16 15:52 ` Tomi Valkeinen
2015-12-16 22:11 ` Rob Clark
2015-12-17 0:22 ` Dave Airlie
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=56699306.4070101@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=robdclark@gmail.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).