Re: ACPI_BUS dependency for CONFIG_PNP

Adam Belay
2004-11-16T05:41:07Z

On Mon, Nov 15, 2004 at 06:35:25PM +0100, Andi Kleen wrote:
> On Mon, Nov 15, 2004 at 11:42:47AM -0500, Brown, Len wrote:
> > On Mon, 2004-11-15 at 06:46, Andi Kleen wrote:
> > > 2.6.10rc2 got this new dependency:
> > >
> > > config PNP
> > > bool "Plug and Play support"
> > > depends on ISA || ACPI_BUS
> > >
> > > from the ACPI update. This enables ISA-PNP on x86-64, where
> > > it was always disabled previously and is completely useless. Can
> > > someone
> > > explain the rationale behind that change? IMHO you should never use
> > > ISA-PNP without CONFIG_ISA.
> >
> > Linux PNP handles up to 3 protocols:
> > ISAPNP -- useful only if CONFIG_ISA, independent of PNPBIOS and PNPACPI
> > PNPBIOS -- useful only if acpi_disabled
> > PNPACPI -- useful if !acpi_disabled
>
> Useful for what? As far as I know no device on x86-64 needs PNPBIOS
> or PNPACPI

Most x86-64 hardware still utilizes ACPI for certain devices.

>
> >
> > drivers/pnp/isapnp/Kconfig appears to already have the dependency you're
> > looking for to make sure that ISAPNP is not defined without CONFIG_ISA:
> >
> > config ISAPNP
> > bool "ISA Plug and Play support"
> > depends on PNP && ISA
> >
>
> Perhaps. But it doesn't work.

In which way doesn't it work? It seems to pretty clearly require ISA support.
Is there a bug?

Thanks,
Adam