From alsa-user-owner@alsa.jcu.cz  Mon Jan 18 06:33:57 1999
Received: from yme.mo.hiMolde.no (qmailr@[158.38.74.10])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id GAA07163
	for <alsa-user@alsa.jcu.cz>; Mon, 18 Jan 1999 06:31:12 +0100
Received: (qmail 1594 invoked by uid 633); 18 Jan 1999 05:31:11 -0000
Date: Mon, 18 Jan 1999 06:31:11 +0100 (CET)
From: Erik Inge Bolso <knan@mo.himolde.no>
To: alsa-user@alsa.jcu.cz, alsa-devel@alsa.jcu.cz
Subject: Another one bites the dust... Multiple cards & ISA PnP issue...
Message-ID: <Pine.LNX.4.05.9901180458080.2854@balder.mo.himolde.no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

Well well. I just tried ALSA for the first time, and was positively
surprised... it has a lot cleaner structure than OSS, and much better
feedback. Which brings me to the multiple-cards & native isa pnp... 

I have a GUS PnP and a SB 16 (non-PnP) in my machine. When I do a
"modprobe snd-sb16", isapnp.o kicks in, finds the Gus and assigns it its
preferred values. These preferred values (i/o address 0x220 & dma 5)
happens to be the same the sb16 is set to. -Then the snd-sb16.o tries to
find the sb16, and naturally fails with a "device busy". This probably can
be overcome with some creative patching of Makefiles and/or adding options
to either isapnp.o (THESE_RESOURCES_ARE_RESERVED=xxx) or snd-sb16.o
(NO_ISA_PNP=TRUE)...

What do you think?

--
Erik I. Bols <knan at mo.himolde.no>
The White Tower: http://www.mo.himolde.no/~knan/




