mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brad Hards <bhards@bigpond.net.au>
To: Dave Jones <davej@suse.de>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	trivial@rustcorp.com.au
Subject: Re: [patch] i386 "General Options" - begone [take 2]
Date: Thu, 6 Jun 2002 09:11:20 +1000	[thread overview]
Message-ID: <200206060911.20027.bhards@bigpond.net.au> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C02AB7ED5@orsmsx111.jf.intel.com> <200206051134.24063.bhards@bigpond.net.au> <20020605122939.H5277@suse.de>

On Wed, 5 Jun 2002 20:29, Dave Jones wrote:
> On Wed, Jun 05, 2002 at 11:34:23AM +1000, Brad Hards wrote:
>  > One idea that comes to mind is putting the power management config
>  > options in a "Power Management" section
>
> *nod* sounds sensible 8)
>
>  > then PNPBIOS in with the other PnP stuff, and
>  > so on (read: don't know were to put MPS yet, and don't know what $PIR is
>  > :)
>
> It's an interrupt routing table.
>
> MPS and interrupt routing are both CPU related features, so the best
> place we currently have is under the CPU menu imho.
Is it fundamentally different _functionality_ to the stuff that is in "Plug 
and Play configuration" (which makes devices automatically get the right 
itnerrupts)?  [ Ignore implementation for a second - we can always solve this 
with another layer of abstraction. :-]

Of course, putting all this into the CPU menu (which is obviously a per-arch 
config.in change) would make drivers/arch/acpi/Config.in look a lot cleaner.

I'll try to work with Andy Grover off-list with this, and come up with an 
agreed position.

Rusty: This is starting to get a little non-trivial. Please drop the two 
patches I've sent. I'll get back to you later.

Brad
-- 
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.

  reply	other threads:[~2002-06-05 23:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- 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 21:58 Grover, Andrew
2002-06-04 22:09 ` Dave Jones
2002-06-04 23:16 ` Alan Cox
2002-06-07  5:38   ` fchabaud
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=200206060911.20027.bhards@bigpond.net.au \
    --to=bhards@bigpond.net.au \
    --cc=andrew.grover@intel.com \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@rustcorp.com.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®