From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000194]: Prodigy 192 - Eprom incorrect size?
Date: Tue, 9 Nov 2004 16:19:26 +0100 [thread overview]
Message-ID: <023acefe925bb019d9d9ec78d2075c07@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=194>
======================================================================
Reported By: jvlake
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 194
Category: PCI - ice1724
Reproducibility: always
Severity: feature
Priority: normal
Status: closed
Distribution: RedHat 9 _ 2.4.20.8
Kernel Version: RedHat9 _ 2.4.20.8
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 04-07-2004 06:06 CEST
Last Modified: 11-09-2004 16:19 CET
======================================================================
Summary: Prodigy 192 - Eprom incorrect size?
Description:
after compiling the driver and rebooting i get a message that the eprom is
the wrong size for my card (on startup) needless to say, I also get no
sound. I am assuming this is because this card is not a 'prodigy 7.1' but
a 'prodigy 192' even though both cards are made by Audiotrak are 24/192khz
& 7.1. to look at the cards they are almost identical. is there anyway I
can get the driver to work?
======================================================================
----------------------------------------------------------------------
co2b - 09-07-04 16:37
----------------------------------------------------------------------
Prodigy192 uses Sigmatel STAC9460 audio codec, so Prodigy7.1 driver does
not work.
STAC9460 data sheet is here:
http://www.sigmatel.com/products/technical_docs.htm#9460
I wrote a patch for this card (it is against Linux-2.6.8-rc2).
----------------------------------------------------------------------
perex - 09-07-04 17:03
----------------------------------------------------------------------
The patch was applied to CVS. Thanks.
Issue History
Date Modified Username Field Change
======================================================================
04-07-04 06:06 jvlake New Issue
04-07-04 06:06 jvlake Distribution => RedHat 9 _ 2.4.20.8
04-07-04 06:06 jvlake Kernel Version => RedHat9 _ 2.4.20.8
04-07-04 06:09 jvlake Note Added: 0000760
04-07-04 06:10 jvlake Issue Monitored: jvlake
04-07-04 19:47 perex Category PCI - ice1712 => PCI -
ice1724
04-07-04 19:53 perex Severity major => feature
04-07-04 19:53 perex Status new => confirmed
04-07-04 19:54 perex Note Added: 0000763
04-16-04 16:00 tiwai Note Added: 0000838
06-18-04 17:45 Apostolos DimitromanolakisNote Added: 0001319
06-18-04 18:01 Apostolos DimitromanolakisIssue Monitored: Apostolos
Dimitromanolakis
09-07-04 16:37 co2b Note Added: 0001711
09-07-04 16:38 co2b File Added: linux-2.6.8-rc2-prodigy192.patch
09-07-04 17:03 perex Status confirmed => resolved
09-07-04 17:03 perex Resolution open => fixed
09-07-04 17:03 perex Assigned To => perex
09-07-04 17:03 perex Note Added: 0001719
11-09-04 16:19 tiwai Status resolved => closed
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next reply other threads:[~2004-11-09 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 15:19 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-07 15:03 [ALSA - driver 0000194]: Prodigy 192 - Eprom incorrect size? bugtrack
2004-09-07 14:37 bugtrack
2004-06-18 15:45 noreply
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=023acefe925bb019d9d9ec78d2075c07@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