From: Clemens Ladisch <clemens@ladisch.de>
To: Doug McLain <doug@nostar.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA Fireworks driver
Date: Fri, 17 Jun 2011 13:17:43 +0200 [thread overview]
Message-ID: <4DFB37D7.5030204@ladisch.de> (raw)
In-Reply-To: <4DFB1F0B.5010201@nostar.net>
Doug McLain wrote:
> > > [nostar@iggy firewire]$ cat /proc/asound/cards
> > > 3 [AudioFire12 ]: Fireworks - AudioFire12
> > > Echo Digital Audio AudioFire12 v5.0, GUID 0014860fc44a84a6 at fw1.0, S400
>
> [nostar@iggy export]$ aplay -D plughw:AudioFire12 wg.wav
> aplay: main:660: audio open error: No such file or directory
>
> [nostar@iggy export]$ aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: NVidia [HDA NVidia], device 0: ALC1200 Analog [ALC1200 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> card 0: NVidia [HDA NVidia], device 1: ALC1200 Digital [ALC1200 Digital]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
There is not PCM device for the AF12.
In theory, it shouldn't be possible for the driver to attach to the
device without having created the PCM device. Are you sure that you
have the latest version of the driver? Where exactly did you get it
from? Please check that the fireworks.c file has 2275 lines, like this
one:
http://git.alsa-project.org/?p=alsa-kprivate.git;a=blob;hb=fireworks;f=sound/firewire/fireworks.c
Regards,
Clemens
next prev parent reply other threads:[~2011-06-17 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 6:26 ALSA Fireworks driver Doug McLain
2011-06-17 7:15 ` Clemens Ladisch
2011-06-17 7:21 ` Doug McLain
[not found] ` <4DFB0643.7070700@ladisch.de>
[not found] ` <4DFB1F0B.5010201@nostar.net>
2011-06-17 11:17 ` Clemens Ladisch [this message]
2011-06-18 21:18 ` Doug McLain
2011-06-21 11:38 ` Clemens Ladisch
2011-06-21 12:57 ` Doug McLain
2011-06-18 22:51 ` Doug McLain
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=4DFB37D7.5030204@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=doug@nostar.net \
/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