All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Carlos Pita <carlosjosepita@yahoo.com.ar>
Cc: alsa-devel@alsa-project.org
Subject: Re: virmidi, hotplug and udev
Date: Mon, 29 Nov 2004 12:28:43 +0100	[thread overview]
Message-ID: <s5h1xecrj10.wl@alsa2.suse.de> (raw)
In-Reply-To: <200411281851.29845.carlosjosepita@yahoo.com.ar>

At Sun, 28 Nov 2004 18:51:29 -0300,
Carlos Pita wrote:
> 
> Hi!
> 
> I'm using kernel 2.6.8 with hotplug enabled and udev
> (distro: debian sarge).
> 
> I need to use the snd-virmidi to create a virtual sound card
> with its raw midi devices.
> 
> I do:
>   modprobe snd-virmidi
> 
> Does this generate a hotplug event? Or at least an udev event?
> 
> I ask it because here the order is somewhat inverted. Normally
> a device is cold/hot plugged and modprobe is run in
> response to a subsequent hotplug event. But here the device is
> added as the effect of a previous modprobe. One thing I see
> is that modprobe would be retried as part of the event processing,
> that's innocuous but ugly.
> 
> Finally, do you know how to write the udev rules to generate
> the OSS raw midi devices. Currently, the only rules related
> to ALSA in my /etc/udev/rules.d/udev.rules are:
> 
> # ALSA devices
> KERNEL="controlC[0-9]*", NAME="snd/%k"
> KERNEL="hw[CD0-9]*",    NAME="snd/%k"
> KERNEL="pcm[CD0-9cp]*", NAME="snd/%k"
> KERNEL="midi[CD0-9]*",  NAME="snd/%k"
> KERNEL="timer",         NAME="snd/%k"
> KERNEL="seq",           NAME="snd/%k"
> 
> Most of the OSS devices are generated at boot time by
> udevstart. But /dev/midi10.../dev/midi13 are missing after
> modprobing snd-virmidi.

There are no /dev/midi1x devices on OSS.
As written in my last post, the OSS device has no concept of "card".
It just accepts the device in a serial order.

Nevertheless, OSS supports only up to 4 devices for /dev/midi0?.
(You can use more 4 devices with /dev/amidi?, too, though.)


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-11-29 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-28 21:51 virmidi, hotplug and udev Carlos Pita
2004-11-29 11:28 ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-28 21:49 Carlos Pita

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=s5h1xecrj10.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=carlosjosepita@yahoo.com.ar \
    /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.