From: Hans de Goede <hdegoede@redhat.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, Aaron Lu <aaron.lu@intel.com>
Subject: Fixing i915/opregion issues with firmware which lists more then 8 output devices
Date: Thu, 5 Nov 2015 17:05:05 +0100 [thread overview]
Message-ID: <563B7E31.60200@redhat.com> (raw)
Hi,
As discussed in the past, the i915 opregion code does not do the
right thing wrt the CADL field when there are more then 8 outputs,
this is causing issues on many different types of Asus laptops.
This thread has details and a number of attempts to fix this:
https://lkml.org/lkml/2014/2/11/1032
This is impacting many users, here is an incomplete list of bug reports:
https://bugzilla.kernel.org/show_bug.cgi?id=70241
https://bugzilla.kernel.org/show_bug.cgi?id=88941
https://bugzilla.redhat.com/show_bug.cgi?id=1144866
https://bugzilla.redhat.com/show_bug.cgi?id=1277785
And I'm pretty sure that is just the tip of the iceberg, some users
have even analyzed their BIOS AML code and come up with an AML
hack in an attempt to fix this:
http://blog.yjwong.name/fixing-display-backlight-hotkeys-on-asus-n550jk/
It would be really great of someone from Intel could step up and start
working on a proper fix for this.
Regards,
Hans
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-11-05 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 16:05 Hans de Goede [this message]
2015-11-06 10:19 ` Fixing i915/opregion issues with firmware which lists more then 8 output devices Jani Nikula
2015-11-06 10:20 ` Hans de Goede
2015-11-13 18:41 ` Jani Nikula
2016-03-23 11:48 ` Jani Nikula
2016-03-23 12:57 ` Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2016-03-22 16:24 Nicolas Repentin
2016-03-23 11:36 ` Jani Nikula
2016-03-23 17:04 ` Nicolas Repentin
2016-03-24 8:36 ` Jani Nikula
2016-04-15 17:35 ` Nicolas Repentin
2016-04-18 7:44 ` Jani Nikula
2016-04-25 18:19 Ruslan Boitsov
2016-04-26 11:28 thermatk(EZN)
2016-08-30 12:55 tasev.stefanoska
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=563B7E31.60200@redhat.com \
--to=hdegoede@redhat.com \
--cc=aaron.lu@intel.com \
--cc=daniel.vetter@ffwll.ch \
--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 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).