From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Olivier Galibert <galibert@pobox.com>
Cc: Indan Zupancic <indan@nul.nu>, Dave Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, Len Brown <lenb@kernel.org>,
Alan Cox <alan@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH] ACPI/Intel: Rework Opregion support
Date: Tue, 15 Mar 2011 13:43:11 +0000 [thread overview]
Message-ID: <20110315134311.GA5892@srcf.ucam.org> (raw)
In-Reply-To: <20110315134059.GB33193@dspnet.fr>
On Tue, Mar 15, 2011 at 02:40:59PM +0100, Olivier Galibert wrote:
> On Tue, Mar 15, 2011 at 01:32:40PM +0000, Matthew Garrett wrote:
> > Opregion is one mechanism to provide VBT - it doesn't define it.
>
> Then let me repeat that I haven't seen anything in the VBT tables of
> the gma500-using netbook I have that didn't seem to be parsed
> correctly by the current gpu/drm/i915/intel_bios.c code and its
> friends. Have a look at it if you want.
gma600 *certainly* has a bunch of additional functionality. It may be
that this is code that can be split out in a reasonable manner, but
there's been sufficient fragility here that I think doing it at this
stage for the benefit of a driver in staging doesn't buy us a great
deal.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-03-15 13:43 UTC|newest]
Thread overview: 29+ 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 ` [Intel-gfx] [PATCH 1/2] ACPI/Intel: Rework Opregion support Jesse Barnes
2011-03-03 2:14 ` Len Brown
2011-03-14 17:59 ` [PATCH] " Chris Wilson
2011-03-15 1:18 ` Indan Zupancic
2011-03-15 1:52 ` Matthew Garrett
2011-03-15 13:30 ` [Intel-gfx] " Olivier Galibert
2011-03-15 13:32 ` Matthew Garrett
2011-03-15 13:40 ` Olivier Galibert
2011-03-15 13:43 ` Matthew Garrett [this message]
2011-03-15 8:37 ` Chris Wilson
2011-03-15 11:13 ` Indan Zupancic
2011-03-15 11:27 ` Peter Stuge
2011-03-15 11:46 ` Indan Zupancic
2011-03-15 11:46 ` Indan Zupancic
2011-03-15 16:06 ` Alex Deucher
2011-03-16 0:02 ` Indan Zupancic
2011-03-16 2:17 ` Alex Deucher
2011-03-16 6:26 ` Indan Zupancic
2011-03-16 14:11 ` Jerome Glisse
2011-03-16 3:46 ` Dave Airlie
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=20110315134311.GA5892@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=airlied@linux.ie \
--cc=alan@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=galibert@pobox.com \
--cc=indan@nul.nu \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@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.