From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Re: [alsa-cvslog] CVS: alsa-kernel/isa cmi8330.c,1.10,1.11 Date: Mon, 16 Sep 2002 18:06:15 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by alsa.alsa-project.org (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id SAA15657 for ; Mon, 16 Sep 2002 18:06:17 +0200 In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Thierry Vignaud Cc: Jaroslav Kysela , alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Mon, 16 Sep 2002 18:00:50 +0200, Thierry Vignaud wrote: > > Takashi Iwai writes: > > > > > cmi8330 works even without isapnp. hence CONFIG_ISAPNP should > > > > not be added in config.in. > > > > > > for all models ? > > > > not sure... > > > > > i had once a cmi8330 (well something like four years ago) and at > > > that time it would only works after playing with isapnptools. > > > > then CONFIG_ISAPNP should not be in the dependency list. the driver > > wouldn't be compiled once if CONFIG_ISAPNP=n, even though you could > > use the card with help of isapnptools. > > but alsa donation of isapnp to the core kernel made isapnptools > obsoloted since. yes but users can still choose not to build isapnp support into the kernel. and with your patch (btw you forgot $ before CONFIG_ISAPNP), the cmi8330 module will not be _built_ in such a case. that's the problem. Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf