From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] Use rawmidi device name for sequencer client name
Date: Thu, 28 Nov 2002 17:23:35 +0100 [thread overview]
Message-ID: <s5hptspzmrc.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.HPX.4.33n.0211281650360.20371-100000@studcom.urz.uni-halle.de>
At Thu, 28 Nov 2002 17:00:35 +0100 (MET),
Clemens Ladisch wrote:
>
> Takashi Iwai wrote:
> > Clemens Ladisch wrote:
> > > The snd_seq_midisynth_register_port() function already knows the name of
> > > the rawmidi device, so there is no reason to invent another name for the
> > > sequencer client.
> >
> > the reason was that many rawmidi devices give the same name even if
> > there are many. for example, mpu401 sets only "MPU-401 (UART)" as its
> > name.
> > although the card can be distinguished by the client number, it would
> > be better to be able to know only from its name string.
>
> The maybe we could add the card number or id to the string.
> "MPU-401 (card42)" would be better than "External MIDI 42-0".
ok, now, the question is whether this "(cardx)" is included in each
rawmidi name or put in seq_midi.c.
if we use the rawmidi name with the card id, each rawmidi creator
should be responsible.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
next prev parent reply other threads:[~2002-11-28 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 12:38 [PATCH] Use rawmidi device name for sequencer client name Clemens Ladisch
2002-11-28 14:16 ` Takashi Iwai
2002-11-28 16:00 ` Clemens Ladisch
2002-11-28 16:23 ` Takashi Iwai [this message]
2002-11-28 17:12 ` Clemens Ladisch
-- strict thread matches above, loose matches on Subject: below --
2002-11-12 15:06 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=s5hptspzmrc.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 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.