Hi,
I had again some time to write an audio driver for the AMD Au1500 CPU.
I can already initalize the device and create the nodes.
Using the wave.c and some .wav files makes already some noise which
sounds a little bit like the .wav files, but it’s either much too fast
or always just the beginnings of the frames…
If I play around with the max frame rate (normally set to max 8160) the
sound system access the _trigger function with cmd==ADO_PCM_TRIGGER_GO
The function returns EOK. Afterwards there is no sound/noise anymore
and my wave application seems to hang. pidin shows it is on sigwaitinfo.
Do I have to send some signal to the sound system to allow it to
proceed with playback or something else???
Tiemo
Hmmm - maybe you are giving the wrong information by telling us it is an
Au 1500 CPU. This means next to nothing…
This chip is a MIPS chip - this means something…
This chip has not integrated sound, so what sound chip/mechanism are you
using? This too means something…
The Au1500 has a controller for an AC97-Codec. I have an AC97 codec
attached to the Au1500 via the internal AC97 controller in the Au1500.
Tiemo
In article <blgrbt$39k$1@inn.qnx.com>, tk@mycable.de says…
Hi,
I had again some time to write an audio driver for the AMD Au1500 CPU.
I can already initalize the device and create the nodes.
Using the wave.c and some .wav files makes already some noise which
sounds a little bit like the .wav files, but it’s either much too fast
or always just the beginnings of the frames…
If I play around with the max frame rate (normally set to max 8160) the
sound system access the _trigger function with cmd==ADO_PCM_TRIGGER_GO
The function returns EOK. Afterwards there is no sound/noise anymore
and my wave application seems to hang. pidin shows it is on sigwaitinfo.
Do I have to send some signal to the sound system to allow it to
proceed with playback or something else???
Tiemo
Hmmm - maybe you are giving the wrong information by telling us it is an
Au 1500 CPU. This means next to nothing…
This chip is a MIPS chip - this means something…
This chip has not integrated sound, so what sound chip/mechanism are you
using? This too means something…
–
Stephen Munnings
Developer
Corman Technologies Inc.
In article <blhaq3$dk3$1@inn.qnx.com>, tk@mycable.de says…
Hmmm - maybe you are giving the wrong information by telling us it is an
Au 1500 CPU. This means next to nothing…
This chip is a MIPS chip - this means something…
This chip has not integrated sound, so what sound chip/mechanism are you
using? This too means something…
The Au1500 has a controller for an AC97-Codec. I have an AC97 codec
attached to the Au1500 via the internal AC97 controller in the Au1500.
Tiemo
My humble apologies, I had forgotten that and missed the obvious
connection. Sorry.
–
Stephen Munnings
Developer
Corman Technologies Inc.
If I have a big fragmentation size (which is of course higher then my
technical limit), a short
…wav file is played completely, but because of the wrong frag size the
output sounds of
course corrupted. I don’t see any access to the trigger function. The
playback returns
correctly, I still have my shell and can even repeat the playback.
If I reduce frag size and play the same .wav, then the trigger function
is called and it
definitly returns EOK (I tried it even with delay inside). From my point
of view
io-audio should proceed to write data to the previously given address
again after
trigger returns.
Unfortunatly after trigger returns EOK I don’t see anything anymore and
nothing happens,
I loose the shell, so QNX seems to hang. This is, what is irritating me…
For a lot of parameters I miss if this parameter should be given in Byte
or perhaps in Bit.
Can I assume that everytime it is not written in the documentation, that
it is Byte?
Tiemo
Stephen Munnings wrote:
In article <blhaq3$dk3$> 1@inn.qnx.com> >, > tk@mycable.de > says…
Hmmm - maybe you are giving the wrong information by telling us it is an
Au 1500 CPU. This means next to nothing…
This chip is a MIPS chip - this means something…
This chip has not integrated sound, so what sound chip/mechanism are you
using? This too means something…
The Au1500 has a controller for an AC97-Codec. I have an AC97 codec
attached to the Au1500 via the internal AC97 controller in the Au1500.
Tiemo
My humble apologies, I had forgotten that and missed the obvious
connection. Sorry.
red-faced