From: Magnus Sandin <magnus@sandin.cx>
To: alsa-devel@lists.sourceforge.net
Subject: S/PDIF indication wrong?
Date: Sat, 19 Aug 2006 09:37:01 +0200 [thread overview]
Message-ID: <44E6BF9D.1090903@sandin.cx> (raw)
Hello!
On my ASUS P5P800-VM motherboard, the onboard AC97-chip (Realtek ALC655)
does not indicate that there are any S/PDIF functionality available.
However, the manufacturer (Asus) claim that there are S/PDIF output on
the board, and of course there is.
I created a patch that check the PCI subsystem vendor id and device id,
and if it's a match to this board it ignores the AC97_EI_SPDIF bit when
the controls are built.
This allows me to get the desired S/PDIF output to work just as expected.
I'm not sure this is good practise to just ignore this bit or force the
bit to 1?
I have checked the BIOS for settings regarding S/PDIF, but there are
none. The only audio setting available is to control if the chip shall
be enabled or disabled.
What do you recommend in this case?
You can find more information about this issue on the bugtracker:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2372
Regards
// Magnus
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-08-19 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-19 7:37 Magnus Sandin [this message]
2006-08-19 14:01 ` S/PDIF indication wrong? Takashi Iwai
2006-08-21 20:11 ` [PATCH] Asus P5P800-VM, " Magnus Sandin
2006-08-22 11:22 ` Takashi Iwai
2006-08-22 19:57 ` Magnus Sandin
2006-08-23 9:50 ` Takashi Iwai
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=44E6BF9D.1090903@sandin.cx \
--to=magnus@sandin.cx \
--cc=alsa-devel@lists.sourceforge.net \
/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.