From: Eugeni Dodonov <eugeni.dodonov@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Eugeni Dodonov <eugeni.dodonov@intel.com>
Subject: [PATCH 2/2] drm/i915: there is no pipe CxSR on ironlake
Date: Thu, 5 Jan 2012 09:34:29 -0200 [thread overview]
Message-ID: <1325763269-7245-2-git-send-email-eugeni.dodonov@intel.com> (raw)
In-Reply-To: <1325763269-7245-1-git-send-email-eugeni.dodonov@intel.com>
After checking the specs and discussing with Jesse, turns out CxSR is not
available on Ironlake and gen5, and its advertisement on the device
description is misleading.
Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eugeni Dodonov <eugeni.dodonov@intel.com>
---
drivers/gpu/drm/i915/i915_drv.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
index a1103fc..4795edd 100644
--- a/drivers/gpu/drm/i915/i915_drv.c
+++ b/drivers/gpu/drm/i915/i915_drv.c
@@ -198,7 +198,7 @@ static const struct intel_device_info intel_pineview_info = {
static const struct intel_device_info intel_ironlake_d_info = {
.gen = 5,
- .need_gfx_hws = 1, .has_pipe_cxsr = 1, .has_hotplug = 1,
+ .need_gfx_hws = 1, .has_hotplug = 1,
.has_bsd_ring = 1,
};
--
1.7.8
next prev parent reply other threads:[~2012-01-05 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 11:34 [PATCH 1/2] drm: give up on edid retries when i2c bus is not responding Eugeni Dodonov
2012-01-05 11:34 ` Eugeni Dodonov [this message]
2012-01-16 20:30 ` [PATCH 2/2] drm/i915: there is no pipe CxSR on ironlake Daniel Vetter
2012-01-05 14:43 ` [PATCH 1/2] drm: give up on edid retries when i2c bus is not responding Daniel Vetter
2012-01-05 15:37 ` Eugeni Dodonov
2012-01-05 15:50 ` Keith Packard
2012-01-16 20:33 ` [Intel-gfx] " Daniel Vetter
2012-01-20 20:06 ` Fwd: " Eugeni Dodonov
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=1325763269-7245-2-git-send-email-eugeni.dodonov@intel.com \
--to=eugeni.dodonov@intel.com \
--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 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.