Intel-GFX Archive on 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
Subject: Re: HD audio not working
Date: Thu, 09 Aug 2012 08:07:22 +0200	[thread overview]
Message-ID: <s5hlihofvj9.wl%tiwai@suse.de> (raw)
In-Reply-To: <502319A7.2080604@kvalsvoll.com>

[Cc re-added, please don't drop Cc]

At Thu, 09 Aug 2012 04:00:07 +0200,
Øyvind Kvålsvoll wrote:
> 
> Patch tested now on alsa-1.0.25, compiled for 3.2.xx kernel.
> 
> Unfortunately this patch does not fix the problem, still only noise on 
> TrueHD and DTS-HD (on HDMI).

So it didn't change anything?

> It can play TrueHD and DTS-HD if decoded and output (on HDMI) to 
> multichannel PCM.
> The patch did not destroy anything, as far as I could verify during this 
> short test playing different format audio and video files.
> 
> I did not verify that the patch was actually embedded correctly.
> Alsa-version was verified by version and build date.

Don't trust anything from this 1.0.25 number.  It's just confusing.
It sticks for so long time although the code has been rewritten
largely.  That is, 1.0.25 isn't only 1.0.25.  Not like Highlander.
(I suggested Jaroslav to drop this numbering, but he didn't agree...)

For testing, try alsa-driver-snapshot tarball below.
  ftp://ftp.suse.com/pub/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz

there you need to apply the patch in alsa-kernel directory with -p2.


thanks,

Takashi

> 
> 
> Øyvind Kvålsvoll
> (+47) 41306243
> N-6008 Ålesund, Norway
> 
> 
> On 08.08.2012 09:31, Takashi Iwai wrote:
> > 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

      parent reply	other threads:[~2012-08-09  6:07 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
     [not found]   ` <502319A7.2080604@kvalsvoll.com>
2012-08-09  6:07     ` Takashi Iwai [this message]

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=s5hlihofvj9.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=oyvind@kvalsvoll.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox