All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Bilien <bilien@imit.kth.se>
To: alsa-devel@alsa-project.org
Subject: Recording problem on cs46xx on recent linux kernels
Date: Fri, 10 Dec 2004 14:59:55 +0100	[thread overview]
Message-ID: <1102687196.10057.15.camel@localhost> (raw)

Hi,

since moving from kernel 2.6.9 to 2.6.10-rc2 and -rc2-bk4, I was happy
to see that hardware mixing is now supported on my hardware
(CrystalClear SoundFusion Audio Accelerator on a IBM T22). However I
have also been experiencing a new problem when recording from the
soundcard: a readi returns -5 after about 5 seconds, with parameters
that used to work. I'm using libalsa v1.0.7 (Debian unstable) and Linux
2.6.10-rc2-bk4 with cs46xx and "New DSP support".

The /proc says that the capture PCM is running, but the available field
remains to 0. 

10/12 14:56 /proc/asound/card0/pcm0c/sub0% cat status
state: RUNNING
trigger_time: 1102686881.461093000
tstamp      : 1102687019.388211000
delay       : 0
avail       : 0
avail_max   : 0
-----
hw_ptr      : 0
appl_ptr    : 0

10/12 14:57 /proc/asound/card0/pcm0c/sub0% cat hw_params
access: RW_INTERLEAVED
format: S16_LE
subformat: STD
channels: 2
rate: 8000 (8000/1)
period_size: 8
buffer_size: 320
tick_time: 1000

10/12 14:57 /proc/asound/card0/pcm0c/sub0% cat sw_params
tstamp_mode: NONE
period_step: 1
sleep_min: 0
avail_min: 8
xfer_align: 8
start_threshold: 1
stop_threshold: 2147483647
silence_threshold: 0
silence_size: 0
boundary: 1342177280

Thanks,
Johan.



-------------------------------------------------------
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://productguide.itmanagersjournal.com/

                 reply	other threads:[~2004-12-10 13:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1102687196.10057.15.camel@localhost \
    --to=bilien@imit.kth.se \
    --cc=alsa-devel@alsa-project.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 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.