From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>, intel-gfx@lists.freedesktop.org
Subject: Re: Deep color support and bug fixes
Date: Fri, 24 Jun 2011 13:46:41 +0100 [thread overview]
Message-ID: <f80fcd$lbv6c@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <e0d58a$gs691@orsmga002.jf.intel.com>
On Fri, 24 Jun 2011 11:24:08 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Fri, 24 Jun 2011 10:32:16 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > So here goes -depth 30...
>
> So other than a couple of rendering paths where we write 8bpc data into
> the depth-30 fb (go flash, go!), X looks good.
Looking at the xtrace and what the xserver/ddx is doing, it appears that
flash is b0rked. Quel surprise.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2011-06-24 12:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 17:48 Deep color support and bug fixes Jesse Barnes
2011-05-11 17:48 ` [PATCH 1/9] drm: add bit depth parsing Jesse Barnes
2011-05-11 17:48 ` [PATCH 2/9] drm: parse color format support for digital displays Jesse Barnes
2011-05-11 17:48 ` [PATCH 3/9] drm/i915: don't set SDVO color range on ILK+ Jesse Barnes
2011-06-24 5:50 ` Keith Packard
2011-05-11 17:48 ` [PATCH 4/9] drm/i915: don't set transcoder bpc on CougarPoint Jesse Barnes
2011-06-23 21:16 ` Keith Packard
2011-05-11 17:48 ` [PATCH 5/9] drm/i915: set bpc for DP transcoder Jesse Barnes
2011-05-11 17:48 ` [PATCH 6/9] drm/i915: split out Ironlake pipe bpp picking code Jesse Barnes
2011-06-24 9:58 ` Chris Wilson
2011-05-11 17:48 ` [PATCH 7/9] drm/i915: split out plane update code Jesse Barnes
2011-05-11 17:48 ` [PATCH 8/9] drm/i915: use pipe bpp in DP link bandwidth calculations Jesse Barnes
2011-05-11 17:48 ` [PATCH 9/9] drm/i915: use pipe bpp when setting HDMI bpc Jesse Barnes
2011-06-24 9:32 ` Deep color support and bug fixes Chris Wilson
2011-06-24 10:24 ` Chris Wilson
2011-06-24 12:46 ` Chris Wilson [this message]
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='f80fcd$lbv6c@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.