All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Jackson <ajax@redhat.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Small series to enable OpRegion->VBT
Date: Tue, 24 Aug 2010 11:42:40 -0400	[thread overview]
Message-ID: <1282664560.17843.37883.camel@atropine> (raw)
In-Reply-To: <89kc63$hrta0i@fmsmga002.fm.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1369 bytes --]

On Tue, 2010-08-24 at 15:37 +0100, Chris Wilson wrote:
> On Tue, 24 Aug 2010 10:22:48 -0400, Adam Jackson <ajax@redhat.com> 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.
> 
> 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

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2010-08-24 15:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24  8:42 Small series to enable OpRegion->VBT Chris Wilson
2010-08-24  8:43 ` [PATCH 1/4] drm/i915: Allocate the PCI resource for the MCHBAR Chris Wilson
2010-08-24 19:25   ` Jesse Barnes
2010-08-24  8:43 ` [PATCH 2/4] drm/i915: Rename i915_opregion.c to intel_opregion.c Chris Wilson
2010-08-24  8:43 ` [PATCH 3/4] drm/i915: Use the VBT from OpRegion when available (v3) Chris Wilson
2010-08-24  8:43 ` [PATCH 4/4] drm/i915: Addin-offset is an unreliable indicator of LVDS presence (v2) Chris Wilson
2010-08-24 14:22 ` Small series to enable OpRegion->VBT Adam Jackson
2010-08-24 14:37   ` Chris Wilson
2010-08-24 15:42     ` Adam Jackson [this message]

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=1282664560.17843.37883.camel@atropine \
    --to=ajax@redhat.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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.