From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001732]: Support for Intel D945Pvs Board
Date: Wed, 11 Jan 2006 18:30:34 +0100 [thread overview]
Message-ID: <e3da7284c4b571dac7de93d9ec02814f@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1732>
======================================================================
Reported By: timtt
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1732
Category: PCI - hda-intel
Reproducibility: always
Severity: feature
Priority: normal
Status: assigned
Distribution: FC4
Kernel Version: 2.6.14-1656
======================================================================
Date Submitted: 01-11-2006 04:53 CET
Last Modified: 01-11-2006 18:30 CET
======================================================================
Summary: Support for Intel D945Pvs Board
Description:
Alsa is only able to output regular 2-channel audio via the headphone jack
at the back of this motherboard. This motherboard has an SPDIF connection
available that is currently not supported, but should be.
======================================================================
----------------------------------------------------------------------
rlrevell - 01-11-06 05:04
----------------------------------------------------------------------
Did you try the various "model" options for hda-intel which are documented
in ALSA-Configuration.txt?
----------------------------------------------------------------------
timtt - 01-11-06 18:30
----------------------------------------------------------------------
I have not. I just looked at it though and am unsure on how to do so. Could
you give me the correct syntax to enable the "5stack-digout" directive for
either /etc/modprobe.conf or for doing it on the shell loading and
unloading modules?
I'm sorry that I'm not so familiar with how modules work in the Linux
kernel. Thanks.
Issue History
Date Modified Username Field Change
======================================================================
01-11-06 04:53 timtt New Issue
01-11-06 04:53 timtt Distribution => FC4
01-11-06 04:53 timtt Kernel Version => 2.6.14-1656
01-11-06 05:04 rlrevell Note Added: 0007558
01-11-06 18:30 timtt Note Added: 0007563
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-11 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 17:30 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-10 14:40 [ALSA - driver 0001732]: Support for Intel D945Pvs Board bugtrack
2006-04-09 21:30 bugtrack
2006-04-09 21:19 bugtrack
2006-01-20 21:47 bugtrack
2006-01-11 17:36 bugtrack
2006-01-11 4:04 bugtrack
2006-01-11 3:53 bugtrack
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=e3da7284c4b571dac7de93d9ec02814f@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox