From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
Subject: [Bug 67051] No nouveau HDMI sound on NVIDIA GT430
Date: Thu, 18 Jul 2013 23:45:19 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1347167159=="
Return-path:
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: nouveau-bounces+gcfxn-nouveau=m.gmane.org-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Errors-To: nouveau-bounces+gcfxn-nouveau=m.gmane.org-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
List-Id: nouveau.vger.kernel.org
--===============1347167159==
Content-Type: multipart/alternative; boundary="1374191119.B7CFc061.18815"; charset="us-ascii"
--1374191119.B7CFc061.18815
Date: Thu, 18 Jul 2013 23:45:19 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
https://bugs.freedesktop.org/show_bug.cgi?id=67051
--- Comment #12 from Ilia Mirkin ---
(In reply to comment #10)
> (In reply to comment #9)
> > (b) Can you test out a 3.7-based kernel?
> I suppose I can. Let me know if it's critical for you to proceed with your
> work. I'd rather wait for some more of your thoughts/tests/results _if
> possible_. However, I'll jump to it immediately if you say the word.
Well, the situation is that I don't have any HDMI devices at all (either with
HDMI outputs or inputs, forget HDMI audio), nor do I know anything about it. So
if this doesn't work, that means that someone else needs to (a) reproduce your
issue [and note, hdmi audio does work for some other people, so there must be
something a bit more special about your situation, be it EDID data or more
missed register setup], and (b) do the RE work to figure out what we're
missing.
It seems like testing out an old kernel is easy by comparison. However I don't
hold out a huge amount of hope for it, since like you said, eld_valid = 0,
which more likely indicates an EDID issue.
If you're interested, some minor code inspection shows that at least some of
the logic is in nv50_display.c:nv50_audio_mode_set. You could add prints in
there to see what it's detecting stuff as. You could also add prints to
drm_edid.c:drm_detect_monitor_audio, perhaps your monitor's EDID is different
than what it expects.
Looks like there are a few prints already, you could see what happens when you
boot with drm.debug=0x06 which should output nouveau- and kms-related debug
statements.
--
You are receiving this mail because:
You are the assignee for the bug.
--1374191119.B7CFc061.18815
Date: Thu, 18 Jul 2013 23:45:19 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Comment # 12
on bug 67051
from Ilia Mirkin
(In reply to comment #10)
> (In reply to comment #9)
> > (b) Can you test out a 3.7-based kernel?
> I suppose I can. Let me know if it's critical for you to proceed with your
> work. I'd rather wait for some more of your thoughts/tests/results _if
> possible_. However, I'll jump to it immediately if you say the word.
Well, the situation is that I don't have any HDMI devices at all (either with
HDMI outputs or inputs, forget HDMI audio), nor do I know anything about it. So
if this doesn't work, that means that someone else needs to (a) reproduce your
issue [and note, hdmi audio does work for some other people, so there must be
something a bit more special about your situation, be it EDID data or more
missed register setup], and (b) do the RE work to figure out what we're
missing.
It seems like testing out an old kernel is easy by comparison. However I don't
hold out a huge amount of hope for it, since like you said, eld_valid = 0,
which more likely indicates an EDID issue.
If you're interested, some minor code inspection shows that at least some of
the logic is in nv50_display.c:nv50_audio_mode_set. You could add prints in
there to see what it's detecting stuff as. You could also add prints to
drm_edid.c:drm_detect_monitor_audio, perhaps your monitor's EDID is different
than what it expects.
Looks like there are a few prints already, you could see what happens when you
boot with drm.debug=0x06 which should output nouveau- and kms-related debug
statements.
You are receiving this mail because:
- You are the assignee for the bug.
--1374191119.B7CFc061.18815--
--===============1347167159==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
--===============1347167159==--