From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"ffado-devel@lists.sf.net" <ffado-devel@lists.sf.net>,
JACK <jack-devel@lists.jackaudio.org>,
linux1394-devel@lists.sourceforge.net,
General PulseAudio Discussion
<pulseaudio-discuss@lists.freedesktop.org>
Cc: Maximilian Engelhardt <maxi@daemonizer.de>,
Daniel Wagner <wagi@monom.org>,
Darren Anderson <darrena092@gmail.com>,
David Henningsson <david.henningsson@canonical.com>
Subject: A report about an enhancement for ALSA firewire stack
Date: Wed, 23 Jul 2014 18:17:18 +0900 [thread overview]
Message-ID: <53CF7D9E.2050908@sakamocchi.jp> (raw)
Dear all,
My work for ALSA firewire stack was pulled into Linux 3.16, therefore
Linux 3.16 newly supports 60-70 firewire sound devices. The work may
affects user-space applications such like FFADO. Additionally, I leave
some issues for the stack.
So I wrote a report about my work.
PDF:
https://github.com/takaswie/alsa-firewire-report/blob/master/firewire.pdf
Repository:
https://github.com/takaswie/alsa-firewire-report
Table of contents
1. Introduction
2. Common Specifications
3. Device features
4. Existing drivers
5. Investigation for user-land driver
6. Investigation for kernel-land driver
7. Enhancement of ALSA firewire stack
8. Driver implementation
9. Rest of issue
I hope ALSA maintainers to read section 8 and 9.
For FFADO developers, section 3, 5, 8 will be good information.
For JACK/PulseAudio and Linux firewire subsystem developers, section 4,
5, 6, 7, 9 will be good information.
I'm not a good English writer and have a little experiences to write
technical documents. It's my glad to receive some corrections,
indications, supplements and so on from you.
Regards
Takashi Sakamoto
o-takashi@sakamocchi.jp
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
next reply other threads:[~2014-07-23 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 9:17 Takashi Sakamoto [this message]
2014-07-28 14:06 ` A report about an enhancement for ALSA firewire stack Daniel Wagner
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=53CF7D9E.2050908@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=darrena092@gmail.com \
--cc=david.henningsson@canonical.com \
--cc=ffado-devel@lists.sf.net \
--cc=jack-devel@lists.jackaudio.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=maxi@daemonizer.de \
--cc=pulseaudio-discuss@lists.freedesktop.org \
--cc=wagi@monom.org \
/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.