Message-ID: <3AAF811F.9C4F83E2@didntduck.org>
Date: Wed, 14 Mar 2001 09:33:03 -0500
From: Brian Gerst <bgerst@didntduck.org>
MIME-Version: 1.0
To: mshiju@in.ibm.com
CC: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ISAPNP :driver not recognized when compiled in kernel
In-Reply-To: <CA256A0F.004A726A.00@d73mta05.au.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

mshiju@in.ibm.com wrote:
> 
> Hello,
>            I have a basic question. Can we build a PnP ISA driver in kernel
> with ISAPNP kernel option enabled so that kernel PnP does the job of
> allocating the resources for the driver. The problem being that the
> /etc/isapnp.conf should be executed before the device driver. I tried this
> and was unsuccessful but worked fine when the driver was compiled as a
> module. I read somewhere that ISAPNP drivers with ISAPNP enabled in kernel
> should only be build as modules so that we can keep the order of execution
> . Is this true.? Have any one of you tried this .
> 
> Thanks & Regards
> Shiju

If you build ISAPnP support into the kernel you should not be using the
isapnp userspace tools.  Use on or the other, but not both.  The ISAPnP
system when non-modular is initialized before built-in drivers, so they
do not have to be modular.  With the old userspace tools they must be
modular.

--

				Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/