All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Parpart <trapni@gentoo.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: virtual OSS devices [for making selfish apps happy]
Date: Mon, 21 Nov 2005 22:16:07 +0100	[thread overview]
Message-ID: <200511212216.10837.trapni@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]

Hi all,

I'm having some apps running on my desktop that all want
exclusive access to my sound device just for playing audio
(and a single app for capturing), namely:

 * TeamSpeak (VoIP team voice chat)
 * Cedega (for playing some win32 games on my beloved box)
 * KDE/arts (my desktop wants to play some sounds as well wtf)

While I could easily disable my desktop sounds, and yeah, forget about the 
music, but I'd still like to be in TeamSpeak (talking to friends and alike) 
while playing a game using cedega.

Unfortunately, *all* those stupid (2) apps want exclusive access to the OSS 
layout of my ALSA drivers, though, there just came into my mind to buy a 
second audio device and wear a second headset (a little one below/under my 
big one). But I couldn't find it handy anyway :(

So, in the end, what about writing a virtual OSS driver that can spawn 
multiple (fake) /dev/vdsp%d's that all allow audio rendering (output) and at 
least a single one capturing (this at least would fit *my* needs).
This virtual driver then would has to know about the real audio device then of 
course that would it use to merge/mix the audio outputs to and to read the 
requested capture data from.

Okay, neat idea, but I never ever wrote a single kernel code line!

So, can some guys of you please help me out there in *either* telling me where 
to find the basics on kernel module writing *and* how to do such things like 
I said I want.
Or, even if you feel that happy about that idea and can't wait until I got 
stuck in finishing it, and you can DIYS, that would be even much nicer.

C/C++ is not my problem, and I have already seen/read the linux kernel code 
not just once, but I am definitely laggin in experience in kernel 
development.

Please help.

Thanks in advance,
Christian Parpart.

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

             reply	other threads:[~2005-11-21 21:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 21:16 Christian Parpart [this message]
2005-11-21 21:40 ` virtual OSS devices [for making selfish apps happy] Lee Revell
2005-11-22  2:26   ` Alistair John Strachan
2005-11-22  3:59     ` Lee Revell
2005-11-22  8:20   ` Jaroslav Kysela
  -- strict thread matches above, loose matches on Subject: below --
2005-11-21 21:39 Nick Warne
2005-11-21 21:52 ` Lee Revell

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=200511212216.10837.trapni@gentoo.org \
    --to=trapni@gentoo.org \
    --cc=linux-kernel@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 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.