From: Marcel Holtmann <marcel@holtmann.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA Mailing List <alsa-devel@lists.sourceforge.net>
Subject: Re: IO plugin and multiple poll descriptors
Date: Wed, 18 May 2005 15:45:11 +0200 [thread overview]
Message-ID: <1116423911.10063.257.camel@pegasus> (raw)
In-Reply-To: <s5hpsvosm8m.wl@alsa2.suse.de>
Hi Takashi,
> > > > What happens at the moment when I really return two poll_fd.
> >
> > What about this one?
>
> The poll_descriptors_count and poll_descriptors should return 2,
> for example,
>
> int my_poll_descriptors_count(snd_pcm_ioplug_t *io)
> {
> return 2;
> }
>
> int my_poll_descriptors(snd_pcm_ioplug_t *io, struct pollfd *pfds,
> unsigned int space)
> {
> if (space < 2) {
> error("Too little pfd\n");
> return 0;
> }
> pfds[0].fd = fd0;
> pfds[0].events = POLLOUT | POLLERR | POLLNVAL
> pfds[1].fd = fd1;
> pfds[0].events = POLLIN | POLLERR | POLLNVAL
> return 2;
> }
I know, but what I meant was if both descriptors are handled inside the
library. Previous you said that multiple descriptors are not supported.
Of did I understand that wrong?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
next prev parent reply other threads:[~2005-05-18 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 16:16 IO plugin and multiple poll descriptors Marcel Holtmann
2005-05-17 8:51 ` Takashi Iwai
2005-05-17 13:03 ` Marcel Holtmann
2005-05-17 16:15 ` Takashi Iwai
2005-05-18 11:03 ` Takashi Iwai
2005-05-18 12:05 ` Marcel Holtmann
2005-05-18 12:36 ` Takashi Iwai
2005-05-18 12:56 ` Marcel Holtmann
2005-05-18 13:21 ` Takashi Iwai
2005-05-18 13:45 ` Marcel Holtmann [this message]
2005-05-18 13:50 ` Takashi Iwai
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=1116423911.10063.257.camel@pegasus \
--to=marcel@holtmann.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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.