From: Raymond <rayau@netvigator.com>
To: openvortex-dev@nongnu.org
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [Openvortex-dev] aplay - How to use device 3 of card 0 ?
Date: Mon, 07 Mar 2005 15:54:53 +0800 [thread overview]
Message-ID: <422C08CD.2000200@netvigator.com> (raw)
>> 2) How did you perform your "WT DMA" test ?
>Using:
>aplay -d hw:0,1 test.wav
>The result for me was that aplay did newer finish, because data was
>never being transfered. After some time it timed out with an error.
http://savannah.nongnu.org/cgi-bin/viewcvs/openvortex/alsa/pci/au88x0/au88x0_pcm.c.diff?r1=1.9&r2=1.10
#define VORTEX_PCM_TYPE(x) (x->name[40])
http://cvs.sourceforge.net/viewcvs.py/alsa/alsa-kernel/pci/au88x0/au88x0_pcm.c?rev=1.6&view=markup
snd_vortex_new_pcm()
{
...
strcpy(pcm->name, vortex_pcm_name[idx]);
chip->pcm[idx] = pcm;
// This is an evil hack, but it saves a lot of duplicated code.
VORTEX_PCM_TYPE(pcm) = idx;
pcm->private_data = chip;
...
}
Added debug statement in snd_vortex_pcm_open()
/* Avoid PAGE_SIZE boundary to fall inside of a period. */
if ((err =
snd_pcm_hw_constraint_pow2(runtime, 0,
SNDRV_PCM_HW_PARAM_PERIOD_BYTES)) < 0)
return err;
+ printk(KERN_INFO "vortex_pcm_open()
%d\n",VORTEX_PCM_TYPE(substream->pcm));
if (VORTEX_PCM_TYPE(substream->pcm) != VORTEX_PCM_WT) {
Don't know why VORTEX_PCM_TYPE(substream->pcm) is always zero when using
"aplay -d hw:0,1 test.wav" or "aplay -d hw:0,3 test.wav"
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-03-07 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 7:54 Raymond [this message]
2005-03-07 12:22 ` Re: [Openvortex-dev] aplay - How to use device 3 of card 0 ? Manuel Jander
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 9:17 Raymond
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=422C08CD.2000200@netvigator.com \
--to=rayau@netvigator.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=openvortex-dev@nongnu.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