From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Matthew Garrett <mjg@redhat.com>
Cc: linux-acpi@vger.kernel.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, alan@linux.intel.com
Subject: Re: [Intel-gfx] [PATCH 1/2] ACPI/Intel: Rework Opregion support
Date: Tue, 22 Feb 2011 12:18:40 -0800 [thread overview]
Message-ID: <20110222121840.32a6e782@jbarnes-desktop> (raw)
In-Reply-To: <1298404994-2907-1-git-send-email-mjg@redhat.com>
On Tue, 22 Feb 2011 15:03:13 -0500
Matthew Garrett <mjg@redhat.com> wrote:
> The Integrated Graphics Device opregion specification defines a mechanism
> for the OS and system firmware to collaborate on various graphics-related
> functionality. This is currently implemented in the i915 driver but isn't
> strictly limited to these devices. Move it to a more generic location and
> remove the i915 dependency, while simultaneously reworking i915 to make
> use of the new driver.
Nice, having it split out makes sense. And I like the formalized
interface between the driver and the OpRegion features.
Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-02-22 20:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 20:03 [PATCH 1/2] ACPI/Intel: Rework Opregion support Matthew Garrett
2011-02-22 20:03 ` [PATCH 2/2] staging: Use generic IGD opregion code for gma500 Matthew Garrett
2011-02-22 21:15 ` Alan Cox
2011-03-03 2:14 ` Len Brown
2011-03-03 2:16 ` Len Brown
2011-03-03 11:43 ` Alan Cox
2011-03-03 11:43 ` Alan Cox
2011-03-03 13:07 ` Matthew Garrett
2011-03-03 12:52 ` Alan Cox
2011-02-22 20:18 ` Jesse Barnes [this message]
2011-03-03 2:14 ` [PATCH 1/2] ACPI/Intel: Rework Opregion support Len Brown
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=20110222121840.32a6e782@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=alan@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.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