All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Øyvind Kvålsvoll" <oyvind@kvalsvoll.com>
Cc: intel-gfx@lists.freedesktop.org, wangxingchao2011@gmail.com
Subject: Re: HD audio not working
Date: Wed, 08 Aug 2012 09:31:31 +0200	[thread overview]
Message-ID: <s5h628thmb0.wl%tiwai@suse.de> (raw)
In-Reply-To: <502197D4.6080004@kvalsvoll.com>

At Wed, 08 Aug 2012 00:33:56 +0200,
Øyvind Kvålsvoll wrote:
> 
> Ref. to filed bug https://bugs.freedesktop.org/show_bug.cgi?id=49055:
> 
> DTS-HD and Dolby TrueHD audio is not working in Intel Sandy Bridge.
> This must have been well known for quite some time now, and I consider 
> this to be a serious error in the Intel driver.
> Due to this error it is not possible to play DTS-HD or Dolby-TrueHD on 
> Linux.
> 
> I have waited patiently several months for a fix, as I was confident 
> that Intel knew about the problem and surely would fix this in the next 
> driver release.
> I also have the understanding that quite many people are waiting for 
> this fix.
> 
> Seeing as the bug is filed, and someone has actually looked at it and 
> identified the problem, is there a plan for further progress on this?

Could you check whether the test patch Xingchao posted in the last
week fixes your problem?
	https://patchwork.kernel.org/patch/1256981/

If this really cures, we can cook up it in a bit better form and merge
to the upstream.


thanks,

Takashi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2012-08-08  7:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07 22:33 HD audio not working Øyvind Kvålsvoll
2012-08-08  7:31 ` Takashi Iwai [this message]
     [not found]   ` <502319A7.2080604@kvalsvoll.com>
2012-08-09  6:07     ` Takashi Iwai

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=s5h628thmb0.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=oyvind@kvalsvoll.com \
    --cc=wangxingchao2011@gmail.com \
    /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.