From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Jackson Subject: Re: Small series to enable OpRegion->VBT Date: Tue, 24 Aug 2010 11:42:40 -0400 Message-ID: <1282664560.17843.37883.camel@atropine> References: <1282639383-26988-1-git-send-email-chris@chris-wilson.co.uk> <1282659768.17843.37718.camel@atropine> <89kc63$hrta0i@fmsmga002.fm.intel.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0191984727==" Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by gabe.freedesktop.org (Postfix) with ESMTP id 7EA209E733 for ; Tue, 24 Aug 2010 08:42:48 -0700 (PDT) In-Reply-To: <89kc63$hrta0i@fmsmga002.fm.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Chris Wilson Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org --===============0191984727== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-DBxpuxBexFKtygMII/TW" --=-DBxpuxBexFKtygMII/TW Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2010-08-24 at 15:37 +0100, Chris Wilson wrote: > On Tue, 24 Aug 2010 10:22:48 -0400, Adam Jackson wrote: > > I'd be a little more comfortable with this series if we tried to find > > VBT in VBIOS first. The way around you have it in patch 3 we'll likely > > be changing behaviour on existing machines, since we've not been paying > > any attention to what OpRegion's VBT contains before now. I mean, I'm > > not going to insist on it, but I'll reserve the right to say I told you > > so. >=20 > That would be the conservative approach. The docs are adamant that > OpRegion should be used in preference to any legacy approach. But nobody > reads those docs, at least not whilst writing the BIOS or during review. If only there were some kind of firmware verification kit so vendors would be able to test that they're not violating our assumptions. http://linuxfirmwarekit.org/ Wonder whatever happened to that? > One of the goals here is to solve the mystery of what happens to the VBT > on docking and whether new devices appear via the OpRegion, through the > ROM or never. If you do have one of the affected HP systems, can you at > try the patch and grab the /sys/kernel/debug/dri/0/i915_opregion before > and after docking? I have a few Lenovae that update VBT on dock, yeah, I'll give it a shot. - ajax --=-DBxpuxBexFKtygMII/TW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAkxz6HAACgkQW4otUKDs0NOvbgCgkKAYGKQCCDTWSBcKdtqk2f4q C1wAn1LZwNn3X4dqlQuTqEK/g0YQjdQ2 =uBsr -----END PGP SIGNATURE----- --=-DBxpuxBexFKtygMII/TW-- --===============0191984727== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============0191984727==--