From: Takashi Iwai <tiwai@suse.de>
To: loritz@fh-furtwangen.de
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: config bug with sbawe and --with-isapnp=no
Date: Mon, 26 Jan 2004 12:15:33 +0100 [thread overview]
Message-ID: <s5hsmi3ufje.wl@alsa2.suse.de> (raw)
In-Reply-To: <200401241557.21770.loritz@fh-furtwangen.de>
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
next prev parent reply other threads:[~2004-01-26 11:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 11:49 config bug with sbawe and --with-isapnp=no Mario Loritz
2004-01-22 12:05 ` Takashi Iwai
2004-01-23 10:13 ` Mario Loritz
2004-01-23 10:26 ` Jaroslav Kysela
2004-01-23 11:49 ` Takashi Iwai
2004-01-24 14:57 ` Mario Loritz
2004-01-26 11:15 ` Takashi Iwai [this message]
2004-01-28 15:45 ` Mario Loritz
2004-01-28 21:53 ` Mario Loritz
2004-01-29 15:12 ` Mario Loritz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hsmi3ufje.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=loritz@fh-furtwangen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox