From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: [PATCH] USB MIDI driver
Date: Wed, 03 Jul 2002 15:18:46 +0200 [thread overview]
Message-ID: <s5hk7odrlu1.wl@alsa2.suse.de> (raw)
In-Reply-To: <3D22F37D.14EE3DAB@ladisch.de>
At Wed, 03 Jul 2002 14:52:13 +0200,
Clemens Ladisch wrote:
>
> Takashi Iwai wrote:
> > - newly added virmidi registrations.
> > that means, snd-usb-midi will have its own rawmidi devices
> > automatically as /dev/snd/midiCxDx.
> > this will be good for applications which speak only with
> > rawmidi.
> >
> > the latter one was not tested.
> > can anyone update the cvs if it works?
>
> Using the cable number as index for the rawmidi device will not work
> if there is more than one endpoint (I don't think such a device exists;
> my driver supports more than one endpoint only because the OSS and
> NetBSD drivers do).
>
> I changed it to use the sequencer port number instead.
>
> There are devices with more output than input ports (e.g. MU1000),
> and virmidi with SNDRV_VIRMIDI_SEQ_ATTACH doesn't support input anyway,
hmm, this mode wasn't tested, too. usb-midi is the first case.
doesn't rawmidi read work at all?
> so I moved the rmidi pointer from usbmidi_in_port to usbmidi_out_port.
> (The virmidi device applies to both input and output ports, so,
> theoretically, it should go into a usbmidi_endpoint structure. That
> one hasn't been needed until now.)
yep.
anyway, the patch is applied. thanks.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
No, I will not fix your computer.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-03 13:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 17:07 [PATCH] USB MIDI driver Clemens Ladisch
2002-07-02 10:36 ` Takashi Iwai
2002-07-02 14:28 ` USB recording - repetitive peaks Patrick Shirkey
2002-07-02 14:57 ` Takashi Iwai
2002-07-02 15:35 ` Patrick Shirkey
2002-07-02 16:03 ` Takashi Iwai
2002-07-02 16:37 ` Patrick Shirkey
2002-07-02 16:39 ` Takashi Iwai
2002-07-02 17:08 ` Patrick Shirkey
2002-07-02 17:29 ` Takashi Iwai
2002-07-02 18:04 ` Patrick Shirkey
2002-07-02 18:26 ` Patrick Shirkey
2002-07-02 18:38 ` Patrick Shirkey
2002-07-04 9:41 ` Takashi Iwai
2002-07-03 8:55 ` Takashi Iwai
2002-07-04 16:23 ` Patrick Shirkey
2002-07-04 16:26 ` Takashi Iwai
2002-07-04 17:15 ` Patrick Shirkey
2002-07-04 17:27 ` Paul Davis
2002-07-05 13:44 ` Takashi Iwai
2002-07-05 18:19 ` Patrick Shirkey
2002-07-05 18:37 ` Patrick Shirkey
2002-07-04 18:59 ` Thorsten Haas
2002-07-05 6:56 ` Thorsten Haas
2002-07-05 8:34 ` Patrick Shirkey
2002-07-05 8:38 ` Thorsten Haas
2002-07-05 9:06 ` Thorsten Haas
2002-07-05 15:35 ` Takashi Iwai
2002-07-03 5:18 ` Fernando Pablo Lopez-Lezcano
2002-07-03 8:50 ` Takashi Iwai
2002-07-02 16:07 ` Patrick Shirkey
2002-07-02 14:51 ` Re: [PATCH] USB MIDI driver Takashi Iwai
2002-07-02 20:40 ` Pedro Lopez-Cabanillas
2002-07-02 22:10 ` Pedro Lopez-Cabanillas
2002-07-03 12:52 ` Clemens Ladisch
2002-07-03 13:18 ` Takashi Iwai [this message]
2002-07-03 14:42 ` Clemens Ladisch
2002-07-04 9:47 ` Takashi Iwai
2002-07-04 11:52 ` Clemens Ladisch
2002-07-05 7:55 ` Clemens Ladisch
2002-07-05 13:40 ` Takashi Iwai
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=s5hk7odrlu1.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox