From: Rolf Anderegg <rolf.anderegg@weiss.ch>
To: alsa-devel <alsa-devel@alsa-project.org>
Cc: Brian Karr <briank@tctechnologies.tc>,
Clemens Ladisch <clemens@ladisch.de>
Subject: firewire-kernel-streaming branch into main kernel tree?
Date: Tue, 19 Mar 2013 13:25:36 +0100 [thread overview]
Message-ID: <51485940.9070908@weiss.ch> (raw)
Hello Clemens,
it's been a long time since I last inquired about the snd_dice module
provided by your firewire-kernel-streaming branch
(http://git.alsa-project.org/?p=alsa-kprivate.git;a=shortlog;h=refs/heads/firewire-kernel-streaming),
which is a good sign I guess. In the meantime we have been making heavy
use of the snd_dice module for over a year with all of our Weiss DICE
based products (obviously playback only), and it has proven to be
extremely stable (currently 3.4.18-rt29, patched with
firewire-kernel-streaming).
Therefore I have been meaning to ask you for some time now whether you
have any interest in merging this firewire-kernel-streaming branch into
the main kernel tree (at least as an experimental option, mind you), or
are there any major objections?
Given that you don't have unlimited time at hand to further develop the
snd_dice module, let alone provide capture support in the near future,
AND the fact that DICE is likely to see its EOL soon (and replaced by a
sophisticated successor by TCAT), I realize that this is probably not a
high priority. However from our perspective it would be sad to see these
ALSA Firewire proceedings be lost and not be appreciated by a larger
audience. With respect to this:
* what would be the customary approach to requesting such a merge?
* what are your reservations, resp. are there any existing shortcomings
that you are yet unhappy with?
* have you received any other (negative/positive) feedback from
snd_dice users? I know of the Vortexbox community, which has been
offering an optional patch to support Firewire plackback devices; as far
as I know, they're happy with it.
* if you need any backing or assistance, we'd be happy to help out
Keen to hear your feedback on this suggestion.
Best regards,
Rolf Anderegg
(Weiss Engineering Ltd.)
next reply other threads:[~2013-03-19 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 12:25 Rolf Anderegg [this message]
2013-03-19 14:34 ` firewire-kernel-streaming branch into main kernel tree? Clemens Ladisch
2013-06-10 14:51 ` Rolf Anderegg
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=51485940.9070908@weiss.ch \
--to=rolf.anderegg@weiss.ch \
--cc=alsa-devel@alsa-project.org \
--cc=briank@tctechnologies.tc \
--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 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.