dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [PULL] topic/drm-fixes
Date: Thu, 07 Apr 2016 12:05:03 +0300	[thread overview]
Message-ID: <87mvp5x000.fsf@intel.com> (raw)


Hi Dave, some drm fixes I've picked up.

The qxl fix I've picked up quite some time ago, and unfortunately
neglected.

Then there's established timing fixes, of which particularly "drm/edid:
Fix parsing of EDID 1.4 Established Timings III descriptor" is quite
surprising. It looks like we've never got any of them right. I am not
sure what the full implications of this are. That combined with lack of
any details of real world bugs fixed made me decide against cc: stable.

BR,
Jani.

The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:

  Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)

are available in the git repository at:

  git://anongit.freedesktop.org/drm-intel tags/topic/drm-fixes-2016-04-07

for you to fetch changes up to 735b100f6d84b60da68e81e0bcb953d2021e0aa8:

  drm/edid: Fix DMT 1024x768@43Hz (interlaced) timings (2016-04-05 12:49:31 +0300)

----------------------------------------------------------------
John Keeping (1):
      drm/qxl: fix cursor position with non-zero hotspot

Paul Parsons (3):
      drm/edid: Fix EDID Established Timings I and II
      drm/edid: Fix parsing of EDID 1.4 Established Timings III descriptor
      drm/edid: Fix DMT 1024x768@43Hz (interlaced) timings

 drivers/gpu/drm/drm_edid.c        | 10 +++++-----
 drivers/gpu/drm/qxl/qxl_display.c | 13 +++++++++----
 drivers/gpu/drm/qxl/qxl_drv.h     |  2 ++
 3 files changed, 16 insertions(+), 9 deletions(-)

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-04-07  9:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07  9:05 Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-19 16:00 [PULL] topic/drm-fixes Jani Nikula
2015-11-11 11:41 Jani Nikula
2015-08-14 10:03 Jani Nikula
2015-07-23  6:53 Daniel Vetter
2015-07-16  6:44 Daniel Vetter
2015-07-15  8:52 Daniel Vetter
2015-07-15  9:16 ` Daniel Vetter
2015-07-03 23:07 Daniel Vetter
2015-05-27 11:37 Jani Nikula
2015-04-02  8:17 Jani Nikula

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=87mvp5x000.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).