public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Doug McLain <doug@nostar.net>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA Fireworks driver
Date: Sat, 18 Jun 2011 17:18:53 -0400	[thread overview]
Message-ID: <4DFD163D.9050408@nostar.net> (raw)
In-Reply-To: <4DFB37D7.5030204@ladisch.de>

Aha! I had an older version that someone from the ffado list pointed me 
to.  I grabbed the .c and .h file from your link and built them (after 
defining CSR_IPCR and CSR_OPCR locally, my kernel-dev pkg doesnt have 
them) and now jack starts and I can record and play from ardour, but 
only at 44.1Khz, even though I start jackd with -r48000.  It looks like 
44.1Khz is the default setting the AF12 powers up at, and the alsa 
driver doesn't know how to change SR yet, is this the case?

I start the device up using ffado to force it into 48K, but then jack 
will no longer start using the alsa driver until I cycle power on the 
device.

The driver appears to work good in 44.1K though.  Aplay plays wav files 
using plughw, but not hw.

I also wonder if you can explain to me how to clone just that driver so 
I can keep up with it correctly using git pull.  I'm a little weak on 
git.  I just grabbed the .c and .h files manually and made my own 
Makefile for standalone module building.

Doug

On 06/17/2011 07:17 AM, Clemens Ladisch wrote:
> 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

  reply	other threads:[~2011-06-18 21:20 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
2011-06-18 21:18           ` Doug McLain [this message]
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=4DFD163D.9050408@nostar.net \
    --to=doug@nostar.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    /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