From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Peter Enderborg <pme@ufh.se>,
"alsa-devel@lists.sourceforge.net"
<alsa-devel@lists.sourceforge.net>
Subject: Re: Number of subdevices on midi.
Date: Mon, 08 Apr 2002 17:02:30 +0200 [thread overview]
Message-ID: <s5hbscumdx5.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0204072220340.1002-100000@pnote.perex-int.cz>
At Sun, 7 Apr 2002 22:22:42 +0200 (CEST),
Jaroslav wrote:
>
> On Thu, 4 Apr 2002, Peter Enderborg wrote:
>
> > Jaroslav Kysela wrote:
> >
> > > On Wed, 3 Apr 2002, Peter Enderborg wrote:
> > >
> > > > I have tryed to get some answer from Jaroslav about subdevices on midi.
> > > > Im trying to write a driver for midisport 8x8/s and that have 9 midi
> > > > ports. On my hack to figure out the protocol I use virmidi to handle the
> > > > interface to alsa. But virmidi only have four subdevices per device. I
> > >
> > > You can set up to eight virmidi devices (snd_midi_devs parameter controls
> > > this count). On rawmidi side, there is 16 rawmidi substreams (subdevices)
> > > per one virmidi device. These subdevices are used for event merging
> > > (write) and coping (read). On sequencer side, there is one client and
> > > one port connected to virmidi device.
> > >
> > > > need to see the driver for a midi interface that using all the 16
> > > > subdevices. Since I don't get answer from Jaroslav i guess he don't have
> > > > the time or my question is stupid. But can someone help me out? Where
> > > > should I look?
> > >
> > > There are two ways:
> > >
> > > 1) we can add a new mode to virmidi code which suppress copying and
> > > merging and connects more sequencer ports per a sequencer client
> > > to rawmidi subdevices to handle such devices
> > > 2) without any change - simply use more than one virmidi card and connect
> > > your code to more clients:
> > >
> >
> > That is what I do now. But it is not pretty. My plan is to do a real driver
> > not a virmidi user.
> >
> >
> > >
> > > modprobe snd-virmidi snd_index=1,2 snd_enable=1,1 snd_midi_devs=8,8
> > >
> > > (use index values as you wish)
> > >
> >
> > Have you done that? This is what I get.
> >
> > [root@pescadero pme]# /sbin/modprobe snd-virmidi snd_enable=1,1
> > snd_midi_devs=8,8
> > /lib/modules/2.4.16/misc/snd-virmidi.o: init_module: No such device
> > Hint: insmod errors can be caused by incorrect module parameters, including
> > invalid IO or IRQ parameters
> > /lib/modules/2.4.16/misc/snd-virmidi.o: insmod
> > /lib/modules/2.4.16/misc/snd-virmidi.o failed
> > /lib/modules/2.4.16/misc/snd-virmidi.o: insmod snd-virmidi failed
>
> Oops. I've fixed this problem in CVS. Change SNDRV_RAWMIDI_DEVICES in
> alsa-kernel/include/rawmidi.h to 8.
in alsa-kernel/include/minors.h,
#define SNDRV_MINOR_RAWMIDI 8 /* 8 - 11 */
#define SNDRV_MINOR_RAWMIDIS 4
#define SNDRV_MINOR_PCM_PLAYBACK 16 /* 16 - 23 */
so we need to change this too..
it seems no problem to assign 8 rawmidi devices - 8 devices are free,
although the comment says 8 - 11..
Takashi
next prev parent reply other threads:[~2002-04-08 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 19:23 Number of subdevices on midi Peter Enderborg
2002-04-04 7:17 ` Michael Ashton
2002-04-04 8:01 ` Jaroslav Kysela
2002-04-04 20:30 ` Peter Enderborg
2002-04-07 20:22 ` Jaroslav Kysela
2002-04-08 15:02 ` Takashi Iwai [this message]
2002-04-09 6:36 ` Jaroslav Kysela
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=s5hbscumdx5.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=pme@ufh.se \
/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.