alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Olof <olof@baah.se>
Cc: alsa-devel@alsa-project.org
Subject: Re: Information request - writing a driver for a virtual soundcard
Date: Wed, 18 Aug 2010 21:15:10 +0200	[thread overview]
Message-ID: <20100818191510.GL17833@buzzloop.caiaq.de> (raw)
In-Reply-To: <AANLkTiksDnhg=kBupJ1uQO_vXq+8q-tk+TXwAwgtRaSm@mail.gmail.com>

On Wed, Aug 18, 2010 at 07:53:29PM +0200, Olof wrote:
> Maybe this is the wrong place to ask, but I kinda feel that I'm out of options.

ALSA allows rerouting of audio material to arbitary userspace plugins,
which sounds like what you're looking for. PulseAudio also give you
similar options, so it seems unnecessary to hack around in kernel space.

What exactly are you trying to do?

Daniel


> My goal is to write a dummy driver which makes the PCM data available
> as a character device though /dev/whatever. Of course I start with the
> dummy pcm driver. However I find it difficult to understand how the
> driver shall poll PCM data from the ALSA framework. I've read the
> how-to-write-a-driver doc and studied the hda driver but I don't
> understand how it all fits together with substreams, reading from
> intermediate buffers, the PCM memory management functions etc.
> 
> Could someone please help me out with some pointers to additional
> documentation, a suitable piece of driver code to study or any thing
> that might help?
> 
> Kind Regards,
> Olof

  reply	other threads:[~2010-08-18 19:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 17:53 Information request - writing a driver for a virtual soundcard Olof
2010-08-18 19:15 ` Daniel Mack [this message]
     [not found]   ` <AANLkTi=EO295r9BpmR105gYLRsjFhG3_kiD81mHTSLKP@mail.gmail.com>
2010-08-18 19:33     ` Daniel Mack
2010-08-18 19:44       ` Olof
2010-08-18 20:00         ` Daniel Mack

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=20100818191510.GL17833@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=olof@baah.se \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).