From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98505] [Topaz] Regression introduces in 4.8-rc3
Date: Fri, 04 Nov 2016 14:51:49 +0000 [thread overview]
Message-ID: <bug-98505-502-zY6GWJSV2g@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98505-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2203 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98505
--- Comment #15 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Peter Wu from comment #14)
> (In reply to Alex Deucher from comment #12)
> [..]
> > > Lowering the minumum from 2015 to 2014 should work for nouveau:
> > > https://lists.freedesktop.org/archives/nouveau/2016-July/025619.html
> > >
> >
> > For further clarify on your research, the current hybrid graphics spec
> > requires no connectors on the dGPU and hence no audio devices. For devices
> > with connectors on the dGPU, they should use the older vendor specific
> > methods and PR3 should not be exposed.
>
> The list was mentioned because of the BIOS dates and whether _PR3 is used.
>
> The Windows 8 requirements state that the discrete GPU is render-only[0],
> but the Win10 reqs have no such requirement[1]. (Are these the same specs
> you had in mind? If not, could you share the right one?) On my new hybrid
> nvidia laptop, there are actually DP/HDMI ports to the dGPU (HDMI with
> audio).
>
I had access to the PR3 spec internally. I'm not sure if it's available
publicly or not. Support for displays was not included in the information I
saw or from talking with our internal hybrid graphics architects. It's
possible the spec has been updated since I last talked to them earlier this
year. I can double check.
Does your new laptop use PR3 or the older nvidia proprietary ACPI method?
> [0]:
> https://msdn.microsoft.com/en-us/library/windows/hardware/dn265510(v=vs.85).
> aspx
> [1]:
> https://msdn.microsoft.com/en-us/windows/hardware/commercialize/design/
> compatibility/systems#systemfundamentalsgraphicshybridgraphicsmultigpu
>
> > > You can try to ask Mika, see v4.7-rc2-3-g9d26d3a. Maybe the presence of a
> > > power resource (_PR3 or flags.power_resources) can be used as a hint whether
> > > to enable port PM.
> >
> > Yes, the presence of _PR3 would be a great way to determine when to enable
> > it.
>
> Have you been working on this or should I have a look?
I have not been. Please have a look. Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3525 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-04 14:51 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 16:48 [Bug 98505] [Topaz] Regression introduces in 4.8-rc3 bugzilla-daemon
2016-10-30 16:53 ` bugzilla-daemon
2016-11-01 13:29 ` bugzilla-daemon
2016-11-01 13:56 ` bugzilla-daemon
2016-11-01 18:26 ` bugzilla-daemon
2016-11-01 20:46 ` bugzilla-daemon
2016-11-01 20:49 ` bugzilla-daemon
2016-11-01 23:31 ` bugzilla-daemon
2016-11-02 6:07 ` bugzilla-daemon
2016-11-02 6:11 ` bugzilla-daemon
2016-11-02 16:35 ` bugzilla-daemon
2016-11-02 16:46 ` bugzilla-daemon
2016-11-02 16:55 ` bugzilla-daemon
2016-11-02 16:56 ` bugzilla-daemon
2016-11-04 0:08 ` bugzilla-daemon
2016-11-04 14:51 ` bugzilla-daemon [this message]
2016-11-04 15:04 ` bugzilla-daemon
2016-11-07 18:42 ` bugzilla-daemon
2016-11-11 17:56 ` bugzilla-daemon
2016-11-11 17:58 ` [Bug 98505] [radeon, amdgpu] Regression introduced " bugzilla-daemon
2016-11-11 18:14 ` bugzilla-daemon
2016-11-11 18:17 ` bugzilla-daemon
2016-11-11 18:49 ` bugzilla-daemon
2016-11-11 21:22 ` bugzilla-daemon
2016-11-12 23:40 ` bugzilla-daemon
2016-11-13 6:41 ` bugzilla-daemon
2016-11-13 11:24 ` bugzilla-daemon
2016-11-13 16:01 ` bugzilla-daemon
2016-11-13 16:02 ` bugzilla-daemon
2016-11-14 10:52 ` bugzilla-daemon
2016-11-14 15:12 ` bugzilla-daemon
2016-11-17 15:03 ` bugzilla-daemon
2016-11-19 0:22 ` bugzilla-daemon
2016-11-19 2:07 ` bugzilla-daemon
2016-11-19 2:08 ` bugzilla-daemon
2016-11-19 17:32 ` bugzilla-daemon
2016-11-19 19:21 ` bugzilla-daemon
2016-11-19 19:23 ` bugzilla-daemon
2016-12-05 13:49 ` bugzilla-daemon
2016-12-05 19:32 ` bugzilla-daemon
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=bug-98505-502-zY6GWJSV2g@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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).