From: Jonathan Nieder <jrnieder@gmail.com>
To: stable@vger.kernel.org
Cc: Maik Zumstrull <maik@zumstrull.net>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [3.2.y] drm/i915: add Ivy Bridge GT2 Server entries
Date: Mon, 1 Oct 2012 03:24:32 -0700 [thread overview]
Message-ID: <20121001102432.GA8959@elie.Belkin> (raw)
In-Reply-To: <CAO=zWD+aBgNN3bL8Frvi1pgDhkZKfWUO3B8xt8J3GMha+fmxAg@mail.gmail.com>
Hi Ben,
Please consider
cc22a938fc1d drm/i915: add Ivy Bridge GT2 Server entries, 2012-03-29
for application to the 3.2.y tree. It adds a PCI id to the i915
driver, making kms work. It was applied during the 3.4-rc2 cycle, so
newer stable kernels don't need it.
Maik Zumstrull tried it[1] on top of 3.2.30 and found it to work ok
(thanks!).
Note that pre-2.4.34 versions of libdrm don't cope well with that
card, with or without this patch:
- without this patch, modern X errors out instead of starting,
because the intel driver requires kms. (In a hypothetical better
world, userspace would know to fall back to vesa or something.)
- with this patch and with libdrm patch 2.4.34~22 (intel: add Ivy
Bridge GT2 server variant, 2012-03-29), X should work great
- with this patch, without libdrm 2.4.34~22, but with libdrm patch
2.4.38~10 (intel: Bail gracefully if we encounter an unknown Intel
device, 2012-07-25) applied, X should error out instead of starting
- with this patch, and with libdrm lacking 2.4.34~22 and 2.4.38~10,
X freezes at startup.
"No regressions" means you probably shouldn't take this patch without
a safety to work around the old X userspace, unless you can shout
enough in release notes to get people to apply 2.4.38~10 to libdrm and
maintain sanity. ;)
Hmm?
Jonathan
[1] http://bugs.debian.org/684767
next parent reply other threads:[~2012-10-01 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120729113605.5102.7805.reportbug@antares.zumstrull.net>
[not found] ` <20120929235234.GA13098@elie.Belkin>
[not found] ` <CAO=zWD+aBgNN3bL8Frvi1pgDhkZKfWUO3B8xt8J3GMha+fmxAg@mail.gmail.com>
2012-10-01 10:24 ` Jonathan Nieder [this message]
2012-10-07 14:01 ` [3.2.y] drm/i915: add Ivy Bridge GT2 Server entries Ben Hutchings
2012-10-07 14:11 ` Chris Wilson
2012-10-07 15:29 ` Ben Hutchings
2012-10-07 17:26 ` [Intel-gfx] " Julien Cristau
2012-10-07 17:35 ` Maik Zumstrull
2012-10-07 17:44 ` Jonathan Nieder
2012-10-07 17:53 ` Maik Zumstrull
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=20121001102432.GA8959@elie.Belkin \
--to=jrnieder@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maik@zumstrull.net \
--cc=stable@vger.kernel.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.