All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pedro Lopez-Cabanillas <plcl@telefonica.net>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: snd-usb-audio in ALSA 0.9.0rc5
Date: Thu, 14 Nov 2002 00:34:17 +0100	[thread overview]
Message-ID: <200211140034.17681.plcl@telefonica.net> (raw)
In-Reply-To: <Pine.HPX.4.33n.0211130912420.5971-100000@studcom.urz.uni-halle.de>

On Wednesday 13 November 2002 09:50, Clemens Ladisch wrote:
> Pedro Lopez-Cabanillas wrote:
> > IMHO, mapping the card MIDI ports to subdevices may be OK, but only for
> > ALSA native rawmidi. After all, you can access some MIDI port with
> > "hw:x,y,z" instead of "hw:x,y", but for OSS emulation a better approach
> > is needed. For major 14, why not to bind minors sequentially for each
> > MIDI port on the system? I mean: first port minor=2, second port
> > minor=18, ... thru -and up- minor=242 (/dev/midi15) if needed, regardless
> > of ALSA card numbers?
>
> This would break if cards are loaded dynamically, i.e. the port number
> would depend on the order the drivers are loaded.

Yes, but not only the driver's loading order matters. With USB devices, the 
hub's port number and the plug-in order may cause troubles, too. With my UM-2 
and Midisport2x2, both using snd-usb-audio driver, i was used to cat 
/proc/asound/seq/clients from time to time, to know which client number had 
each device, until i've found a solution that is the same as for driver 
loading order. This is a snippet from my modules.conf file:

alias char-major-14 soundcore
alias char-major-116 snd
alias snd-card-0 snd-ens1371
alias snd-card-1 snd-usb-audio
alias snd-card-2 snd-usb-audio
options snd cards_limit=3
options snd-ens1371 index=0
options snd-usb-audio index=1,2 vid=0x0763,0x0582 pid=0x1110,0x0005

Since i've found this trick, i don't need to wonder about client numbers as 
they always are the same. It doesn' matter which device i plug-in first, 
neither which USB hub port it uses. 72 is always Midisport and 80 is UM-2.

I don't know if there is a better way, and i'm not sure if it shall work  for 
OSS rawmidi also. 

> Well, for obvous reasons (i.e. laziness), the current answer for this is
> "don't use OSS".  ;-)

You're kidding :-) You made a great, tireless work with ALSA usb driver, and 
ALSA as a whole is going to be beautiful too... but there are a lot of worthy   
OSS legacy apps (i.e. PD), and many cheap and ubiquitous USB MIDI multiport 
devices now. IMHO, ALSA should be able to give support to both worlds.

Of course, this issue must be addressed very carefully, having some previous 
discussions with final consensus.

About device minor numbers, i've heard that Linux 2.6 shall break actual  
limitations, with a 32 bits kdev_t, divided up to 12 bits for major and 20 
bits for minor. Anybody can confirm this?

Regards,
Pedro

-- 
ALSA Library Bindings for Pascal
http://alsapas.alturl.com



-------------------------------------------------------
This sf.net email is sponsored by: Are you worried about 
your web server security? Click here for a FREE Thawte 
Apache SSL Guide and answer your Apache SSL security 
needs: http://www.gothawte.com/rd523.html

  reply	other threads:[~2002-11-13 23:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200211122006.36454.plcl@telefonica.net>
2002-11-13  8:50 ` snd-usb-audio in ALSA 0.9.0rc5 Clemens Ladisch
2002-11-13 23:34   ` Pedro Lopez-Cabanillas [this message]
2002-11-14  9:09     ` Jaroslav Kysela
2002-11-14 21:23       ` Pedro Lopez-Cabanillas
2002-11-15 14:37         ` Jaroslav Kysela
2002-11-14 10:52     ` 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=200211140034.17681.plcl@telefonica.net \
    --to=plcl@telefonica.net \
    --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.