* [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes
2018-03-01 5:34 [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes bugzilla-daemon
@ 2018-03-01 14:49 ` bugzilla-daemon
2018-03-01 19:41 ` bugzilla-daemon
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2018-03-01 14:49 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 606 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105302
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |harry.wentland@amd.com
--- Comment #1 from Alex Deucher <alexdeucher@gmail.com> ---
The non-DC code should really have limited this too. It's probably a bug
there. As to what the actual limit is, hopefully Harry can comment on that.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1990 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
^ permalink raw reply [flat|nested] 8+ messages in thread* [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes
2018-03-01 5:34 [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes bugzilla-daemon
2018-03-01 14:49 ` bugzilla-daemon
@ 2018-03-01 19:41 ` bugzilla-daemon
2018-03-01 23:42 ` bugzilla-daemon
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2018-03-01 19:41 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 711 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105302
--- Comment #2 from Harry Wentland <harry.wentland@amd.com> ---
I don't have the spec right now but wikipedia has a nice run-down of the DVI
bounding box: https://en.wikipedia.org/wiki/Digital_Visual_Interface#Digital
Basically 2560x1600 @ 60Hz is the highest allowed for dual-link, which is just
a tad above your 2560x1440 @ 60Hz. 110Hz at full resolution would definitely
not be supported by DVI.
What monitor are you using? Is it intended to support 110Hz at full resolution
on DVI? Could it be that this full monitor capabilities are only supported
through DP?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1618 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
^ permalink raw reply [flat|nested] 8+ messages in thread* [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes
2018-03-01 5:34 [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes bugzilla-daemon
2018-03-01 14:49 ` bugzilla-daemon
2018-03-01 19:41 ` bugzilla-daemon
@ 2018-03-01 23:42 ` bugzilla-daemon
2018-03-02 15:03 ` bugzilla-daemon
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2018-03-01 23:42 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 1180 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105302
--- Comment #3 from Andrew Sheldon <asheldon55@gmail.com> ---
(In reply to Harry Wentland from comment #2)
> I don't have the spec right now but wikipedia has a nice run-down of the DVI
> bounding box: https://en.wikipedia.org/wiki/Digital_Visual_Interface#Digital
>
> Basically 2560x1600 @ 60Hz is the highest allowed for dual-link, which is
> just a tad above your 2560x1440 @ 60Hz. 110Hz at full resolution would
> definitely not be supported by DVI.
>
> What monitor are you using? Is it intended to support 110Hz at full
> resolution on DVI? Could it be that this full monitor capabilities are only
> supported through DP?
It's a cheap Korean monitor that only supports DVI-D (Qnix qx2710 single input
version), and unofficially supports greater than 60hz. You're right, it's above
DVI-D spec but it would be nice to have an option to use higher pixel clocks
nevertheless. The Nvidia binary drivers have the option for ignoring the pixel
clock check so there is at least one example of this being supported in the
wild.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2183 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
^ permalink raw reply [flat|nested] 8+ messages in thread* [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes
2018-03-01 5:34 [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes bugzilla-daemon
` (2 preceding siblings ...)
2018-03-01 23:42 ` bugzilla-daemon
@ 2018-03-02 15:03 ` bugzilla-daemon
2018-03-02 15:39 ` bugzilla-daemon
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2018-03-02 15:03 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 254 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105302
--- Comment #4 from Harry Wentland <harry.wentland@amd.com> ---
This sounds like a feature request, rather than a bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1076 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
^ permalink raw reply [flat|nested] 8+ messages in thread* [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes
2018-03-01 5:34 [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes bugzilla-daemon
` (3 preceding siblings ...)
2018-03-02 15:03 ` bugzilla-daemon
@ 2018-03-02 15:39 ` bugzilla-daemon
2018-03-08 9:06 ` bugzilla-daemon
2019-11-19 8:31 ` bugzilla-daemon
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2018-03-02 15:39 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 597 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105302
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
--- Comment #5 from Alex Deucher <alexdeucher@gmail.com> ---
I'd rather not support running things out of spec in the driver. The source is
open. If you want to adjust the code allow something like that you can.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1966 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
^ permalink raw reply [flat|nested] 8+ messages in thread* [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes
2018-03-01 5:34 [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes bugzilla-daemon
` (4 preceding siblings ...)
2018-03-02 15:39 ` bugzilla-daemon
@ 2018-03-08 9:06 ` bugzilla-daemon
2019-11-19 8:31 ` bugzilla-daemon
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2018-03-08 9:06 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 474 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105302
--- Comment #6 from Andrew Sheldon <asheldon55@gmail.com> ---
(In reply to Alex Deucher from comment #5)
> I'd rather not support running things out of spec in the driver. The source
> is open. If you want to adjust the code allow something like that you can.
Fair enough, it's simple enough to patch the source for a higher limit.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1368 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
^ permalink raw reply [flat|nested] 8+ messages in thread* [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes
2018-03-01 5:34 [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes bugzilla-daemon
` (5 preceding siblings ...)
2018-03-08 9:06 ` bugzilla-daemon
@ 2019-11-19 8:31 ` bugzilla-daemon
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2019-11-19 8:31 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105302
Martin Peres <martin.peres@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #7 from Martin Peres <martin.peres@free.fr> ---
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.
You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/319.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2422 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 8+ messages in thread