From: Peter Niemayer <niemayer@isg.de>
To: alsa-devel@alsa-project.org
Subject: spdif/iec958 outputs at VT1708S not recognized
Date: Wed, 29 Apr 2009 14:25:28 +0200 [thread overview]
Message-ID: <gt9gvo$ocq$1@ger.gmane.org> (raw)
Hi,
I recently installed an Asus M4N78 mainboard, that uses a
nVidia GeForce 8300 chipset and a VT1708S soundchip.
Alas, the code in pci/hda/patch_via.c did not recognize
the 3 existing iec958/spdif outputs, and presented only
the analog devices.
I had to short circuit the pin definition
in vt1708S_parse_auto_config() to get the digital outputs
to work:
spec->multiout.max_channels = spec->multiout.num_dacs * 2;
- if (spec->autocfg.dig_out_pin)
+ // test fails for Asus M4N78 if (spec->autocfg.dig_out_pin)
spec->multiout.dig_out_nid = VT1708S_DIGOUT_NID;
spec->extra_dig_out_nid = 0x15;
The digital sound output works just fine for me with this change,
but I guess there should be a cleaner way to make this work?
Several people in forums on the InterNet reported similar problems
with getting their digital outputs on VT1708S to work under Linux.
Regards,
Peter Niemayer
next reply other threads:[~2009-04-29 13:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 12:25 Peter Niemayer [this message]
2009-04-29 15:07 ` spdif/iec958 outputs at VT1708S not recognized Takashi Iwai
2009-05-05 10:48 ` Peter Niemayer
2009-05-07 14:17 ` Takashi Iwai
2009-05-07 14:17 ` Takashi Iwai
2009-05-08 9:21 ` Peter Niemayer
2009-05-08 9:30 ` Takashi Iwai
2009-05-11 8:56 ` Peter Niemayer
2009-04-29 15:19 ` David Douglas
2009-04-29 16:41 ` Vedran Miletić
-- strict thread matches above, loose matches on Subject: below --
2009-05-24 4:24 linux user
2009-05-26 3:04 Sentinel
2009-05-26 14:24 Sentinel
2009-05-27 2:57 Sentinel
2009-05-27 5:35 ` Takashi Iwai
[not found] ` <003401c9dee9$322399f0$966acdd0$@net>
2009-05-27 16:51 ` Takashi Iwai
2009-05-27 3:19 Sentinel
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='gt9gvo$ocq$1@ger.gmane.org' \
--to=niemayer@isg.de \
--cc=alsa-devel@alsa-project.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.