From: Doug McLain <doug@nostar.net>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA Fireworks driver
Date: Tue, 21 Jun 2011 08:57:57 -0400 [thread overview]
Message-ID: <4E009555.5040208@nostar.net> (raw)
In-Reply-To: <4E0082A6.4030502@ladisch.de>
Nice, now I have it up and running with my preferred SR of 48Khz, and it
seems to be stable. I figured out the git stuff since the last email I
sent. I didn't know how to browse and switch to various branches, so I
kept getting the wrong files in sound/firewire.
Thanks for the help,
Doug
On 06/21/2011 07:38 AM, Clemens Ladisch wrote:
> Doug McLain wrote:
>> 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?
>
> Actually, the driver knows quite well how to change SR, and does this to
> initialize the device to 44.1 kHz. However, this driver was intended as
> a prototype, so I didn't bother to implement making the other SRs
> available to ALSA applications.
>
>> FYI I tried #define FIXED_RATE 48000 just to see if I could use the
>> driver at 48K for soem recording sessions today.
>
> This should work if you also change FIXED_RATE_SFC (0...6 = 32/44.1/48/
> 88.2/96/176.4/192 kHz).
>
>> Aplay plays wav files using plughw, but not hw.
>
> This is to be expected if your .wav doesn't have twelve channels of
> 32-bit samples.
>
>> 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.
>
> The driver is in a kernel repository because it is part of the kernel;
> using it with other kernel versions would require back-porting any
> changes in the kernel API (as you did this with the CSR_ symbols).
>
> Current development is in the firewire-kernel-streaming branch, where
> the drivers are composed of more files and depend on some changes in
> the core kernel. There is no easy way of using these with another
> kernel.
>
>
> Regards,
> Clemens
next prev parent reply other threads:[~2011-06-21 12:58 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
2011-06-21 11:38 ` Clemens Ladisch
2011-06-21 12:57 ` Doug McLain [this message]
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=4E009555.5040208@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