Hi! I agree that a native failback function of ALSA would be the best solution and should definitely be implemented (if possible easily enough). While waiting for that, I've got another idea than udev rules and module loading. Maybe one could create a couple of .asoundrc files for the different possible combinations of devices plugged in (like one for the pci card only and one if the usb card is plugged in). When plugging in or out a card, a script would be launched (with udev or hotplug or whatever) which would find out which devices are available and move the appropriate .asoundrc.combinationX to .asoundrc. This solution allows everything to be configured depending on the available devices. E.g. one might want the surround51 device downmixed to stereo when the usb headset is plugged in, but use the default surround51 device when it's not. When implementing a fallback function in ALSA, there could be a similar thing. Maybe one could define several configuration files with <confdir:pcm/surround.conf> or devide the .asoundrc file in several sections, one for every combination of available devices. Of course, these are just ideas of an user and implementing them might not be what a developper wants. I just want to contribute as much as I can, even if it's only ideas... Regards, Ingo Lee Revell schrieb: > On 2/15/07, Bill Unruh <unruh@xxxxxxxxxxxxxx> wrote: >> On Thu, 15 Feb 2007, Lee Revell wrote: >>> Why muck around with the kernel drivers anyway? This problem should >>> be solvable in userspace (as long as you don't use /dev/dsp apps). >>> >>> ALSA allows addressing devices by name so module loading order is >>> irrelevant. All that's missing is for .asoundrc to support defining a >>> default device with fallback to another card. >> But... it appears to be missing. Ie, if the OP wants to solve his problem >> now, using this will not work. >> >> I agree that unloading the driver if it is in use is problematic. >> > > Yep, I agree. My point was that there's currently no 100% solution > and it might be easier to implement my suggestion than to solve the > problem of unloading drivers with the device open. > > I'll ask about it on the alsa-devel list. > > Lee ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
