From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Apostolos Dimitromanolakis <apostolos@aei.ca>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Prodigy 7.1 ?
Date: Sat, 18 Oct 2003 02:07:12 +0100 [thread overview]
Message-ID: <3F909240.8040505@superbug.demon.co.uk> (raw)
In-Reply-To: <3F8F8EEB.4000303@aei.ca>
Does this card have something to do with EGOSYS ?
Apostolos Dimitromanolakis wrote:
>
> Takashi Iwai wrote:
>
>>> The Prodigy 7.1 is identically the same card as the Aureon Space
>>> 7.1....just different firmware and digital coaxial instead of toslink.
>>>
>>
>>
>> then you can fake the subvendor id (VT1724_SUBDEVICE_AUREON71_SPACE)
>> defined in aureon.h by replacing it with your card's id, which is
>> shown in the EEPROM output in /proc/asound/card0/ice1724.
>>
>> we might need to tune up eeprom entries to match with the actual
>> hardware, but in theory it should be ok as it is.
>>
>>
>
> Unfortunately I tried that and it doesn't work. A patch was needed since
> the reported eeprom size was 120 and no provision was made for that. I
> was able to get an eeprom dump and it doesn't look quite as the data for
> the aureon eeprom:
>
> EEPROM dump: 45 53 49 33 78 78 78 78 45 47 4f 53 59 53 ff ff ff ff ff ff
in ASCII: ESI3xxxxEGOSYS (Do EGOSYS make the card?)
>
> Module loads and report ICE1724 at ALSA but no sound at all. The
> following errors appear:
>
> PCI: Found IRQ 11 for device 00:0a.0
> invalid EEPROM version 120
> AC'97 0:0 does not respond - RESET
> ice1712: cannot initialize pro ac97, skipped
>
> and here is the lspci data (after module loaded):
>
> 00:0a.0 Multimedia audio controller: IC Ensemble Inc ICE1724 [Envy24HT]
> (rev 01)
> Subsystem: Unknown device 4933:4553
> Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32
> Interrupt: pin A routed to IRQ 11
> Region 0: I/O ports at a000 [size=32]
> Region 1: I/O ports at 9800 [size=128]
> Capabilities: [80] Power Management version 1
> Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 00: 12 14 24 17 05 00 10 02 01 00 01 04 00 20 00 00
> 10: 01 a0 00 00 01 98 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 33 49 53 45
ASCII: 3ISE ( The exact reverse of ESI3 in the EEPROM.)
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
prev parent reply other threads:[~2003-10-18 1:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 0:02 Prodigy 7.1 ? Apostolos Dimitromanolakis
2003-10-15 12:41 ` Liam Girdwood
2003-10-15 13:00 ` Takashi Iwai
2003-10-15 14:35 ` Mark Hubbard
2003-10-15 14:35 ` Takashi Iwai
2003-10-17 6:40 ` Apostolos Dimitromanolakis
2003-10-17 9:53 ` Takashi Iwai
2003-10-18 1:07 ` James Courtier-Dutton [this message]
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=3F909240.8040505@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=apostolos@aei.ca \
/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