From: Michael Trimarchi <michael@amarulasolutions.com>
To: Grant Diffey <gdiffey@gmail.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Clemens Ladisch <clemens@ladisch.de>,
Daniel Mack <zonque@gmail.com>
Subject: Re: HIFACE family driver
Date: Wed, 14 Nov 2012 12:40:44 +0100 [thread overview]
Message-ID: <50A3833C.8030101@amarulasolutions.com> (raw)
In-Reply-To: <CACckToWXMza5tMB0w+qAseXjiRijsFzidLET7jDZynSguatxew@mail.gmail.com>
Hi
On 11/14/2012 12:15 PM, Grant Diffey wrote:
> On Wed, Nov 14, 2012 at 9:40 PM, Michael Trimarchi <michael@amarulasolutions.com <mailto:michael@amarulasolutions.com>> wrote:
>
> Hi all,
>
> I have written in my spare time an alsa driver for HIFACE devices family. Now I'm not an alsa expert and I would like to know if you think that it's useful to include it in mainline
>
> https://github.com/panicking/snd-usb-asyncaudio
>
> The list of usb devices supported
>
> https://github.com/panicking/snd-usb-asyncaudio/blob/master/chip.c
>
> The main difference is that I need to use bulk message to talk to the usb dongle and ofcourse there are a lot of improvement that we can do on it. I have already tested on several kernel version and it's already included in some linux distribution. Wait for some feedback ;)
>
> Michael
>
>
> Michael,
>
> Your driver has been discussed briefly on list already: http://mailman.alsa-project.org/pipermail/alsa-devel/2012-November/056791.html
>
> adding Daniel and Clemens as cc's
Ok, so the idea is to send patches on the mailing list. I can send one hiface for free if someone want help me on the submission. Sounds good?
Michael
>
> Grant
next prev parent reply other threads:[~2012-11-14 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 10:40 HIFACE family driver Michael Trimarchi
2012-11-14 11:15 ` Grant Diffey
2012-11-14 11:40 ` Michael Trimarchi [this message]
2012-11-14 12:44 ` Daniel Mack
2012-12-04 10:22 ` Michael Trimarchi
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=50A3833C.8030101@amarulasolutions.com \
--to=michael@amarulasolutions.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=gdiffey@gmail.com \
--cc=zonque@gmail.com \
/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