public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH arm: initial TI-Nspire support]
Date: Tue, 9 Apr 2013 14:51:20 +0100	[thread overview]
Message-ID: <20130409135120.GC14496@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1365508916.24306.17.camel@hornet>

On Tue, Apr 09, 2013 at 01:01:56PM +0100, Pawel Moll wrote:
> So I have PL111 code almost working here, however today it depends on
> not-yet-upstream (to my knowledge) generic/common panel/display
> framework. If I'm not disturbed again I may get something done this
> week, hopefully removing the dependency.
> 
> There's also some work going on on a DRM driver for PL111, but I can't
> promise any dates.
> 
> As to PL110 I have no idea how different is it from the PL111, but
> nothing is happening about it anyway.

If you're doing PL111, then you might as well do PL110, because the two
are basically the same.  But note that all PL111's aren't equal.  Some
are closer to PL110 than the current PL111, so if you want to support
all PL111s, you also need to have the support in place for PL110.

Also note that the way the bits are assigned in the frame buffer varies
between platforms, and most certainly the TRMs documentation of colour
bitfield layouts can _not_ be relied upon.

I have considerable knowledge in this area, but as seems to be the norm
now, no one cares about that.  I'll go back to twiddling my thumbs now,
waiting for the next email to arrive.  Or maybe I'll go down to the
shops and wander around down there.  Or something.

  parent reply	other threads:[~2013-04-09 13:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  9:01 [RFC PATCH arm: initial TI-Nspire support] Daniel Tang
2013-04-04 11:12 ` Arnd Bergmann
2013-04-06  0:26   ` Daniel Tang
2013-04-06 11:51     ` Arnd Bergmann
2013-04-06 12:00       ` Daniel Tang
2013-04-06 13:24         ` Arnd Bergmann
2013-04-07  0:06           ` Daniel Tang
2013-04-07  3:56             ` Daniel Tang
2013-04-07 21:23               ` Arnd Bergmann
2013-04-08 11:33                 ` Daniel Tang
2013-04-08 19:16                   ` Fabian Vogt
2013-04-08 19:38                     ` Arnd Bergmann
2013-04-08 20:06                       ` Fabian Vogt
2013-04-08 21:29                         ` Arnd Bergmann
2013-04-09  5:59                     ` Daniel Tang
2013-04-09 11:23                 ` Linus Walleij
2013-04-09 12:01                   ` Pawel Moll
2013-04-09 12:05                     ` Linus Walleij
2013-04-09 13:51                     ` Russell King - ARM Linux [this message]
2013-04-07 14:32             ` Arnd Bergmann
2013-04-09 11:14 ` Linus Walleij
2013-04-09 11:39   ` Daniel Tang
2013-04-09 11:58     ` Linus Walleij

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=20130409135120.GC14496@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