From: Shaju Abraham <shaju@multitech.co.in>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Calling snd_pcm_oss_write directly.
Date: Wed, 24 Jul 2002 15:47:38 +0530 [thread overview]
Message-ID: <3D3E7EC2.E28C98AF@multitech.co.in> (raw)
In-Reply-To: s5hr8hwovno.wl@alsa2.suse.de
Hi all,
I am in a situation where I intend to call snd_pcm_oss_write
directly.
What exactly happens is - the open and all the initial ioctl calls are
done by the oss application. But the write call of the oss application
is not done but it is done by some other task.
So what I do is, when snd_pcm_oss_open gets called, I store the
-- struct file *file -- in my own pointer, say, gfile.
Then I use this pointer, -gfile- in snd_pcm_oss_write() when I call the
function directly. But apparently this much is not enough. The direct
write call crashes. If you can please tell me what else needs to be
done for the call to get through, it will be of great help.
--Shaju Abraham
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-24 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200207201425.KAA12713@bromo.msbb.uc.edu>
2002-07-22 11:21 ` fix for missing symbol in snd-ymfpci.o Takashi Iwai
2002-07-24 10:17 ` Shaju Abraham [this message]
2002-07-24 11:39 ` Calling snd_pcm_oss_write directly Paul Davis
2002-07-24 14:49 ` Inserting modules on the run Shaju Abraham
2002-07-24 23:54 ` Patrick Shirkey
2002-07-24 18:10 ` Calling snd_pcm_oss_write directly Jaroslav Kysela
[not found] <200207241129.g6OBTIbt000943@multitech.co.in>
2002-07-24 14:27 ` Shaju Abraham
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=3D3E7EC2.E28C98AF@multitech.co.in \
--to=shaju@multitech.co.in \
--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.