From: Rui Sousa <rsousa@grad.physics.sunysb.edu>
To: linux-sound@vger.kernel.org
Subject: Re: File descriptors and Sound
Date: Mon, 09 Aug 1999 14:57:08 +0000 [thread overview]
Message-ID: <marc-linux-sound-93421235323784@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93415570309034@msgid-missing>
Alan Cox wrote:
>
> > If the device is full-duplex how can I have one application
> > reading it and another writing?
>
> You either do file handle passing (funky) or normally one program runs the
> other: ie
>
> open file
> fork()
>
> child:
> exec other app (which inherits file)
> exit
>
> parent:
> run code
As I said before I'm trying to get speakfreely to work in full-duplex
mode.
This program has two components (two independent processes) that try to
access /dev/audio. The thing is that during execution they open/close
/dev/audio multiple times so I think that the second method wont work
(correct me if I am wrong).
Can you indicate me some (online) documentation concerning file handle
passing?
Thanks
--
Rui Sousa
next prev parent reply other threads:[~1999-08-09 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-08 23:48 File descriptors and Sound Rui Sousa
1999-08-08 23:53 ` Alan Cox
1999-08-09 14:57 ` Rui Sousa [this message]
1999-08-09 16:40 ` Matthew Wilcox
1999-08-13 12:41 ` Benno Senoner
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-93421235323784@msgid-missing \
--to=rsousa@grad.physics.sunysb.edu \
--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 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.