linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: chuckw@ieee.org
To: linux-c-programming@vger.kernel.org
Subject: Re: Sound Programming and Signals
Date: Thu, 13 Jun 2002 21:25:42 -0400	[thread overview]
Message-ID: <20020613212542.A24845@whatever.local> (raw)
In-Reply-To: <15625.4880.647809.617013@cerise.nosuchdomain.co.uk>; from glynn.clements@virgin.net on Thu, Jun 13, 2002 at 10:48:00PM +0100

On Thu, Jun 13, 2002 at 10:48:00PM +0100, Glynn Clements wrote:
> 
> Chuck Winters wrote:
> 
> > I am trying to write a program which get a SIGIO signal from a
> > sound device, and then selects on the fd to decide if the device
> > can accept write, read, exception data.  The problem is that
> > it doesn't seem like the device every raises a SIGIO signal.  If
> > I do a kill -SIGIO <test_pid>, my handler runs.  Anyone have any ideas?
> 
> 1. Did you set the O_ASYNC flag on the descriptor, either in the call
> to open(), or with a subsequent call to fcntl(fd, F_SETFL, O_ASYNC)?
I used fcntl(fd, F_SETFL, f_flags|F_ASYNC)
after I used the F_SETOWN fcntl.  
> 
> 2. Did you set the target process ID with fcntl(fd, F_SETOWN, pid)?
> 
> If you have done both of these, but you still don't receive SIGIO,
> then I would suspect that it's a limitation of the sound card driver.
That really sucks then.  I thought all the drivers would support that.

Thanks
Chuck

      reply	other threads:[~2002-06-14  1:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 19:41 Sound Programming and Signals Chuck Winters
2002-06-13 21:48 ` Glynn Clements
2002-06-14  1:25   ` chuckw [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=20020613212542.A24845@whatever.local \
    --to=chuckw@ieee.org \
    --cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).