From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Daniel Drake" <drake@endlessm.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Linux Upstreaming Team <linux@endlessm.com>,
intel-gfx@lists.freedesktop.org, Chris Chiu <chiu@endlessm.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] i915 4.9 regression: DP AUX CH sanitization no longer working on Asus desktops
Date: Fri, 26 May 2017 14:26:04 +0300 [thread overview]
Message-ID: <878tljn9kj.fsf@intel.com> (raw)
In-Reply-To: <CAD8Lp47Kbf76KDGz3KoDA8RAY3kdVqGVHcfQMuUVSwLF6qfi0Q@mail.gmail.com>
On Wed, 24 May 2017, Daniel Drake <drake@endlessm.com> wrote:
> On Fri, May 5, 2017 at 4:29 AM, Ville Syrjälä
> <ville.syrjala@linux.intel.com> wrote:
>> On Thu, May 04, 2017 at 02:52:09PM -0600, Daniel Drake wrote:
>>> On Thu, May 4, 2017 at 2:37 PM, Ville Syrjälä
>>> <ville.syrjala@linux.intel.com> wrote:
>>> > Please check if commit bb1d132935c2 ("drm/i915/vbt: split out defaults
>>> > that are set when there is no VBT") fixes things for you.
>>>
>>> I think this is not going to help. This would only make a difference
>>> when there is no VBT at all at which point we would see this message
>>> in the logs:
>>>
>>> DRM_INFO("Failed to find VBIOS tables (VBT)\n");
>>
>> No, the patch will in fact make a difference only when there is a VBT.
>
> We confirmed the mentioned patch fixes the issue. Apologies for
> doubting you :)
Thanks for the follow-up, I made a stable backport request [1] of the
relevant commits to v4.9+.
BR,
Jani.
[1] http://mid.mail-archive.com/87bmqfn9sp.fsf@intel.com
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-05-26 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 20:21 i915 4.9 regression: DP AUX CH sanitization no longer working on Asus desktops Daniel Drake
2017-05-04 20:37 ` Ville Syrjälä
2017-05-04 20:52 ` Daniel Drake
2017-05-04 21:14 ` Manasi Navare
2017-05-05 10:29 ` Ville Syrjälä
2017-05-24 13:50 ` Daniel Drake
2017-05-26 11:26 ` Jani Nikula [this message]
2017-05-05 6:24 ` Jani Nikula
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=878tljn9kj.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chiu@endlessm.com \
--cc=drake@endlessm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux@endlessm.com \
--cc=ville.syrjala@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).