All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Manuel Jander <mjander@embedded.cl>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Recording
Date: Wed, 26 Mar 2003 18:13:05 +0100	[thread overview]
Message-ID: <s5hwuimnja6.wl@alsa2.suse.de> (raw)
In-Reply-To: <3E7D4F73.4040603@embedded.cl>

At Sun, 23 Mar 2003 02:08:51 -0400,
Manuel Jander wrote:
> 
> Hello,
> 
> I'm having serious trouble implementing record support into the Aureal 
> Vortex driver.
> I get total lockups...
> 
> The obvious answer would be: the cards overwrites your kernel :) ... but 
> i double checked
> that. If that would be the case, playback wouldnt work either (i would 
> hear noise, or at least a crack).
> I'm using the same operator functions (callbacks) for recording and 
> playback with some very few
> branch code to decide between record and playback.
> 
> Is there something like a typical pitfal list ? Any important difference 
> when recording
> instead of playback ?

i don't know of any big differences between playback and capture
except for the hardwares which need buffer copy.

> Can i use runtime->dma_addr just as when doing 
> playback for
> the DMA address programmed into the SoundCard ?

yes.

hmm, what i would check are

- the buffer allocation and the hardware config are ok?
	-> check debug print in prepare()
- interrupts properly acknowledged?
	-> check the interrupt handler
- any spin dead locks?
	-> removing locks first (for UP)

and if alt+sysrq works, you can get the trace.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en

      reply	other threads:[~2003-03-26 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-23  6:08 Recording Manuel Jander
2003-03-26 17:13 ` Takashi Iwai [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=s5hwuimnja6.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mjander@embedded.cl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.