From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77002] hdmi audio problems with 3.14
Date: Thu, 10 Apr 2014 14:28:30 +0000 [thread overview]
Message-ID: <bug-77002-502-kF5vQqBZje@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-77002-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1084 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=77002
--- Comment #35 from bgunteriv@gmail.com ---
(In reply to comment #34)
> (In reply to comment #29)
> > Garret,
> >
> > make sure your tree is in sync. The patch done by Anssi has already been
> > included. It's here:
> > https://github.com/OpenELEC/OpenELEC.tv/commit/
> > a333166f7d6fda668cc2184797d302fe89288c9d
>
> OK the build finished this AM and in the linux/3.14 folder this
> reverse-order patch was present. But unfortunately playback is the same.
> Machine gun like cyclical sounds with audio coming in and out.
>
> Any more info needed, please let me know.
>
> Here is my card [Diamond 7750PE51G]:
>
> http://www.newegg.com/Product/Product.aspx?Item=N82E16814103206
>
> thanks,
> Garrett
this was my fear. I don't think your problem fits the scope of this bug.
Garrett, can you open a new bug report, and i'll put up my logs as well.
this way we won't get the devs confused on this situation.
send me a PM on XBMC once you've got it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2144 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-04-10 14:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 13:23 [Bug 77002] New: problems with kernel 3.14 bugzilla-daemon
2014-04-03 13:25 ` [Bug 77002] " bugzilla-daemon
2014-04-03 13:26 ` bugzilla-daemon
2014-04-03 13:27 ` bugzilla-daemon
2014-04-04 14:44 ` bugzilla-daemon
2014-04-04 14:48 ` bugzilla-daemon
2014-04-04 15:28 ` bugzilla-daemon
2014-04-04 15:29 ` bugzilla-daemon
2014-04-04 15:35 ` bugzilla-daemon
2014-04-05 21:43 ` bugzilla-daemon
2014-04-07 2:20 ` bugzilla-daemon
2014-04-07 2:26 ` [Bug 77002] hdmi audio problems with 3.14 bugzilla-daemon
2014-04-07 2:26 ` bugzilla-daemon
2014-04-07 15:33 ` bugzilla-daemon
2014-04-07 15:33 ` bugzilla-daemon
2014-04-07 15:35 ` bugzilla-daemon
2014-04-07 19:13 ` bugzilla-daemon
2014-04-07 19:22 ` bugzilla-daemon
2014-04-07 19:39 ` bugzilla-daemon
2014-04-07 19:42 ` bugzilla-daemon
2014-04-07 19:46 ` bugzilla-daemon
2014-04-07 19:49 ` bugzilla-daemon
2014-04-07 20:14 ` bugzilla-daemon
2014-04-07 20:14 ` bugzilla-daemon
2014-04-08 7:37 ` bugzilla-daemon
2014-04-08 13:10 ` bugzilla-daemon
2014-04-08 17:42 ` bugzilla-daemon
2014-04-08 18:07 ` bugzilla-daemon
2014-04-08 20:53 ` bugzilla-daemon
2014-04-09 14:30 ` bugzilla-daemon
2014-04-09 14:32 ` bugzilla-daemon
2014-04-09 14:35 ` bugzilla-daemon
2014-04-09 14:40 ` bugzilla-daemon
2014-04-09 15:13 ` bugzilla-daemon
2014-04-09 15:22 ` bugzilla-daemon
2014-04-10 14:21 ` bugzilla-daemon
2014-04-10 14:28 ` bugzilla-daemon [this message]
2014-04-11 13:06 ` bugzilla-daemon
2014-04-11 14:02 ` bugzilla-daemon
2015-01-21 18:31 ` bugzilla-daemon
2015-01-22 16:13 ` 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-77002-502-kF5vQqBZje@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