From: "Gabriel M. Beddingfield" <gabrbedd@gmail.com>
To: Lucas Takejame <lucas@takejame.com.br>, alsa-devel@alsa-project.org
Subject: Re: snd-usb driver
Date: Wed, 11 Dec 2013 20:17:00 -0800 [thread overview]
Message-ID: <52A938BC.1050804@gmail.com> (raw)
In-Reply-To: <CAJUVNopomSJU_+WE8U8kjOP5Bh_670H2w=DTRLBF37fDsQfg4g@mail.gmail.com>
Hi Lucas,
I wonder if I've misunderstood what you're trying to accomplish...
On 12/11/2013 08:59 AM, Lucas Takejame wrote:
> snd-usb driver). I know the code is already optimized but I was hoping
> that, since we only use one specific sound card and we won't need a generic
> driver, I could change something in the code to optimize it latency wise. I
Are you creating a product that *is* a USB sound card and you want to
write a driver for it?
...or do you have some pre-existing USB sound card (and driver) that
this product is using and you're trying to set up a low-latency audio
workstation that uses it?
-gabe
next prev parent reply other threads:[~2013-12-12 4:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 16:59 snd-usb driver Lucas Takejame
2013-12-11 21:17 ` Clemens Ladisch
2013-12-12 4:17 ` Gabriel M. Beddingfield [this message]
2013-12-12 16:24 ` Lucas Takejame
2013-12-12 19:28 ` Patrick Shirkey
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=52A938BC.1050804@gmail.com \
--to=gabrbedd@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=lucas@takejame.com.br \
/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.