From: Ben Williamson <ben.williamson@greyinnovation.com>
To: David Brownell <david-b@pacbell.net>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@lists.sourceforge.net,
Clemens Ladisch <clemens@ladisch.de>
Subject: Re: [RFC] g_midi: New USB MIDI Gadget class driver.
Date: Fri, 07 Jul 2006 14:14:25 +1000 [thread overview]
Message-ID: <44ADDFA1.50109@greyinnovation.com> (raw)
In-Reply-To: <200607061949.40459.david-b@pacbell.net>
David Brownell wrote:
> One UDC, yes -- that's a very basic USB definition thing. But surely one
> MIDI gadget can support multiple channels, one interface each?
Actually I was wondering if you plan to support plugging in multiple NetChip UDC
cards, but I can't imagine it would be all that useful.
At this stage g_midi only support one MIDI in jack and one MIDI out jack, because
that's all I need for now. In order to support more than that one would need to
add more jack descriptors and corresponding rawmidi substreams, none of which
should be too tough. But I think it would make the most sense for all that to
still appear under the one ALSA "card", with a single index and id as Clemens
suggested, at least as I understand it.
- Ben.
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-07-07 4:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 6:06 [RFC] g_midi: New USB MIDI Gadget class driver Ben Williamson
2006-07-06 9:27 ` Clemens Ladisch
2006-07-07 0:37 ` Ben Williamson
2006-07-07 2:49 ` David Brownell
2006-07-07 4:14 ` Ben Williamson [this message]
2006-07-06 16:31 ` David Brownell
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=44ADDFA1.50109@greyinnovation.com \
--to=ben.williamson@greyinnovation.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=david-b@pacbell.net \
--cc=tiwai@suse.de \
/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.