All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102820] [bisected][DC] commit ebbf7337e2daacacef3e01114e6be68a2a4f11b4 prevents X11 from starting
Date: Tue, 17 Oct 2017 22:25:33 +0000	[thread overview]
Message-ID: <bug-102820-502-ec2ZXE77zS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102820-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2041 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=102820

--- Comment #14 from dwagner <jb5sgc1n.nya@20mm.eu> ---
(In reply to Alex Deucher from comment #13)
> It's pretty vague unfortunately regarding HDMI:
> It does not explicitly say 4K@60 on HDMI.  The high refresh rates may only
> be available on DP.

Well then, if you suspect XFX to be sneaky bitches, I should refer you to the
page of the actual reseller that I bought my XFX RX 460 from:
https://www.caseking.de/en/xfx-radeon-rx-460-passive-heatsink-edition-2048-mb-gddr5-gcxf-148.html
which clearly states: "The 2.0b HDMI port carries a 4K/UHD resolution signal at
60 Hz and permits the sending and receiving of encrypted signals using the HDCP
2.2 protocol (4K streaming, 4K Blu-Rays)."

And that corresponds well to the many reports of Windows users you find on the
Internet that confirm XFX RX460 cards do in fact drive HDMI displays at 4k 60Hz
also under Windows - or should we assume the Windows drivers to be broken and
all those users just being "lucky"?

> HDMI 2.0b does not imply 4K@60.

Support of 4k @ 60Hz was the first and foremost feature advertised by the HDMI
licensors as being the main reason for introducing HDMI 2.0! - Here's their
press release from back then: 
https://www.hdmi.org/press/press_release.aspx?prid=133
and a clear statement on HDMI 2.0b supporting 4k@60Hz:
https://www.hdmi.org/manufacturer/hdmi_2_0/index.aspx

> Your board may work, but others might not depending on the board, cable,
> monitor, etc.

Yes, the GPU board cannot guarantee anything with regards to cabling or
monitors - but how is that a reason for a driver software to keep users from
even trying to use this fundamentally important, reseller-promised,
broadly-reported-to-be-working-under-Windows feature?

Should audio drivers discard LFE channels because some sound card vendor cannot
validate that the user connected a capable sub-woofer to his amplifier...?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3329 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

  parent reply	other threads:[~2017-10-17 22:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17 11:46 [Bug 102820] [bisected] commit ebbf7337e2daacacef3e01114e6be68a2a4f11b4 prevents X11 from starting bugzilla-daemon
2017-09-17 18:40 ` bugzilla-daemon
2017-09-17 20:14 ` bugzilla-daemon
2017-09-17 20:16 ` bugzilla-daemon
2017-09-17 20:23 ` bugzilla-daemon
2017-09-17 20:27 ` bugzilla-daemon
2017-10-13 22:35 ` bugzilla-daemon
2017-10-16  9:22 ` [Bug 102820] [bisected][DC] " bugzilla-daemon
2017-10-16 13:42 ` bugzilla-daemon
2017-10-16 21:14 ` bugzilla-daemon
2017-10-16 21:36 ` bugzilla-daemon
2017-10-16 23:45 ` bugzilla-daemon
2017-10-17  7:35 ` bugzilla-daemon
2017-10-17  7:37 ` bugzilla-daemon
2017-10-17 13:15 ` bugzilla-daemon
2017-10-17 22:25 ` bugzilla-daemon [this message]
2017-10-17 22:45 ` bugzilla-daemon
2017-10-17 23:33 ` bugzilla-daemon
2017-10-18 21:46 ` bugzilla-daemon
2018-02-20  1:13 ` bugzilla-daemon
2018-02-20 18:48 ` bugzilla-daemon
2018-02-20 23:22 ` bugzilla-daemon
2018-02-20 23:24 ` bugzilla-daemon
2018-02-21  2:28 ` bugzilla-daemon
2018-04-24 19:00 ` 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-102820-502-ec2ZXE77zS@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 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.