From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 62305] [NV4B] No HDMI Audio out (pass-thru) on Geforce 7600 Go
Date: Sat, 17 Jan 2015 00:29:33 +0000 [thread overview]
Message-ID: <bug-62305-8800-a9Soua3tJC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-62305-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 657 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=62305
Pierre Moreau <pierre.morrow-GANU6spQydw@public.gmane.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #3 from Pierre Moreau <pierre.morrow-GANU6spQydw@public.gmane.org> ---
I'm not sure if HDMI audio support was added for NV4B, but it might be worth
trying a recent kernel (3.18, 3.19-rc4).
If it still doesn't work, please provide the traces Ilia asked for.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1948 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2015-01-17 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 17:51 [Bug 62305] New: No HDMI Audio out (pass-thru) on Geforce 7600 Go bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-62305-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-03-13 17:56 ` [Bug 62305] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 14:39 ` [Bug 62305] [NV4B] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17 0:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-12-04 8:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-62305-8800-a9Soua3tJC@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.