dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rob Clark <rob.clark@linaro.org>
Cc: Greg KH <greg@kroah.com>,
	patches@linaro.org, dri-devel@lists.freedesktop.org,
	Rob Clark <rob@ti.com>
Subject: Re: [PATCH 1/3] drm/omap: drm API update: addfb2
Date: Wed, 21 Dec 2011 01:30:42 +0200	[thread overview]
Message-ID: <20111220233042.GT3692@intel.com> (raw)
In-Reply-To: <1324421933-18170-2-git-send-email-rob.clark@linaro.org>

On Tue, Dec 20, 2011 at 04:58:51PM -0600, Rob Clark wrote:
> +static const struct format formats[] = {
> +	/* 16bpp [A]RGB: */
> +	{ OMAP_DSS_COLOR_RGB16,       DRM_FORMAT_RGB565,   {{2, 1}}, false }, /* RGB16-565 */
> +	{ OMAP_DSS_COLOR_RGB12U,      DRM_FORMAT_RGBX4444, {{2, 1}}, false }, /* RGB12x-4444 */
> +	{ OMAP_DSS_COLOR_RGBX16,      DRM_FORMAT_XRGB4444, {{2, 1}}, false }, /* xRGB12-4444 */
> +	{ OMAP_DSS_COLOR_RGBA16,      DRM_FORMAT_RGBA4444, {{2, 1}}, false }, /* RGBA12-4444 */
> +	{ OMAP_DSS_COLOR_ARGB16,      DRM_FORMAT_ABGR4444, {{2, 1}}, false }, /* ARGB16-4444 */
                                                 ^^^^^^^^

Should be ARGB4444, no?

BTW I took a quick gander at the format specifications in the OMAP4 TRM
and it has a funny bug.

xRGB16-1555 and ARGB16-1555 are listed like this:

31       ...          0
U  R1 G1 B1 U  R0 B0 G0
A1 R1 G1 B1 A0 R0 B0 G0

So every second pixel has B and G swapped around. That would be some
interesting hardware to use :D

It's possible the TRM I had lying around was an old one though and the
issue is fixed in later revisions.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2011-12-20 23:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 22:58 [PATCH 0/3] drm/omap: updates for addfb2 and plane support Rob Clark
2011-12-20 22:58 ` [PATCH 1/3] drm/omap: drm API update: addfb2 Rob Clark
2011-12-20 23:30   ` Ville Syrjälä [this message]
2011-12-20 23:58     ` Rob Clark
2011-12-21  0:34       ` Ville Syrjälä
2012-01-02 16:43     ` Rob Clark
2011-12-20 22:58 ` [PATCH 2/3] drm/omap: add drm_plane support Rob Clark
2011-12-20 22:58 ` [PATCH 3/3] drm/omap: multiplanar and YUV support Rob Clark
  -- strict thread matches above, loose matches on Subject: below --
2012-01-05 21:22 [PATCH 0/3] drm/omap: updates for addfb2 and plane support Rob Clark
2012-01-05 21:22 ` [PATCH 1/3] drm/omap: drm API update: addfb2 Rob Clark
2011-12-15  6:16 [PATCH 0/3] drm/omap: updates for addfb2 and plane support Rob Clark
2011-12-15  6:16 ` [PATCH 1/3] drm/omap: drm API update: addfb2 Rob Clark

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=20111220233042.GT3692@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=greg@kroah.com \
    --cc=patches@linaro.org \
    --cc=rob.clark@linaro.org \
    --cc=rob@ti.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