Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Pablo Bouza <jpbouza@hotmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: M-Audio FTU issues
Date: Wed, 13 Jul 2011 18:18:23 -0300	[thread overview]
Message-ID: <BAY155-w5801313DA3F263CD8A59C3B6470@phx.gbl> (raw)
In-Reply-To: <CACckToXFevhAHt_jC9P=ifZ9X0KVT1S7-KQnrcSna_ineeSyZg@mail.gmail.com>


Hi! Sorry for the dull question, but I'm new to this mailing list and to alsa development in general.
I was looking for the latest patch for the FTU, can anyone send me the link to it, or point me out to a location where alsa patches are stored?

Thanks!


> Date: Sun, 3 Jul 2011 21:52:06 +1000
> From: gdiffey@gmail.com
> To: zonque@gmail.com
> CC: tiwai@suse.de; blablack@gmail.com; alsa-devel@alsa-project.org; clemens@ladisch.de; linuxaudio@showlabor.de
> Subject: Re: [alsa-devel] M-Audio FTU issues
> 
> >
> > On Tue, Jun 28, 2011 at 10:37 PM, Aurélien Leblond <blablack@gmail.com>
> > wrote:
> > > Hi Daniel,
> > >
> > > All clicks gone as Felix already said :)
> >
> > Good.
> >
> >
> 
> So it works. yay
> 
> 
> > > And confirmed, the kernel crashed with playback and capture streams
> > > started at the same time :)
> >
> > I'd like to discuss the API for the ALSA/USB decoupling as suggested
> > by Clemens, which will solve this problem then.
> >
> 
> Nobody has any ideas what this interface might look like?
> 
> From what I understand this would lead to re-unifying the ua101 driver into
> snd-usb-audio as well?
> 
> Grant
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
 		 	   		  

  parent reply	other threads:[~2011-07-13 21:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24  1:14 M-Audio FTU issues Daniel Mack
2011-06-24  3:27 ` Grant Diffey
2011-06-24  7:35 ` Felix Homann
2011-06-24  8:52 ` Felix Homann
2011-06-24 15:23   ` Daniel Mack
2011-06-24 15:58     ` Clemens Ladisch
2011-06-24 16:10       ` Daniel Mack
2011-06-28 20:37         ` Aurélien Leblond
2011-06-29  8:08           ` Daniel Mack
2011-07-03 11:52             ` Grant Diffey
2011-07-04 17:14               ` Aurélien Leblond
2011-07-04 17:23               ` Daniel Mack
2011-07-13 21:18               ` Juan Pablo Bouza [this message]
2011-07-21  5:08               ` Juan Pablo Bouza
2011-07-21  7:55                 ` Daniel Mack
2011-07-21  8:25                   ` Felix Homann
2011-07-24 14:12                     ` Aurélien Leblond
2011-07-24 14:46                       ` Daniel Mack
2011-07-21 20:31                   ` Juan Pablo Bouza
2011-07-22  8:42                     ` Daniel Mack
2011-07-23  4:25                       ` Juan Pablo Bouza
2011-07-25 13:07         ` Clemens Ladisch
2011-06-27  8:52     ` Felix Homann
2011-06-24  9:08 ` Felix Homann

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=BAY155-w5801313DA3F263CD8A59C3B6470@phx.gbl \
    --to=jpbouza@hotmail.com \
    --cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox