From: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Adam Belay <ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>
Subject: Re: ACPI_BUS dependency for CONFIG_PNP
Date: Mon, 15 Nov 2004 18:35:25 +0100 [thread overview]
Message-ID: <20041115173525.GD13402@wotan.suse.de> (raw)
In-Reply-To: <1100536966.5518.947.camel@d845pe>
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
>
> 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.
-Andi
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next prev parent reply other threads:[~2004-11-15 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 11:46 ACPI_BUS dependency for CONFIG_PNP Andi Kleen
[not found] ` <20041115114654.GJ1662-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-11-15 16:42 ` Len Brown
2004-11-15 17:35 ` Andi Kleen [this message]
[not found] ` <20041115173525.GD13402-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-11-16 5:41 ` Adam Belay
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=20041115173525.GD13402@wotan.suse.de \
--to=ak-l3a5bk7wagm@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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.