From: Doug McLain <doug@nostar.net>
To: clemens@ladisch.de, alsa-devel@alsa-project.org
Subject: ALSA Fireworks driver
Date: Fri, 17 Jun 2011 02:26:52 -0400 [thread overview]
Message-ID: <4DFAF3AC.3030506@nostar.net> (raw)
Hi Clemens,
I came across your fireworks driver the other day, and would like to get
involved. Has there been any discussion on this anywhere or have you
been completely on your own? I did a search of alsa-devel and didn't
find anything, suprisingly. It seems like native alsa support of what
seems to me to be the first FW device would be the talk of the town. :)
I built the driver as a module on F15 and loaded it on my AF12, and
found it in /proc/asound/cards, and tried to start jack on it and it
failed to start for duplex, capture, or playback, just FYI.
Doug
next reply other threads:[~2011-06-17 6:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 6:26 Doug McLain [this message]
2011-06-17 7:15 ` ALSA Fireworks driver 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
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=4DFAF3AC.3030506@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