Re: [Alsa-devel] SPDIF output finally working properly with CS4630
On 2002.07.24 14:53 Benny Sjostrand wrote: >> MasterMixSCB: >> 0090 1478 0094 >> 0098 0080 00A0 809A 00C3 009C >> 14F8 80008000 80007FFF > The 9th Dword in SCB is the sub_list_ptr which points > to the SCB's child SCB. Which is in this case is 00A0 > which points to the SRCTaskSCB (sample rate converter). > When SPDIF output is muted the MasterMixSCB sub_list_ptr > is 00A0 -> SRCTaskSCB, and when SPDIF output is unmuted > sub_list_ptr is 0x00E0 AsynchFGTxSCB. > In the moment of this dump the SPDIF seems to be muted. I can watch what you're saying as I mute and unmute "IEC 958" in alsamixer. Muted, the 9th dword is 00a0, unmuted it's 00e0. Side question: you referenced AsynchFGTxSCB. What's the FGT acronym stand for?) >> 0bc0 SPDIFOSCB: >> 00b0 0086 1820fffc >> 0600 0bcd020f 0040 20ff 804c 00010108 deadc0ed > First dword 0, SPDIF output inactive. Here's a strange one. With "IEC 958" muted, I view dsp_scb, and the first dword of SPDIFOSCB is . I unmute "IEC 958", and I can watch the first dword of SPDIFOSCB change each time I view dsp_scb. Here's a list of each individual number I get (duplicates have been removed): 80005001 80001001 8001 80002001 1001 80003001 80006001 6001 3001 4001 80003001 80004001 0001 7001 80005001 5001 80007001 2001 5001 I tried this with and without sounds playing (though I still can't hear them). Do you have any information regarding what each bit stands for in the first dword of SPDIFOSCB? (if you do, could you point me to where you obtained this information so I can try to educate myself?) I'm writing this because it seems strange; I don't understand why the status bits would keep changing for no (apparent) reason. -- Peter Heatwole "Murphy was just a well known pessimist." --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
On 2002.07.24 16:37 Peter Heatwole wrote: >Looking at the datasheets and schematics, it looks like the CS4630 > uses > AC97 codecs to actually process and output it's iec958 frames. I could > easily be wrong, but the schematics for the CS4630-CM don't show the > circuitry necessary to power and control an iec958 line. It shows a pin, > which I assume links to the codec (in my case, a CS4297A). Is there > a datasheet that could show me what you mean? Hmm. Seems like I'm wrong. I just remembered you mentioned that the Game Theatre only has 2 CS4294 codecs, which suggests that the CS4630 does indeed have it's own iec958 output pin. I wish I understood schematics better. The one I was looking at must have just generalized and I took it literally. -- Peter Heatwole "Murphy was just a well known pessimist." --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
On 2002.07.24 14:53 Benny Sjostrand wrote: > Well, if you have access to a oscilloscope that can be programed to view > the differential result > of the signals then probably you can proably view the digital data. > But i've never tested to do this, and don't have any access to a > oscilloscope at home ... Neither do I. =) > Then, do you know if your IEC958 is connected to CS4297A or CS4630 ?? > If it is connected to the CS4297A then this patch will not provide any > output on that IEC958 port. Looking at the datasheets and schematics, it looks like the CS4630 uses AC97 codecs to actually process and output it's iec958 frames. I could easily be wrong, but the schematics for the CS4630-CM don't show the circuitry necessary to power and control an iec958 line. It shows a pin, which I assume links to the codec (in my case, a CS4297A). Is there a datasheet that could show me what you mean? [...] > This dump should not be that long! > Did you change anything in the code ? the SCB block > has always a fixed size of 16 Dwords. A new SCB block will > start on 0x0050. No, I haven't changed a thing. > Well, that's what i can interpret from this outputs. > > Everything look basically OK. > Seems like you have loaded the module successfully and have not started > playing yet. Strange. Well, if it _were_ the case that my card is using a CS4297A for digital output, do you think that would cause this? -- Peter Heatwole "Murphy was just a well known pessimist." --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
>The IEC958 control is supposed to be there because of the CS4297A > codec. > Your changes only involved the CS4297. >My IEC958 is coaxial, and I'm using a set of Cambridge SoundWorks > DTT2500 Digital speakers. I don't know of any other way to check if > the card is sending a signal or not. Well, if you have access to a oscilloscope that can be programed to view the differential result of the signals then probably you can proably view the digital data. But i've never tested to do this, and don't have any access to a oscilloscope at home ... > >I've attached a few files that may help. I just noticed some module > errors that may be the cause of my problems. Then, do you know if your IEC958 is connected to CS4297A or CS4630 ?? If it is connected to the CS4297A then this patch will not provide any output on that IEC958 port. . >WriteBackSCB: >0040 3FCF 0301 00010400 >0044 >0048 00B0 00D0806D 330480C3 >004C 0480 0003 0083 >0050 >0054 >0058 >005C >0060 >0064 >0068 >006C > This dump should not be that long! Did you change anything in the code ? the SCB block has always a fixed size of 16 Dwords. A new SCB block will start on 0x0050. > >MasterMixSCB: >0090 1478 >0094 >0098 0080 00A0 809A 00C3 >009C 14F8 80008000 80007FFF > The 9th Dword in SCB is the sub_list_ptr which points to the SCB's child SCB. Which is in this case is 00A0 which points to the SRCTaskSCB (sample rate converter). When SPDIF output is muted the MasterMixSCB sub_list_ptr is 00A0 -> SRCTaskSCB, and when SPDIF output is unmuted sub_list_ptr is 0x00E0 AsynchFGTxSCB. In the moment of this dump the SPDIF seems to be muted. > >PCMREADER: >0600 ED42F99C EE6EF940 EFB0F8EF F0F6F8A9 >0610 F236F86E F372F83F F4AAF818 F5DDF7F5 >0620 F70DF7D1 F83AF7A6 F969F778 FAA3F742 >MIX_SAMPLE_BUF1: >1400 FF0BF666 FE8DF5C0 FE00F526 FD60F499 >1410 FCBFF421 FC1CF3BF FB76F36F FAD7F334 >1420 FA45F314 F9C4F30B F94FF319 F8EAF33E > >1780 >1790 >17A0 >17B0 >17C0 >17D0 >17E0 >17F0 >SPDIFO_BUFFER: >1800 >1810 >1820 >1830 >... >18D0 >18E0 >18F0 >1900 >OUTPUT_SNOOP: >1200 >1210 >1220 >1230 >... >12D0 >12E0 >12F0 >1300 > As the SPDIFO_BUFFER is empty nothing is going out to the SPDIF output. > >0090 MasterMixSCB: > 1400 > >0080 00a0 809a 00c3 >1480 80008000 80007fff > Here SPDIF still muted. > >0130 SPIOWriteSCB: >804d804d > > 0194 > > Last IO wroten by cs46xx_poke_via_dsp(...) was address 0x804d, and value 0x0 the 0x804d is the SP SPDOUT_CONTROL register, value 0 disables SPDIF. Probably cs46xx_dsp_disable_spdif_in() was invoked, is invoked at end of snd_cs46xx_chip_init(...) when module is initialized.. > >0bc0 SPDIFOSCB: > 00b0 > 0086 1820fffc > 0600 0bcd020f 0040 >20ff 804c 00010108 deadc0ed > First dword 0, SPDIF output inactive. >Jul 24 13:23:09 porky kernel: dsp_spos: downloading code to chip (00021470-00021570) >Jul 24 13:23:09 porky kernel: handle_wideop[1]: 01016:b8630 addr 02d7 >Jul 24 13:23:09 porky kernel: handle_wideop:[2] 01014:e8630 addr 029d >Jul 24 13:23:09 porky kernel: handle_wideop[1]: 01016:e03a0 addr 02dc >Jul 24 13:23:09 porky kernel: handle_wideop:[2] 01015:103a0 addr 02a2 >Jul 24 13:23:09 porky kernel: handle_wideop[1]: 01017:10730 addr 02e2 >Jul 24 13:23:09 porky kernel: handle_wideop:[2] 01015:40730 addr 02a8 >Jul 24 13:23:09 porky kernel: dsp_spos: 3 instructions real
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
On 2002.07.24 12:59 Benny Sjostrand wrote:
> The "IEC958" controll is probably there course my incorrect changes in
> ac97_codec.c that should not
> be there. The "ICE 958 output" control is the one from cs46xx_lib.c.
> Then how does the /proc/asound/card0/dsp_sample looks like when you
> playing a .WAV file ?
>
> If your IEC958 is optical and you see a red light it's a good sign.
The IEC958 control is supposed to be there because of the CS4297A
codec.
Your changes only involved the CS4297.
My IEC958 is coaxial, and I'm using a set of Cambridge SoundWorks
DTT2500 Digital speakers. I don't know of any other way to check if the
card is sending a signal or not.
I've attached a few files that may help. I just noticed some module
errors that may be the cause of my problems.
messages.txt: /var/log/messages after insmodding my module
-- Peter Heatwole
"Murphy was just a well known pessimist."
nullSCB:
0004
0008 0169
000C FE98
TimingMasterSCBInst:
0010
0014
0018 0020 8010
001C 00090001 8001 0001 0006
CodecOutSCB:
0020
0024
0028 00900080 0179
002C 0010 0080 0090
PCMreaderSCB:
0030 F2C0400F 0200 07B84900 00010600
0034
0038 0169 330300C2
003C 0620 80008000 80008000
WriteBackSCB:
0040 3FCF 0301 00010400
0044
0048 00B0 00D0806D 330480C3
004C 0480 0003 0083
0050
0054
0058
005C
0060
0064
0068
006C
SPOSCB:
0070 066A0BA0 06350070 0BAD 0BAD0BAD
0074 DEAD 0600
0078 DEAD 0001 DEADDEAD
007C 0BAD0BAD 0BAD0BAD 0BAD0BAD
CodecInSCB:
0080
0084
0088 0130 804F 00C3
008C 0578 00A00010 80008000
MasterMixSCB:
0090 1478
0094
0098 0080 00A0 809A 00C3
009C 14F8 80008000 80007FFF
SRCtaskSCBInst:
00A0 0029001B 0001 00C0 000107B8
00A4 00C80028 00C2 06A0 01CC
00A8 06840080 0030 80BB 00C9
00AC 07B8 03AC 80008000 80007FFF
VariDecimateSCB:
00B0 00C80028 0780
00B4 00C80028 00C5 FFEB
00B8 02400080 00C0 8197 00C9
00BC 0780 1800 80008000
PCMserialInSCB:
00C0
00C4
00C8 805E 00C1
00CC 0080 80008000 80008000
00D0
00D4
00D8
00DC
AsynchFGTxSCBInst:
00E0 07FFF800 01100610 0BC0
00E4 2AAB
00E8 00A0 00E4022B 00C6
00EC 1814 1800 80008000 80008000
AsynchFGRxSCBInst:
00F0 0000 03800380 0BB0
00F4
00F8 00F00252 00C3
00FC 0E00 80008000
0100
0104
0108
010C
OutputSnoopSCB:
0110
0114
0118 026F 00C3
011C 1200 0020
0120
0124
0128
012C
SPIOWriteSCB:
0130 804D804D
0134
0138 0194
013C
0140
0144
0148
014C
0150
0154
0158
015C
0160
0164
0168
016C 000
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
>It's different than your included output, but it's not zero's. And > yes, > I unmuted both entries "IEC958" and "IEC 958" with alsamixer. The "IEC958" controll is probably there course my incorrect changes in ac97_codec.c that should not be there. The "ICE 958 output" control is the one from cs46xx_lib.c. Then how does the /proc/asound/card0/dsp_sample looks like when you playing a .WAV file ? If your IEC958 is optical and you see a red light it's a good sign. /Benny --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
On 2002.07.24 11:41 Benny Sjostrand wrote: > About the IEC958, remember to unmute it via the ALSA mixer, it does not > apear > with the Gnome Mixer, or any other OSS mixer. > > When you are playing the .WAV file take a look in > /proc/asound/card0/dsp_scb > and check after the line "0bc0 SPDIFOSCB:", should be something like: It's different than your included output, but it's not zero's. And yes, I unmuted both entries "IEC958" and "IEC 958" with alsamixer. -- Peter Heatwole "Murphy was just a well known pessimist." --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
>This is odd. I was going to play with the driver some more this > morning, and when I tried to play a sound... it played! I didn't change > anything since I last tried it, except that I had my computer turned off > overnight. Perhaps it was the cold boot that effected it. Anyway, now it > plays, but I don't get IEC958 output, and the analog out was very > "tinny". I reloaded the module, and now the sound from analog out is > fine. >I'll keep playing with it. About the IEC958, remember to unmute it via the ALSA mixer, it does not apear with the Gnome Mixer, or any other OSS mixer. When you are playing the .WAV file take a look in /proc/asound/card0/dsp_scb and check after the line "0bc0 SPDIFOSCB:", should be something like: 0bc0 SPDIFOSCB: 80002001 00b0 0086 1a4afffc 0001 0600 0bcd020f 0040 20ff 0005804c 00010108 deadc0ed The first DWORD (80002001) monitors the SPDIF output status register, it should be different than 0 if SPDIF output is active. Then you can check the /proc/asound/card0/dsp_sample, should look something like: PCMREADER: 0600 0750FD6A 0763FD6C 0778FD6D 0781FD77 0610 0787FD8F 0797FDA3 07A4FDAD 07A1FDB9 0620 079CFDCB 07A0FDE0 07A5FDFB 07A7FE1A MIX_SAMPLE_BUF1: 1400 F95E0394 F94A039D F93F0395 F93A038B 1410 F934038A F92B038F F923039A F92703AB 1420 F93203C0 F93503DD F93303FC F9390415 1780 1790 17A0 17B0 17C0 17D0 17E0 17F0 SPDIFO_BUFFER: 1800 010EFF9F 0105FF9D 00F3FFAE 00DFFFCA 1810 00CEFFE9 00BF0015 00A90056 009000A7 1820 007C00FD 00680158 004D01BB 002B0222 1830 00080281 FFE402D7 FFB90325 FF8C0367 ... 18D0 FBFE0379 FBE30360 FBC50351 FBA6034B 18E0 FB880345 FB700341 FB610347 FB500355 18F0 FB320365 FB110370 FAF50378 FADC037D 1900 FAC1037D FAA40377 FA8D0369 FA790353 OUTPUT_SNOOP: 1200 1210 The SPDIFO_BUFFER part the values should be different than 0, and there is a stream. /Benny --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
On 2002.07.23 21:28 Benny Sjostrand wrote: >> [peter@porky als]$ aplay footsteps.wav Playing WAVE 'footsteps.wav' : >> Signed 16 bit Little Endian, Rate 44100 Hz, Mono >> aplay: interval_inline.h:65: snd_interval_min: Assertion >> `!snd_interval_empty(i)' failed. >> Aborted... This is odd. I was going to play with the driver some more this morning, and when I tried to play a sound... it played! I didn't change anything since I last tried it, except that I had my computer turned off overnight. Perhaps it was the cold boot that effected it. Anyway, now it plays, but I don't get IEC958 output, and the analog out was very "tinny". I reloaded the module, and now the sound from analog out is fine. I'll keep playing with it. -- Peter Heatwole "Murphy was just a well known pessimist." --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
Hi Benny, At Tue, 23 Jul 2002 22:33:38 +0200, Benny Sjostrand wrote: > > Hi! > > After a lot fustrated hacking nights and days, finally (at least) I > manage to get a properly sound out from SPDIF interface on my Hercules > Game Theater XP card, at least "so far as i can hear". The sound is no > longer distorcionated and SPDIF is now integrated with the ALSA mixer > (muted by default). great! i'll take a look, too. > About other missing basic feutures, SPDIF input, 4 channels, multi PCM > etc., well, I'm working on that, we see what I can do, at least there is > a hope ... yeah, 4 channels would be really nice. > The code is still very dirty, noisy, well, I know that it needs a lot of > cleanup. > > My new current snapshots: > http://www.cucumelo.org/~gorm/alsa-driver-0.9.0rc2-bs20020723.tar.gz > http://www.cucumelo.org/~gorm/ospparser.tar.gz ossparser could be put into alsa-tools package. > Please, test it and give some feedback, maybe there are things that was > working before > and are now broken., etc ... > > but, > NOTE the code is very EXPERIMENTAL and may be very UNSTABLE for the moment. Takashi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
On 2002.07.23 21:28 Benny Sjostrand wrote:
> Now I've generated a patch against alsa-driver-0.9.0rc2, so you can try
> to merge it with your CVS snapshot,
> maybe it works better
Thanks. It took a tad of modifying to patch the CVS because it was
expecting a 0.9.0rc2 postfix on everything, but that was simple to fix.
I patched the CVS, and am getting the same error. I stuck the following
into alsa-lib/src/pcm/interval_inline.h, and am getting some feedback on
what's going wrong:
printf("snd_interval_min()::: i->empty == %d\n", i->empty)
<<>>
[peter@porky als]$ aplay footsteps.wav Playing WAVE 'footsteps.wav' :
Signed 16 bit Little Endian, Rate 44100 Hz, Mono
snd_interval_min()::: i->empty == 0
snd_interval_min()::: i->empty == 0
snd_interval_min()::: i->empty == 0
snd_interval_min()::: i->emtpy == 0
snd_interval_min()::: i->empty == 1
aplay: interval_inline.h:66: snd_interval_min: Assertion
`!snd_interval_empty(i)' failed.
Aborted...
Also, I tried the driver with the xmms-alsa plugin, and it
failed the same test, but in the function snd_interval_refine_min().
I haven't developed with ALSA yet, so I don't know the ropes
completely. Anyone have any idea what's happening here? I checked
the online docs and couldn't find any references regarding
"interval"s. Is this a timing issue?
-- Peter Heatwole
"Murphy was just a well known pessimist."
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
> [peter@porky als]$ aplay footsteps.wav Playing WAVE 'footsteps.wav' : > Signed 16 bit Little Endian, Rate 44100 Hz, Mono > aplay: interval_inline.h:65: snd_interval_min: Assertion > `!snd_interval_empty(i)' failed. > Aborted... oops! I guess that maybe you need to alsa-lib-0.9.0rc2, everything *0.9.0rc2, thats what's i got installed. Now I've generated a patch against alsa-driver-0.9.0rc2, so you can try to merge it with your CVS snapshot, maybe it works better http://www.cucumelo.org/~gorm/alsa-driver-0.9.0rc2-bs20020723.diff.gz /Benny --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] SPDIF output finally working properly with CS4630
On 2002.07.23 13:33 Benny Sjostrand wrote: > About other missing basic feutures, SPDIF input, 4 channels, multi PCM > etc., well, I'm working on that, we see what I can do, at least there is > a hope ... [...] > Please, test it and give some feedback, maybe there are things that was > working before > and are now broken., etc ... I've downloaded and installed your driver, but it seems that something has changed in CVS since the rc2 release. Here's the error I'm getting: [peter@porky als]$ aplay footsteps.wav Playing WAVE 'footsteps.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono aplay: interval_inline.h:65: snd_interval_min: Assertion `!snd_interval_empty(i)' failed. Aborted... I'm using the CVS of all the ALSA packages. I'm very interested in S/PDIF output on my Santa Cruz, and will be watching your releases with earnest. One request, however: would you release the files by themselves? (versus the whole alsa-driver-0.9.0rc2 package) I didn't have time to check, but are you modifying anything beyond files in the pci/cs46xx folder? I tested the driver with CVS and your package as a whole, with the same response. Could it be something in alsa-lib that's changed? Good luck! -- Peter Heatwole "Murphy was just a well known pessimist." --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
