From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: config bug with sbawe and --with-isapnp=no Date: Mon, 26 Jan 2004 12:15:33 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <200401221249.07577.loritz@fh-furtwangen.de> <200401241557.21770.loritz@fh-furtwangen.de> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <200401241557.21770.loritz@fh-furtwangen.de> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: loritz@fh-furtwangen.de Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Sat, 24 Jan 2004 15:57:21 +0100, Mario Loritz wrote: > > Am Freitag, 23. Januar 2004 12:49 schrieb Takashi Iwai: > > i found the bug in adriver.h, which always defines CONFIG_PNP when > > CONFIG_ISAPNP is set. > > > > the attached patches are the fix and clean-up for pnp. > > please give a try. > > > > > > Takashi > > After I applied the patches, something strange is happening: > The module option "isapnp=yes/no" is not recognized anymore, > regardless of the configure option "--with-isapnp=yes" or "no". > > The driver itself works, even if I compile with pnp. But why? I > cannot tell the driver, that it shouldn't try pnp. Do you think > the driver will still work when a pnp-card is used? I can't check > this, because my sbawe32 is non-pnp. > > When those questions are answered and the module option > "isapnp=yes/no" really isn't needed anymore, then I think the > driver should be changed in the proposed way. did you run cvscompile? otherwise it won't work properly. Takashi ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn