Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kaushik Kumar <kaukum@gmail.com>
To: Phil Frost <indigo@bitglue.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: sound application needed...
Date: Thu, 21 Jul 2005 12:46:54 +1000	[thread overview]
Message-ID: <e2033af505072019467779417e@mail.gmail.com> (raw)
In-Reply-To: <20050720113614.GA3597@bitglue.com>

hi phil,

I am actually implementing an user level sound driver.. which is still
in its rudimentary stages. It does *not* use the /proc interface. I
have a simple driver API which the application needs to use. And I
need to basically test it.

Any further help would be appreciated.

Thanx!
kaushik

On 7/20/05, Phil Frost <indigo@bitglue.com> wrote:
> On Wed, Jul 20, 2005 at 08:08:18PM +1000, Kaushik Kumar wrote:
> > I need a simple sound application to test my sound driver which does
> > *not* use the  alsa user lib API.
> 
> You can cat files to /dev/dsp, like so:
> 
>   cat /proc/kcore > /dev/dsp
> 
> You can also read from it, then play it again:
> 
>   cat /dev/dsp > tmp; cat tmp > /dev/dsp  # hit ^C to stop recording
>


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click

      reply	other threads:[~2005-07-21  2:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e2033af5050720024951dd4324@mail.gmail.com>
     [not found] ` <e2033af50507200252492b24ab@mail.gmail.com>
2005-07-20 10:08   ` sound application needed Kaushik Kumar
2005-07-20 11:36     ` Phil Frost
2005-07-21  2:46       ` Kaushik Kumar [this message]

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=e2033af505072019467779417e@mail.gmail.com \
    --to=kaukum@gmail.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=indigo@bitglue.com \
    /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