On Wed, 2002-12-18 at 03:17, Takashi Iwai wrote: > At Wed, 18 Dec 2002 11:46:45 +0100, > I wrote: > > > > > It would be better to make the alsasound script more robust (and > > > independent of the startup order) and able to deal with partially loaded > > > modules, so instead of just checking for the /proc/asound directory it > > > would actually see what modules are already loaded and only load those > > > that are not. It does not look too easy, it seems that /proc/asound does > > > not provide a list of loaded modules (rather a list of cards that are > > > not associated with module names). > > > > agreed. a scenario i can imagine now is that the script just takes a > > look at /proc/asound/cards and checks the numbers at the first column. > > this should correspond to the card indices which have been already > > loaded. then the script will try to load the modules snd-card-X but > > skip the numbers listed in the above... > > i'll try to rewrite as this way. > > after reconsideration: it would be much simpler to create a new proc > file which shows the modules already loaded. > I was wondering what would happen in this process if someone had two r three identical USB devices, like the MidiMan 2X2? OR also two identical cards like the RME HDSP 9652?
It is important that the system recognize the same hardware as the same sound device every time the machine booted, and whether the machine is warm or cold booted. The name I'm seeing linked in /dev/sound are possibly a bit too generic, being just '2X2' and 'DSP'. Just a thought. ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
