From: Damien Lespiau <damien.lespiau@intel.com>
To: Ben Widawsky <benjamin.widawsky@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Supporting fused display configurations
Date: Thu, 5 Dec 2013 18:25:42 +0000 [thread overview]
Message-ID: <20131205182542.GC30349@strange.icx.intel.com> (raw)
In-Reply-To: <20131205181920.GA13831@intel.com>
On Thu, Dec 05, 2013 at 10:19:20AM -0800, Ben Widawsky wrote:
> On Thu, Dec 05, 2013 at 02:21:08PM +0000, Damien Lespiau wrote:
> > On Thu, Dec 05, 2013 at 02:09:33PM +0000, Chris Wilson wrote:
> > > Patches look fine. Just relying on fuse registers being correct is like
> > > relying on vbt being correct, fraught with anxiety.
> >
> > Well, I believe those bits are directly reflecting the fuses/straps
> > programmed (the sames that will actually disable hw), so it should be
> > better than VBT. On the other hand, that's the reason why I only check
> > from IVB on and not from ILK to not take unecessary risks on platforms
> > with no known fused config.
>
> I'm surprised by this. We had a semi-lengthy mail on the matter
> internally, and ISTR there was no way to actually make this work for all
> cases. I guess I need to go re-read that.
Oh? I must have missed it or it wasn't broadcasted. Mind digging out the
thread again?
> > In any case, if someone with such a device could test the series :)
>
> IMHO the patches can't be merged until it can be verified. If you want
> to call that a nak-until-then on patch 6, do. I'd much rather have a
> dynamic solution like this though.
Yes, of course! (I'd like to have the writable info in any case).
--
Damien
prev parent reply other threads:[~2013-12-05 18:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 13:56 Supporting fused display configurations Damien Lespiau
2013-12-05 13:56 ` [PATCH 1/7] drm/i915: Make the intel_device_info structure kept in dev_priv writable Damien Lespiau
2013-12-05 13:56 ` [PATCH 2/7] drm/i915: Move num_plane to the intel_device_info structure Damien Lespiau
2013-12-05 13:56 ` [PATCH 3/7] drm/i915: Consolidate FUSE_STRAP in one set of defines Damien Lespiau
2013-12-05 13:56 ` [PATCH 4/7] drm/i915: Disable display when fused off Damien Lespiau
2013-12-05 14:11 ` [PATCH 4/7 v2] " Damien Lespiau
2013-12-05 13:56 ` [PATCH 5/7] drm/i915: Support fused off pipe C configurations Damien Lespiau
2013-12-05 14:13 ` [PATCH 5/7 v2] " Damien Lespiau
2013-12-05 13:56 ` [PATCH 6/7] drm/i915: Remove the Quanta special case Damien Lespiau
2013-12-05 13:56 ` [PATCH 7/7] drm/i915: Use I915_MAX_PIPES in the pipe/plane_to_crtc_mapping definitions Damien Lespiau
2013-12-05 14:03 ` Supporting fused display configurations Damien Lespiau
2013-12-05 14:09 ` Chris Wilson
2013-12-05 14:21 ` Damien Lespiau
2013-12-05 18:19 ` Ben Widawsky
2013-12-05 18:25 ` Damien Lespiau [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=20131205182542.GC30349@strange.icx.intel.com \
--to=damien.lespiau@intel.com \
--cc=benjamin.widawsky@intel.com \
--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.