From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Chris Wilson <chris@chris-wilson.co.uk>,
Jani Nikula <jani.nikula@linux.intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Oleksij Rempel <linux@rempel-privat.de>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] drm/i915/opregion: work around buggy firmware that provides 8+ output devices
Date: Wed, 19 Feb 2014 07:33:39 +0000 [thread overview]
Message-ID: <20140219073339.GA30685@srcf.ucam.org> (raw)
In-Reply-To: <53045DD1.5010406@intel.com>
On Wed, Feb 19, 2014 at 03:31:29PM +0800, Aaron Lu wrote:
> DID2 is in system memory region and has some assigned value like 0x400
> when we read it. For this case it is easy since there is only one output
> device that is of type LVDS so we can match it to connector of type eDP
> or LVDS, suppose there is only one such connector. But for output
> devices' whose _ADR has the value of 0x301, 0x302, etc. I have no idea
> how to match them up to the connectors of that type as we can't be sure
> the probe order we have used in i915 driver is the same as BIOS'.
Non-standard _ADR values are assigend by the GPU vendor, so Intel should
be able to provide you with the correct interpretations.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2014-02-19 7:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 3:05 [PATCH] drm/i915/opregion: work around buggy firmware that provides 8+ output devices Aaron Lu
2014-02-12 10:31 ` Chris Wilson
2014-02-12 10:31 ` Chris Wilson
2014-02-12 10:52 ` Jani Nikula
2014-02-12 10:52 ` Jani Nikula
2014-02-13 9:10 ` Aaron Lu
2014-02-13 9:10 ` Aaron Lu
2014-02-13 10:08 ` Chris Wilson
2014-02-13 10:08 ` Chris Wilson
2014-02-13 12:03 ` Daniel Vetter
2014-02-19 7:31 ` Aaron Lu
2014-02-19 7:33 ` Matthew Garrett [this message]
2014-02-19 8:59 ` Aaron Lu
2014-02-19 8:59 ` Aaron Lu
2014-03-04 14:45 ` Daniel Vetter
2014-12-08 1:58 ` Aaron Lu
2014-12-08 1:58 ` Aaron Lu
2014-12-08 11:00 ` Jani Nikula
2014-12-08 11:00 ` Jani Nikula
2014-12-08 11:04 ` Jani Nikula
2014-12-08 11:04 ` [Intel-gfx] " Jani Nikula
2014-12-09 9:15 ` Aaron Lu
2014-12-09 9:15 ` [Intel-gfx] " Aaron Lu
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=20140219073339.GA30685@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=aaron.lu@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=rjw@rjwysocki.net \
/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.