From alsa-devel-owner@alsa.jcu.cz  Mon Jan 18 22:15:31 1999
Received: from entry.jcu.cz (IDENT:perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id WAA10450;
	Mon, 18 Jan 1999 22:07:21 +0100
Date: Mon, 18 Jan 1999 22:07:21 +0100 (CET)
From: Jaroslav Kysela <perex@jcu.cz>
To: Erik Inge Bolso <knan@mo.himolde.no>
cc: alsa-user@alsa.jcu.cz, alsa-devel@alsa.jcu.cz
Subject: Re: Another one bites the dust... Multiple cards & ISA PnP issue...
In-Reply-To: <Pine.LNX.4.05.9901180458080.2854@balder.mo.himolde.no>
Message-ID: <Pine.LNX.3.96.990118220330.25147F-100000@entry.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

On Mon, 18 Jan 1999, Erik Inge Bolso wrote:

> 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?

It's true that SB16 module must handle both ISA PnP soundcards and non-PnP
SB16 soundcards. Can you try use option snd_skip_isapnp=1 for your snd-sb16
module? I don't know how can be better solved this problem. Maybe we can
create some special module for non-PnP SB16 soundcards. Any other ideas?

							Jaroslav

-----
Jaroslav Kysela <perex@jcu.cz>
Academic Computer Centre, University of South Bohemia
Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic


