All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: HDMI Audio screwed up w/ recent kernels
Date: Sat, 31 Dec 2016 02:55:29 -0500	[thread overview]
Message-ID: <m3bmvsfs7i.fsf@jhcloos.com> (raw)
In-Reply-To: <CADnq5_Pd3VsxYHEEaocqnP4U++LAjocPOVJamboFLuFR3vR6sQ@mail.gmail.com> (Alex Deucher's message of "Sat, 31 Dec 2016 00:36:39 -0500")

>>>>> "AD" == Alex Deucher <alexdeucher@gmail.com> writes:

AD> That option is just a carry over from when the amdgpu was copied from
AD> radeon.  There is some code for older asics left over from when the
AD> code was originally ported from radeon.  If you want hdmi audio
AD> support you need to use the new dc modesetting code we are working on:
AD> https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-4.7

AD> As for radeon, a bisection would help.  If both drivers worked before
AD> and now both have issues, I'd suggest looking at the hda audio driver.

All I know is that radeon audio worked fine in 3.x and stopped working
in 4.x  Where stopped working means fairly recognizable audio which
sounds mixed with white noise.

I doubt I can bisect.  The screen it uses is in almost constant use....

In order for the fb to be there from boot, the firmware is all compiled
into the kernels via CONFIG_EXTRA_FIRMWARE.

Given that, with 4.9, the audio has exactly the same problem with amdgpu
as with radeon, I suspect the actual problem is in the firmware.  If so,
and since I do not have whatever firmware files were installed back when
I compiled the 3. kernels, I doubt bisecting the kernel would help.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 0x997A9F17ED7DAEA6
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-12-31  7:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23  0:49 HDMI Audio screwed up w/ recent kernels James Cloos
2016-12-27  9:47 ` Daniel Vetter
2016-12-27 17:17   ` James Cloos
2016-12-27 18:20     ` Daniel Vetter
2016-12-27 18:32       ` Bridgman, John
2016-12-28 19:43       ` James Cloos
2016-12-31  5:36     ` Alex Deucher
2016-12-31  7:55       ` James Cloos [this message]
2017-01-02 16:04         ` Alex Deucher
2017-01-02 17:11           ` James Cloos

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=m3bmvsfs7i.fsf@jhcloos.com \
    --to=cloos@jhcloos.com \
    --cc=alexdeucher@gmail.com \
    --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.