From: ville.syrjala@linux.intel.com
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: [PATCH 0/3] x86: Intel gen2 graphics stolen memory quirks
Date: Wed, 5 Feb 2014 21:28:57 +0200 [thread overview]
Message-ID: <1391628540-23072-1-git-send-email-ville.syrjala@linux.intel.com> (raw)
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Ingo asked me to post the x86 bits as a standalone series. So here it is.
So the series adds the Intel gen2 graphics stolen memory reservation quirks
to arch/x86. These are not unlike the quirks we have for later gens, except
it's a bit more work to dig out the correct range to reserve on gen2.
This has been tested on 830, 845 and 855 chipsets. 865 still eludes me
unfortunately.
Ville Syrjälä (3):
x86: Add vfunc for Intel graphics stolen memory base address
x86: Add Intel graphics stolen memory quirk for gen2 platforms
x86: Print the Intel graphcis stolen memory range
arch/x86/kernel/early-quirks.c | 211 +++++++++++++++++++++++++++++++++++------
include/drm/i915_drm.h | 20 ++++
2 files changed, 202 insertions(+), 29 deletions(-)
--
1.8.3.2
next reply other threads:[~2014-02-05 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 19:28 ville.syrjala [this message]
2014-02-05 19:28 ` [PATCH 1/3] x86: Add vfunc for Intel graphics stolen memory base address ville.syrjala
2014-02-10 13:30 ` [tip:x86/platform] x86/gpu: " tip-bot for Ville Syrjälä
2014-02-05 19:28 ` [PATCH v3 2/3] x86: Add Intel graphics stolen memory quirk for gen2 platforms ville.syrjala
2014-02-10 13:30 ` [tip:x86/platform] x86/gpu: " tip-bot for Ville Syrjälä
2014-02-05 19:29 ` [PATCH 3/3] x86: Print the Intel graphics stolen memory range ville.syrjala
2014-02-10 13:31 ` [tip:x86/platform] x86/gpu: " tip-bot for Ville Syrjälä
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=1391628540-23072-1-git-send-email-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®