From: Benno Senoner <sbenno@gardena.net>
To: linux-sound@vger.kernel.org
Subject: Re: [linux-audio-dev] full-duplex
Date: Mon, 11 Oct 1999 15:45:29 +0000 [thread overview]
Message-ID: <marc-linux-sound-93968252431691@msgid-missing> (raw)
On Mon, 11 Oct 1999, Paul Barton-Davis wrote:
> >ALSA:
> >Won't compile with gcc-2.95 but it's probably similar to OSS/Free.
>
> ALSA:
> 1) open the device O_RDWR. then use it the way you'd expect,
> independent of the card type or anything else.
>
> OSS/Free or OSS/Commercial:
> 1) forget about it for full-duplex. its just not reliable and/or too
> card dependent.
>
> --p
Hi,
Paul gave me a code fragment to use the soundcard in fullduplex mode,
(My old code were not able to perform DSP_SET_FRAGMENT, because
of wrong order of soundcard initialization).
But my Turtlebeach on my P133 with Tyan Tomcat motherboard (HX)
locks up the kernel some times.
( I tried 2.2.5 and 2.2.10 )
Is this due to a hw problem of buggy mainboards (from the Audio-quality HOWTO
:-) ) ?
Is there a workaround for OSS/Free ?
Does have ALSA the same problems ?
thanks for infos.
regards,
Benno.
next reply other threads:[~1999-10-11 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-11 15:45 Benno Senoner [this message]
1999-10-12 2:02 ` [linux-audio-dev] full-duplex Paul Barton-Davis
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=marc-linux-sound-93968252431691@msgid-missing \
--to=sbenno@gardena.net \
--cc=linux-sound@vger.kernel.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