From: Adam Jackson <ajax@redhat.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: refuse to load on gen6+ without kms
Date: Mon, 26 Mar 2012 16:06:10 -0400 [thread overview]
Message-ID: <1332792370.20129.8.camel@atropine> (raw)
In-Reply-To: <1332790398-5837-1-git-send-email-daniel.vetter@ffwll.ch>
[-- Attachment #1.1: Type: text/plain, Size: 687 bytes --]
On Mon, 2012-03-26 at 21:33 +0200, Daniel Vetter wrote:
> As a first step refuse to load without kms on chips where userspace
> never supported ums. Now upstream hasn't supported ums on ilk, ever.
> But RHEL had the great idea to backport the kms support to their ums
> driver.
In RHEL5, yes. Personally I'm okay with saying those people get to run
RHEL5 kernels too, but Linus might have stronger opinions I guess.
That said we really don't use kernel support for this. Certainly
there's no acceleration on ILK. The corresponding kernel patch appears
to do nothing more than add the PCI IDs to the AGP driver, and add
IS_IRONLAKE() to I915_NEED_GFX_HWS().
- ajax
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2012-03-26 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 19:33 [PATCH] drm/i915: refuse to load on gen6+ without kms Daniel Vetter
2012-03-26 19:44 ` Chris Wilson
2012-03-26 19:50 ` Daniel Vetter
2012-03-26 21:21 ` Chris Wilson
2012-03-26 20:06 ` Adam Jackson [this message]
2012-03-26 20:37 ` [PATCH] drm/i915: disallow gem init ioctl on ilk Daniel Vetter
2012-03-26 20:43 ` Adam Jackson
2012-03-31 10:05 ` Daniel Vetter
2012-03-26 21:16 ` Chris Wilson
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=1332792370.20129.8.camel@atropine \
--to=ajax@redhat.com \
--cc=daniel.vetter@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).