All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77002] hdmi audio problems with 3.14
Date: Wed, 09 Apr 2014 15:13:46 +0000	[thread overview]
Message-ID: <bug-77002-502-NYq14CWhoL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-77002-502@http.bugs.freedesktop.org/>


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

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

--- Comment #32 from Garrett <socalfisher@gmail.com> ---
Yes I am gfisher.  

Peter.  OK. I renamed/saved the old pull.  I git pulled new.  I will rebuild
overnight.  Thx.

The logs that I upload- I applied this patch
https://bugs.freedesktop.org/attachment.cgi?id=97049&action=edit to kernel 3.14
in the oe build.  According to the messages it patched ...hda just fine.  It
did not appear to change anything (bug wise).  I did the logs in #29 over SSH
while the sounds were distorted.

I saw the revert commit comment.  But I am not sure that I can do that on an OE
system (I managed to get patches to work).  I am using OE because breakage and
testing across PC is so much easier.

I will rebuild the latest OE 4.0 branch from new, then report back.  Let me
know if anything else is needed.

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

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

  parent reply	other threads:[~2014-04-09 15:13 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 [this message]
2014-04-09 15:22 ` bugzilla-daemon
2014-04-10 14:21 ` bugzilla-daemon
2014-04-10 14:28 ` bugzilla-daemon
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-NYq14CWhoL@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.