At 17 Dec 2002 11:36:10 -0800, Fernando Pablo Lopez-Lezcano wrote: > > On Tue, 2002-12-17 at 03:06, Takashi Iwai wrote: > > At 16 Dec 2002 19:46:55 -0800, > > Mark Knecht wrote: > > > On Mon, 2002-12-16 at 18:51, Paul Davis wrote: > > > > i think it would something like this: > > > > > > > > options snd-hdsp snd_index=0 > > > > options snd-usb-foo snd_index=1 > > > > > > > > i'm sure that takashi or jaroslav will correct me if i got this wrong. > > > > > > This makes perfect sense, and it isn't what I did. (!!) > > > > > > The PlanetCCRMA has a Nano-HOWTO on how to install the MidiMan 2X2 by > > > hand. It's a little USB-based MIDI interface (not a sound card) that is > > > not recognized by alsaconf, so we do a bit of editing by hand. > > > > the behavior depends on the order of booting. > > if the hotplug service is booted before the alsasound init script, > > hotplug will start the snd-usbaudio module, which will be assigned as > > the first empty device, i.e. device #0, unless you specify the index > > option. and afterwards, the alsasound script is started, and it > > results in the confliction of devices. > > > > setting an index option is one of the solutions. > > in this case, the first usb-audio/midi device will be forced to be > > assigned to #1. so, it's safe to start it beforehand. > > > > but, when we take a deeper look at this, we find another problem. > > the alsasound init script checks whether the ALSA was already started > > by checking the existence of /proc/asound directory. and, if hotplug > > started the usb-audio/midi before alsasound, this directory would be > > also created because the alsa core was started without help of > > alsasound init script, too. this leads to the skip of loading of any > > other soundcards, because alsasound will quit immediately. > > > > after all, a simple solution for this is to make sure that alsasound > > starts before hotplug. then, even the index option for snd-usbaudio > > wouldn't be necessary (in theory). > > I think that in RedHat hotplug is not started as a service so we cannot > make sure that alsasound starts first (at least not easily - I have to > check again on the startup scripts to see what is done and when). hmm, then it's difficult to assume the order... in most cases, hotplug is started at the fairly early stage of boot sequences, because it supports also the fundamental devices such like network.
> 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. > > in the above scenario, anyway, cards_limit must be changed. and i > > think it's a bit annoying. > > > > the attached patch will change the handling of cards_limit option. > > with the patch, the alsa won't restrict the number of cards per > > cards_limit option, but only limits the auto-probing via kmod. > > i.e. you can load more card modules even with cards_limit=1. > > That sounds reasonable. fine, does anybody see a drawback? Takashi ------------------------------------------------------- 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
