dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Paulo Zanoni <przanoni@gmail.com>
To: intel-gfx@lists.freedesktop.org
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>, dri-devel@lists.freedesktop.org
Subject: [PATCH 0/5] module_reload fixes
Date: Thu, 26 Sep 2013 20:05:57 -0300	[thread overview]
Message-ID: <1380236762-1698-1-git-send-email-przanoni@gmail.com> (raw)

From: Paulo Zanoni <paulo.r.zanoni@intel.com>

Hi

These patches allow us to run the "module_reload" script from intel-gpu-tools on
Haswell. The script basically just removes i915.ko and loads it again.

There's a memory corruption fix and also the fix for fd.o #67813.  Notice that
the first patch fixes the case where we boot eDP+something, while patches 3-5
fix the case where we boot eDP-only.

I couldn't find MAINTAINERS entries for vt.c or fbcon.c, but I heard the
dri-devel list is a good place for such patches. Please tell me if I missed some
mailing list.

Cheers,
Paulo


Paulo Zanoni (5):
  drm/i915: redisable VGA when we disable the power well
  drm/i915: destroy connector sysfs files earlier
  tty/vt: add con_bind and con_unbind functions
  console/fbcon: implement con_bind and con_unbind
  drm/i915: put/get the power well at the FB bind/unbind functions

 drivers/gpu/drm/i915/intel_crt.c     |  1 -
 drivers/gpu/drm/i915/intel_display.c |  7 ++++++-
 drivers/gpu/drm/i915/intel_dp.c      |  1 -
 drivers/gpu/drm/i915/intel_drv.h     |  2 ++
 drivers/gpu/drm/i915/intel_dsi.c     |  1 -
 drivers/gpu/drm/i915/intel_dvo.c     |  1 -
 drivers/gpu/drm/i915/intel_fb.c      | 23 +++++++++++++++++++++++
 drivers/gpu/drm/i915/intel_hdmi.c    |  1 -
 drivers/gpu/drm/i915/intel_lvds.c    |  1 -
 drivers/gpu/drm/i915/intel_pm.c      |  6 ++++++
 drivers/gpu/drm/i915/intel_sdvo.c    |  7 +++++--
 drivers/gpu/drm/i915/intel_tv.c      |  1 -
 drivers/tty/vt/vt.c                  |  6 ++++++
 drivers/video/console/fbcon.c        | 26 ++++++++++++++++++++++++++
 include/linux/console.h              |  2 ++
 include/linux/fb.h                   |  4 ++++
 16 files changed, 80 insertions(+), 10 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2013-09-26 23:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 23:05 Paulo Zanoni [this message]
2013-09-26 23:05 ` [PATCH 1/5] drm/i915: redisable VGA when we disable the power well Paulo Zanoni
2013-10-01 13:47   ` Ville Syrjälä
2013-10-01 18:18     ` Ville Syrjälä
2013-09-26 23:05 ` [PATCH 2/5] drm/i915: destroy connector sysfs files earlier Paulo Zanoni
2013-09-30 21:10   ` Daniel Vetter
2013-09-26 23:06 ` [PATCH 3/5] tty/vt: add con_bind and con_unbind functions Paulo Zanoni
2013-10-01 13:50   ` Ville Syrjälä
2013-10-08 21:12     ` Paulo Zanoni
2013-10-09  8:10       ` Ville Syrjälä
2013-09-26 23:06 ` [PATCH 4/5] console/fbcon: implement con_bind and con_unbind Paulo Zanoni
2013-09-26 23:06 ` [PATCH 5/5] drm/i915: put/get the power well at the FB bind/unbind functions Paulo Zanoni

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=1380236762-1698-1-git-send-email-przanoni@gmail.com \
    --to=przanoni@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@intel.com \
    /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).