From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Anuar, Nuhairi" <nuhairi.anuar@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Mustaffa, Mustamin B" <mustamin.b.mustaffa@intel.com>
Subject: Re: [PATCH] drm/i915: fix the issue DP-1 not working in guest
Date: Thu, 15 Jun 2017 23:54:36 +0300 [thread overview]
Message-ID: <87injxvunn.fsf@intel.com> (raw)
In-Reply-To: <20170615102856.GV12629@intel.com>
On Thu, 15 Jun 2017, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Thu, Jun 15, 2017 at 03:53:18AM +0000, Anuar, Nuhairi wrote:
>> To be clear, I believe right now, GVT-g architecture on upstream still only have one Virtualized DP monitor which will be on port B/D, but we have patches (not yet upstream) that have 3 virtualized DP monitors which will be attached to Port A/B/D. So we need to add this flexibility in the code so that it is not conflicted with eDP logic.
>
> Please don't do that. Real hardware doesn't support non-eDP on port A,
> so your virtualized thing shouldn't either. Why aren't you putting it on
> port C instead?
Agreed. Otherwise we may end up piling up more intel_vgpu_active()
checks all over the place.
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-06-15 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 14:55 [PATCH] drm/i915: fix the issue DP-1 not working in guest Anuar, Nuhairi
2017-06-15 3:53 ` Anuar, Nuhairi
2017-06-15 10:28 ` Ville Syrjälä
2017-06-15 20:54 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-14 5:47 Mustamin B Mustaffa
2017-06-14 13:38 ` Ville Syrjälä
2018-02-20 6:40 ` Mustamin B Mustaffa
2018-02-20 11:35 ` Jani Nikula
2018-02-21 0:01 ` Mustaffa, Mustamin B
2018-02-21 8:03 ` Jani Nikula
2018-02-21 8:21 ` Mustaffa, Mustamin B
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=87injxvunn.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mustamin.b.mustaffa@intel.com \
--cc=nuhairi.anuar@intel.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).