linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] DRM: add i.MX IPUv3 base driver
Date: Fri, 24 Aug 2012 19:31:19 +0100	[thread overview]
Message-ID: <20120824183119.GD18957@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAKGA1bkjJXK8bUxLxRYz_4Rj9YW0mJxBMyg7ir+Hfo+s6Lza0w@mail.gmail.com>

On Fri, Aug 24, 2012 at 01:00:13PM -0500, Matt Sealey wrote:
> Nobody wants to write
> the same driver 5 times, and while the Silicon Image controllers are
> wonderfully generic with a common API ("TPI") and there could be a
> generic MFD solution with shim drivers on top for DRM, nobody else's
> are quite as nice.

I got here and immediately thought "oh god not more layers to DRM".
DRM does _not_ need any more bloody layers on top of the existing
layers.  It needs a library of helper functions to provide common
functionality so that folk don't have to write the same bloody stuff
time and time again.

A library of helpers, not a shim layer to convert it to something else.

  reply	other threads:[~2012-08-24 18:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1596192785.2810155.1345817566620.JavaMail.root@advansee.com>
2012-08-24 14:52 ` [PATCH 4/5] DRM: add i.MX IPUv3 base driver Benoît Thébaudeau
2012-08-24 15:58   ` Dirk Behme
2012-08-27  8:30     ` Sascha Hauer
2012-08-24 17:38   ` Robert Schwebel
2012-08-24 18:00   ` Matt Sealey
2012-08-24 18:31     ` Russell King - ARM Linux [this message]
2012-06-14 13:43 [PATCH, RFC] i.MX DRM support Sascha Hauer
2012-06-14 13:43 ` [PATCH 4/5] DRM: add i.MX IPUv3 base driver Sascha Hauer
2012-06-22  6:04   ` Shawn Guo

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=20120824183119.GD18957@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).