From: Dave Jones <davej@suse.de>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'Pavel Machek'" <pavel@suse.cz>,
Brad Hards <bhards@bigpond.net.au>,
Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] i386 "General Options" - begone [take 2]
Date: Wed, 5 Jun 2002 00:09:02 +0200 [thread overview]
Message-ID: <20020605000902.A4751@suse.de> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C02AB7ED8@orsmsx111.jf.intel.com>
<trivial patchbot removed from Cc:>
On Tue, Jun 04, 2002 at 02:58:35PM -0700, Grover, Andrew wrote:
> So, let's assume in the very near future it becomes possible to compile a
> kernel without MPS or $PIR support. Where should those config options go?
Why do they need to be options ? They should be implied if CONFIG_ACPI=n
Otherwise we could build a kernel without any PCI IRQ routing, MPS
discovery etc.. I can't see the benefit of making this stuff compile
time optional other than to save a few bytes (and there are much better
places to start attacking to save space than this).
> These, in addition to pnpbios, are also unneeded with ACPI.
As long as the target box has working ACPI tables and we don't have
to fall back to legacy tables.
> That is why I
> was advocating the more general "Platform interface options" menu, so we
> could have *one* place to config these and ACPI in or out, instead of having
> the many different platform interface options in different logical areas.
Can you confirm that you're not advocating a "ACPI or Legacy" approach ?
I think you're aware of the dragons that lie that way, but I want to be
sure my suspicions are unfounded.
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-06-04 22:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 21:58 [patch] i386 "General Options" - begone [take 2] Grover, Andrew
2002-06-04 22:09 ` Dave Jones [this message]
2002-06-04 23:16 ` Alan Cox
2002-06-07 5:38 ` fchabaud
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 23:31 Grover, Andrew
2002-06-04 23:09 Grover, Andrew
2002-06-04 23:25 ` Dave Jones
2002-06-05 1:00 ` Alan Cox
2002-06-04 20:59 Grover, Andrew
2002-06-04 21:20 ` Dave Jones
2002-06-05 1:34 ` Brad Hards
2002-06-05 10:29 ` Dave Jones
2002-06-05 23:11 ` Brad Hards
2002-06-03 1:56 Linux 2.5.20 Linus Torvalds
2002-06-03 3:18 ` [patch] i386 "General Options" - begone [take 2] Brad Hards
2002-06-03 22:42 ` Rusty Russell
2002-06-04 14:09 ` Pavel Machek
2002-06-04 22:05 ` Brad Hards
2002-06-02 5:16 ` Pavel Machek
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=20020605000902.A4751@suse.de \
--to=davej@suse.de \
--cc=andrew.grover@intel.com \
--cc=bhards@bigpond.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.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.