From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [Intel-gfx] [PATCH] ACPI/Intel: Rework Opregion support Date: Tue, 15 Mar 2011 13:32:40 +0000 Message-ID: <20110315133240.GA5471@srcf.ucam.org> References: <1298404994-2907-1-git-send-email-mjg@redhat.com> <1300125566-29648-1-git-send-email-chris@chris-wilson.co.uk> <20110315015226.GA26454@srcf.ucam.org> <20110315133055.GA33193@dspnet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20110315133055.GA33193@dspnet.fr> Sender: linux-kernel-owner@vger.kernel.org To: Olivier Galibert Cc: Indan Zupancic , Dave Airlie , intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Len Brown , Alan Cox List-Id: intel-gfx@lists.freedesktop.org On Tue, Mar 15, 2011 at 02:30:55PM +0100, Olivier Galibert wrote: > On Tue, Mar 15, 2011 at 01:52:26AM +0000, Matthew Garrett wrote: > > Now that we've got multiple consumers it's probably not helpful to move > > the (potentially chip-specific) VBT handling to general code. We've got > > zero documentation on how GMA500 handles VBT, and not a great deal more > > for i915. > > I'm not sure what you mean by "handles". If you mean find it, the > gma500 driver code reads a 32-bit pointer to the opregion at offset > 0xfc in the pci configuration space. If you mean parse it, I haven't > seen anything that looked different to what the current kernel code > parses. Opregion is one mechanism to provide VBT - it doesn't define it. -- Matthew Garrett | mjg59@srcf.ucam.org