All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaju Abraham <shaju@multitech.co.in>
To: Paul Davis <pbd@op.net>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@lists.sourceforge.net
Subject: Inserting modules on the run.
Date: Wed, 24 Jul 2002 20:19:34 +0530	[thread overview]
Message-ID: <3D3EBE7E.58C9604D@multitech.co.in> (raw)
In-Reply-To: E17XKRX-0007HC-00@usw-sf-list1.sourceforge.net

Hi all,
         This is about OSS emulation by ALSA.   When I modprobe my sound
card,  I find that the snd-pcm-oss.o and mixer-oss.o modules are not there
in the modules list.

But when an OSS application is run, how does ALSA insert these two modules
on the fly?  Supposing I have manually inserted these two modules before
hand  and if ALSA again tries to insmod them, what will happen? could the
system crash 'cos of this?

Whenever ALSA is inserting the abv two modules on the run, it should be
possible for me to insert my own module along with the two mentioned abv,
isn't it?  Can u pls tell me where in the ALSA src code this piece of
action is happening and how to insert my own module on the run.

--shaju abraham



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-07-24 14:49 UTC|newest]

Thread overview: 6+ 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   ` Calling snd_pcm_oss_write directly Shaju Abraham
2002-07-24 11:39     ` Paul Davis
2002-07-24 14:49       ` Shaju Abraham [this message]
2002-07-24 23:54         ` Inserting modules on the run Patrick Shirkey
2002-07-24 18:10     ` Calling snd_pcm_oss_write directly Jaroslav Kysela

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=3D3EBE7E.58C9604D@multitech.co.in \
    --to=shaju@multitech.co.in \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pbd@op.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.