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 10:32:16 +0100 [thread overview]
Message-ID: <e0d58a$grmtf@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1305136090-5858-1-git-send-email-jbarnes@virtuousgeek.org>
On Wed, 11 May 2011 10:48:01 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> A couple of bug fixes, and some patches to support deep color on Intel
> chipsets.
My main concern with extended fb->depth support is in validation that the
crtc+encoder supports the requested fb, and that we have sufficient
logging of the bpc (inc fb->depth/fb->bpp) changes during modeswitch.
There are some restrictions that you add in mode_set() that need to be
raised to intel_framebuffer_init() so that the error is detected early.
But we should also be checking the requested fb->depth is valid during
preparation, and error early.
>From the DDX, we declare the fb depth before we know what's attached, and
once established that depth is permanent (if only due to the complexity of
invalidating all client cached state for the old depth). So we're stuck
with the user getting it right. In a composite-only, pixmap-per-crtc model
changing depths on the fly is possible and clients can choose to take
advantage of the deep-color support, or not.
So here goes -depth 30...
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-24 9:32 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 ` Chris Wilson [this message]
2011-06-24 10:24 ` Deep color support and bug fixes Chris Wilson
2011-06-24 12:46 ` Chris Wilson
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='e0d58a$grmtf@orsmga002.jf.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.