From: Pavel Hofman <pavel.hofman@insite.cz>
To: alsa-devel@alsa-project.org
Subject: ICE1724 - File descriptor in bad state when capturing
Date: Sun, 09 Mar 2008 23:56:01 +0100 [thread overview]
Message-ID: <47D46B01.8020009@insite.cz> (raw)
Hi,
I have most of the ESI Juli driver working, but I have hit a problem
with the capture stream. I had to modify some ice1724.c code to allow
redefining clock-related functions in the actual card file (Juli has a
different clocking scheme), but all the DMA code is left intact, as well
as the methods defining the capture stream.
The ice1724 vu-meters detect input ADC data, I can hear correct sound
when setting the internal mixer to H/W-In. Yet, when trying to record, I get
arecord -v -D hw:0,0,0 -r 44100 -f S32_LE -c2
....
RIFF$WAVEfmt ... data arecord: pcm_read:1346: read error: File
descriptor in bad state
At the same time, my second Envy24-based card Prodigy192 (uses the
original methods in ice1724.c) works OK, arecord gives no errors.
Swapping the cards using the model parameter (to swap the
/dev/snd/pcmCXDXc device file) makes no difference.
Thank you for any hints of where I should focus my attention to. I am
not attaching the patches, as they are rather complicated. If you find
that important, I will send the preliminary version.
Pavel Hofman.
next reply other threads:[~2008-03-09 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 22:56 Pavel Hofman [this message]
2008-03-10 11:08 ` ICE1724 - File descriptor in bad state when capturing Takashi Iwai
2008-03-10 21:39 ` Pavel Hofman
2008-03-11 7:35 ` Clemens Ladisch
2008-03-11 13:25 ` Pavel Hofman
[not found] ` <47D63D6A.10503@insite.cz>
2008-03-11 15:11 ` Clemens Ladisch
2008-03-11 15:21 ` Pavel Hofman
2008-03-11 19:46 ` Pavel Hofman
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=47D46B01.8020009@insite.cz \
--to=pavel.hofman@insite.cz \
--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.