From: Lyude <cpaul@redhat.com>
To: Daniel Vetter <daniel@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: [RESEND] [PATCH 0/4] Important MST fixes for 4.6
Date: Thu, 12 May 2016 10:56:57 -0400 [thread overview]
Message-ID: <1463065021-18280-1-git-send-email-cpaul@redhat.com> (raw)
Unfortunately we've never really made use of creating/destroying connectors on
the fly like we have with MST, so 4.6 ended up showing a lot of various bugs
with hotplugging MST displays, booting with MST displays, etc. Most of these
bugs are very likely to panic the kernel, and a couple of them end up even
doing out of bounds memory accesses causing all sorts of other issues. This
being said; we currently have a much better solution that makes a few of these
patches unneccessary: dave's connector reference counting patch series[1]. For
the time being however, this is the most minimal patchset I could come up with
for 4.6 to work around all of these issues.
[1]: b164d31f50b2923a7a92c2a40cb46973a6ba8c36 in drm-next
Lyude (4):
drm/i915/fbdev: Fix num_connector references in
intel_fb_initial_config()
drm/fb_helper: Fix references to dev->mode_config.num_connector
drm/i915: Discard previous atomic state on resume if connectors change
drm/atomic: Verify connector->funcs != NULL when clearing states
drivers/gpu/drm/drm_atomic.c | 3 ++-
drivers/gpu/drm/drm_fb_helper.c | 4 ++--
drivers/gpu/drm/i915/intel_display.c | 12 ++++++++++++
drivers/gpu/drm/i915/intel_fbdev.c | 6 +++---
4 files changed, 19 insertions(+), 6 deletions(-)
This hasn't been sent to stable@vger.kernel.org yet, just sending this to
intel-gfx for review beforehand.
--
2.5.5
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-05-12 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 14:56 Lyude [this message]
2016-05-12 14:56 ` [PATCH 1/4] drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config() Lyude
2016-05-12 14:56 ` [PATCH 2/4] drm/fb_helper: Fix references to dev->mode_config.num_connector Lyude
2016-05-12 21:47 ` [PATCH v2 3/4] drm/i915: Discard previous atomic state on resume if connectors change Lyude
2016-05-17 12:01 ` Daniel Vetter
2016-05-12 14:57 ` [PATCH " Lyude
2016-05-12 14:57 ` [PATCH 4/4] drm/atomic: Verify connector->funcs != NULL when clearing states Lyude
2016-05-12 15:04 ` Lyude
2016-05-17 12:00 ` Daniel Vetter
2016-05-12 16:48 ` ✗ Ro.CI.BAT: failure for Important MST fixes for 4.6 (rev2) Patchwork
2016-05-12 22:25 ` ✗ Ro.CI.BAT: failure for Important MST fixes for 4.6 (rev3) Patchwork
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=1463065021-18280-1-git-send-email-cpaul@redhat.com \
--to=cpaul@redhat.com \
--cc=daniel@ffwll.ch \
--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).