fix for missing symbol in snd-ymfpci.o
A message that is not in the archive (sent off-list or not yet received): [email protected]
Takashi Iwai
AppliedHi Jack,
At Sat, 20 Jul 2002 10:25:23 -0400 (EDT),
Quoted 8 lines · Jack Howarth
Takashi,
Please check the following patch into the alsa cvs.
Currentlyalsa-kernel/pci/ymfpci/ymfpci_main.crelies on thelinux/vmalloc.hheader being implicitly included by other headers which isn't true on ppc. Without this patch the vmalloc inline isn't defined and a missing symbol for vmalloc results in snd-ymfpci.o. Thanks in advance.
thanks, applied.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Calling snd_pcm_oss_write directly.
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
Re: Calling snd_pcm_oss_write directly.
Quoted 2 lines
I am in a situation where I intend to call
snd_pcm_oss_write
directly.
AFAIK, this is not a supported use of the alsa-lib API. There is no guarantee that your application will continue to work in future versions of alsa-lib.
Quoted 3 lines
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.
there is still no reason to be using snd_pcm_<type>_<function> directly.
if you insist on using the OSS API (a big error, IMHO) then you can just use the OSS API in the other task.
--p
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Inserting modules on the run.
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
Re: Inserting modules on the run.
Quoted 10 lines · Shaju Abraham
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?
Quoted 5 lines
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.
You should use the /etc/modules.conf file
There is a lot of information on how to use this in the alsa-wiki and alsa howto.
see the documentation link on the alsa webpage.
Quoted 14 lines
--shaju abraham
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Signature · 10 lines
Patrick Shirkey - Boost Hardware Ltd. For the discerning hardware connoisseur Http://www.boosthardware.com Http://www.boosthardware.com/LAU/guide/ ======================================== ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim
Re: Calling snd_pcm_oss_write directly.
In reply to Shaju AbrahamQuoted 8 lines · Shaju Abraham
Hi all,
I am in a situation where I intend to callsnd_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.
Quoted 7 lines
So what I do is, when
snd_pcm_oss_opengets 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.
Why you do these very ugly things? It seems that you're calling internal functions of the OSS emulation in the kernel space.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project http://www.alsa-project.org
SuSE Linux http://www.suse.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf