Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: felipe.balbi@nokia.com
Cc: ext Bryan Wu <cooloney@kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: Some idea about usb audio gadget driver.
Date: Tue, 23 Sep 2008 14:08:05 +0200	[thread overview]
Message-ID: <48D8DC25.2060405@parrot.com> (raw)
In-Reply-To: <20080923104542.GB24627@gandalf.research.nokia.com>

Felipe Balbi a écrit :
> On Tue, Sep 23, 2008 at 05:50:33PM +0800, ext Bryan Wu wrote:
>> Hi ALSA and USB folks,
>>
>>
>>  - Is there any similar things on this planet?
>>  - How about gmidi usb midi gadget driver?
>>  - How can I open/playback/record/close a ALSA sound card in kernel
>> space not using alsalib in user space?
> 
> Start by converting gmidi to composite framework. Separate the alsa
> generic code from usb generic code and the function driver (in that case
> MIDI). Then, all you have to do is add a new function driver with proper
> audio streaming.
I am not sure there is lot's of common alsa code. IIRC Midi and Pcm API
are different in alsa.

But I think we shouldn't try to drive a sound card from kernel, we
should create an alsa sound card like gmidi, and let's userspace do what
it wants (redirect from/to another sound card, stream files, ...).


Mattieu

  reply	other threads:[~2008-09-23 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23  9:50 Some idea about usb audio gadget driver Bryan Wu
2008-09-23 10:45 ` Felipe Balbi
2008-09-23 12:08   ` Matthieu CASTET [this message]
     [not found] ` <386072610809230250w2e43c20ei89076a8db62c5044-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-24  7:15   ` [alsa-devel] " Clemens Ladisch

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=48D8DC25.2060405@parrot.com \
    --to=matthieu.castet@parrot.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=cooloney@kernel.org \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-usb@vger.kernel.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