From: Takashi Iwai <tiwai@suse.de>
To: Thierry Vignaud <tvignaud@mandrakesoft.com>
Cc: Jaroslav Kysela <perex@users.sourceforge.net>,
alsa-devel@alsa-project.org
Subject: Re: Re: [alsa-cvslog] CVS: alsa-kernel/isa cmi8330.c,1.10,1.11
Date: Mon, 16 Sep 2002 18:06:15 +0200 [thread overview]
Message-ID: <s5hofaxsyvc.wl@alsa2.suse.de> (raw)
In-Reply-To: <m265x59b65.fsf@vador.mandrakesoft.com>
At Mon, 16 Sep 2002 18:00:50 +0200,
Thierry Vignaud wrote:
>
> Takashi Iwai <tiwai@suse.de> 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
prev parent reply other threads:[~2002-09-16 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17qVU2-0005tc-00@usw-pr-cvs1.sourceforge.net>
2002-09-16 7:22 ` [alsa-cvslog] CVS: alsa-kernel/isa cmi8330.c,1.10,1.11 Thierry Vignaud
2002-09-16 10:31 ` Takashi Iwai
2002-09-16 10:51 ` Thierry Vignaud
2002-09-16 14:35 ` Takashi Iwai
2002-09-16 16:00 ` Thierry Vignaud
2002-09-16 16:06 ` Takashi Iwai [this message]
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=s5hofaxsyvc.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=perex@users.sourceforge.net \
--cc=tvignaud@mandrakesoft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.