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: Tue, 02 Jul 2002 16:51:32 +0200 [thread overview]
Message-ID: <s5hznxarxmz.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hhejibem0.wl@alsa2.suse.de>
At Tue, 02 Jul 2002 12:36:55 +0200,
I wrote:
>
> At Mon, 01 Jul 2002 19:07:40 +0200,
> Clemens Ladisch wrote:
> >
> > Attached is a patch for a USB MIDI driver.
> > Essentially, it does the same as my USB MIDI daemon.
> >
> > The source is put into the alsa-kernel tree, not into alsa-driver like
> > the usb-audio driver.
>
> i prefer putting it onto alsa-driver at first unless it's confirmed as
> enough stable after tarball release. alsa-kernel is the tree to be
> merged into 2.5 kernel. also, the location of usb drivers is still a
> question, whether on sound tree or on drivers/usb tree.
>
> anyway, i'll check the code into cvs after review (if there is no
> objection).
ok, now it's there. as written above, i put it to alsa-driver tree.
let us move the usb stuff later to the official kernel place.
your codes have been slightly modified:
- usb compatibility hack was moved to wrapper.h, so that it can be
shared with usbuadio.c
- 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?
thanks.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-02 14:51 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 ` Takashi Iwai [this message]
2002-07-02 20:40 ` Re: [PATCH] USB MIDI driver 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
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=s5hznxarxmz.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