From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: [PATCH 00/44 v3] Enhancement of support for Firewire devices Date: Fri, 04 Apr 2014 09:04:23 +0200 Message-ID: References: <1395400229-22957-1-git-send-email-o-takashi@sakamocchi.jp> <533DB3C7.5010507@canonical.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 9CDD0265565 for ; Fri, 4 Apr 2014 09:04:25 +0200 (CEST) In-Reply-To: <533DB3C7.5010507@canonical.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: David Henningsson Cc: alsa-devel@alsa-project.org, Takashi Sakamoto , clemens@ladisch.de, ffado-devel@lists.sf.net, linux1394-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Thu, 03 Apr 2014 21:17:27 +0200, David Henningsson wrote: > > On 03/21/2014 12:09 PM, Takashi Sakamoto wrote: > > This series is an update for my previous series: > > [alsa-devel] [GIT PULL][PATCH 00/39 v2] Enhancement of support for Firewire > > devices > > http://mailman.alsa-project.org/pipermail/alsa-devel/2014-March/073868.html > > Hi, > > I've tested Takashi's patches [1] with my one Firewire device (Presonus > FP10) and I've found it to work well, both midi and audio. > In addition, during my testing I've found Takashi Sakamoto to be very > good to work with, and I'm confident he will continue to look after the > driver for some time ahead. > > While I haven't looked through the patches in detail - after all, the > firewire stack is not really my point of expertise (yet!) - but from a > pragmatic view, having ALSA kernel support for firewire devices is a > very welcome addition. (Although a late one, considering firewire's > declining popularity.) > > While not everything is perfect yet - e g PulseAudio and Audacity are > two applications that would require some coding on either end to > facilitate better integration - no driver is ever perfect, and the > current driver is a big step in the right direction. > > To sum up, from my pragmatic view I've found the patch series [1] to be > stable enough to mainline, and I recommend merging this patch series for > the 3.15 kernel merge window. For 3.15, it's too late, sorry. Takashi