All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: John Talbut <john@dpets.demon.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Setup when compiled in 2.6 kernel
Date: Sun, 19 Feb 2006 14:00:58 -0500	[thread overview]
Message-ID: <1140375659.2733.338.camel@mindpipe> (raw)
In-Reply-To: <43F8A917.8010008@dpets.demon.co.uk>

On Sun, 2006-02-19 at 17:21 +0000, John Talbut wrote:
> Am I correct in believing that the kernel will set up and communicate 
> with device files?  If so, how can I test them?  I have tried on
> various 
> devices, e.g.
> 
> >  sox -V -b -c 1 -r 448000 -t alsa /dev/snd/pcmC2D0p -t .wav test.wav
> and I get
> > ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown
> PCM /dev/snd/pcmC2D0p sox: Failed reading /dev/snd/pcmC2D0p: cannot
> open audio device
> and
>  > cat /dos/Workspace/Music/originaldedodedo.wav > /dev/snd/pcmC2D0pD
> and I get nothing. 

This is not how ALSA works, you can't just cat things to the device
file.  The interface to ALSA is through alsa-lib.

What happens if you start SIMPLE:

aplay file.wav

?



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

  reply	other threads:[~2006-02-19 19:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 17:21 Setup when compiled in 2.6 kernel John Talbut
2006-02-19 19:00 ` Lee Revell [this message]
2006-02-19 19:46   ` John Talbut
2006-02-19 19:53     ` Lee Revell
2006-02-19 21:47       ` John Talbut
2006-02-19 21:52         ` Lee Revell
2006-02-20  7:13           ` John Talbut
2006-02-20  8:01             ` Lee Revell
2006-02-20  8:21     ` Clemens Ladisch

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=1140375659.2733.338.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=john@dpets.demon.co.uk \
    /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.