From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102401] Radeon Displayport Audio Warping
Date: Sun, 18 Sep 2016 02:43:17 +0000 [thread overview]
Message-ID: <bug-102401-2300-atB3a03NiX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-102401-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=102401
--- Comment #13 from Maxqia <public@maxqia.com> ---
Looking back with an extra year of programming knowledge, it seems like commit
7726e72b3d6879ee5fc743a230eb6f5afa12844b doesn't do anything except add a
drm_detect_monitor_audio to the hdmi audio pathway ..., before that commit only
Displayport was checked for audio. Anyways, issue still present.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-18 2:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 1:05 [Bug 102401] New: 4.2 RC5 bugzilla-daemon
2015-08-07 1:06 ` [Bug 102401] Radeon Displayport Audio Warping bugzilla-daemon
2015-08-07 1:06 ` bugzilla-daemon
2015-08-10 21:09 ` bugzilla-daemon
2015-08-10 21:17 ` bugzilla-daemon
2015-08-10 21:39 ` bugzilla-daemon
2015-08-10 22:47 ` bugzilla-daemon
2015-08-11 3:28 ` bugzilla-daemon
2015-08-13 9:46 ` bugzilla-daemon
2015-08-17 8:47 ` bugzilla-daemon
2015-08-19 18:00 ` bugzilla-daemon
2015-08-20 1:33 ` bugzilla-daemon
2015-08-20 1:34 ` bugzilla-daemon
2015-08-21 0:28 ` bugzilla-daemon
2015-08-21 23:44 ` bugzilla-daemon
2015-09-17 3:23 ` bugzilla-daemon
2015-09-23 15:42 ` bugzilla-daemon
2016-09-18 2:43 ` bugzilla-daemon [this message]
2016-09-18 3:47 ` bugzilla-daemon
2017-03-04 7:40 ` bugzilla-daemon
2018-10-10 22:33 ` 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-102401-2300-atB3a03NiX@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.