From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Hans de Goede" <hdegoede@redhat.com>,
"Daniel Vetter" <daniel.vetter@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Fix not finding the VBT when it overlaps with OPREGION_ASLE_EXT
Date: Mon, 06 Feb 2017 08:55:18 +0200 [thread overview]
Message-ID: <87y3xjbyg9.fsf@intel.com> (raw)
In-Reply-To: <daaa5f0c-0106-2b7e-949f-1f786b78678d@redhat.com>
On Sat, 04 Feb 2017, Hans de Goede <hdegoede@redhat.com> wrote:
> Hi Jani,
>
> So any further update on this ? I've just got a report from
> an user that my fix also fixes the LCD panel on his (different
> model, ACER SW5_017) machine not lighting up:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=155241#c56
>
> Although my fix my be in contradiction with the VBT spec,
> I do not see how it can really hurt, it just allows the
> VBT to extend into an unused part of the opregion.
>
> Something which windows 10 apparently allows, otherwise
> we would not have multiple models shipping with this
> problem, so it seems best to just allow this in Linux
> too.
Suffice it to say I'm pretty frustrated with this.
Let's get your patch merged, I'll reply to it with a couple of specific
comments.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-06 6:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 10:19 [PATCH] drm/i915: Fix not finding the VBT when it overlaps with OPREGION_ASLE_EXT Hans de Goede
2016-12-25 10:19 ` Hans de Goede
2016-12-27 10:58 ` Jani Nikula
2016-12-27 10:58 ` Jani Nikula
2016-12-31 16:00 ` Hans de Goede
2017-01-20 8:07 ` Hans de Goede
2017-01-20 8:07 ` Hans de Goede
2017-01-20 8:16 ` Jani Nikula
2017-01-20 8:16 ` Jani Nikula
2017-01-23 10:36 ` Jani Nikula
2017-01-23 10:36 ` Jani Nikula
2017-01-23 16:04 ` Hans de Goede
2017-01-24 13:33 ` Jani Nikula
2017-02-04 13:51 ` Hans de Goede
2017-02-06 6:55 ` Jani Nikula [this message]
2017-02-06 7:04 ` Jani Nikula
2017-02-06 7:04 ` Jani Nikula
2017-02-10 10:52 ` Hans de Goede
2017-02-10 10:52 ` Hans de Goede
2017-02-10 12:21 ` Jani Nikula
2017-02-10 12:21 ` 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=87y3xjbyg9.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--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 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.