| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20110315133240.GA5471@srcf.ucam.org> Date: Tue, 15 Mar 2011 13:32:40 +0000 From: Matthew Garrett <mjg59@...f.ucam.org> To: Olivier Galibert <galibert@...ox.com> Cc: Indan Zupancic <indan@....nu>, Dave Airlie <airlied@...ux.ie>, intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org, Len Brown <lenb@...nel.org>, Alan Cox <alan@...ux.intel.com> Subject: Re: [Intel-gfx] [PATCH] ACPI/Intel: Rework Opregion support 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@...f.ucam.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists