From: Daniel Wagner <wagi@monom.org>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>,
"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>,
Darren Anderson <darrena092@gmail.com>,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: A report about an enhancement for ALSA firewire stack
Date: Mon, 28 Jul 2014 16:06:37 +0200 [thread overview]
Message-ID: <53D658ED.8060903@monom.org> (raw)
In-Reply-To: <53CF7D9E.2050908@sakamocchi.jp>
Hi Takashi,
On 07/23/2014 11:17 AM, Takashi Sakamoto wrote:
> 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.
Great work! I really appreciate your hard work. Unfortunately I am a
little busy and don't have time to review soon.
cheers,
daniel
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
prev parent reply other threads:[~2014-07-28 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 9:17 A report about an enhancement for ALSA firewire stack Takashi Sakamoto
2014-07-28 14:06 ` Daniel Wagner [this message]
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=53D658ED.8060903@monom.org \
--to=wagi@monom.org \
--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=o-takashi@sakamocchi.jp \
--cc=pulseaudio-discuss@lists.freedesktop.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.