All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Jackson <ajax@redhat.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/2] Automatic 6bpc dither for DisplayPort
Date: Tue, 25 Oct 2011 12:25:45 -0400	[thread overview]
Message-ID: <1319559945.2009.6.camel@synephrine> (raw)
In-Reply-To: <1318278815-31492-1-git-send-email-ajax@redhat.com>

On Mon, 2011-10-10 at 16:33 -0400, Adam Jackson wrote:
> This fixes a rather irritating limitation of active dp->foo converters.
> Many such (including all DP->VGA chips I can find on the market) come
> equipped with only 2 DP lanes, which clips your dotclock to 144MHz at
> 8bpc.  Of the standard DMT modes, that means you lose 1600x1200@60 and
> above.  Since these adaptors are marketed as supporting 1920x1200, we
> might as well make that work, otherwise it's the driver that comes
> out looking bad.

After the fix in drm-intel-next to fix the DP bandwidth math this series
is probably less useful, since 1920x1200 will in fact fit in 2x2.7G:

(193250 * 24 + 9) / 10 == 463800

But if you have a Really Very Nice CRT then it might still be desirable.
2048x1536 @ 60Hz GTF for example:

(266950 * 24 + 9) / 10 == 640680
(266950 * 18 + 9) / 10 == 480510

I can respin patch 2 if there's still interest, but it might be
difficult to find a monitor to test against.  Patch 1 is still valid
though.

- ajax

  parent reply	other threads:[~2011-10-25 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 20:33 [PATCH 0/2] Automatic 6bpc dither for DisplayPort Adam Jackson
2011-10-10 20:33 ` [PATCH 1/2] drm/i915: intel_choose_pipe_bpp_dither messages should be DRM_DEBUG_KMS Adam Jackson
2011-10-10 20:33 ` [PATCH 2/2] drm/i915/dp: Dither down to 6bpc if it makes the mode fit Adam Jackson
2011-10-25 16:25 ` Adam Jackson [this message]
2011-10-25 18:25   ` [PATCH 0/2] Automatic 6bpc dither for DisplayPort Keith Packard

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=1319559945.2009.6.camel@synephrine \
    --to=ajax@redhat.com \
    --cc=intel-gfx@lists.freedesktop.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.