archive mirror
 help / color / mirror / Atom feed
From: Mikael Pettersson <>
Subject: RE: ACPI patches updated (20030714)
Date: Tue, 15 Jul 2003 20:49:29 +0200 (MEST)	[thread overview]
Message-ID: <> (raw)

On Tue, 15 Jul 2003 11:07:29 -0700, "Brown, Len" wrote:
>Ps. Below is the current plan for ACPI build and boot knobs.  Except for the
>config syntax -- 2.4 and 2.5 should end up the same.  Let me know if we
>missed anything.
>Audit of ACPI build and boot options
>Scrubbed w/ Andy 7/10 -- see TODO for Lenb's plan
>Build Options
>Indentation shows dependency (from acpi/Kconfig, Makefile)
>	depends on X86 && ACPI && X86_LOCAL_APIC
>	:= acpitable.o
>	TODO: simplify acpitable.c to only to LAPIC enumeration for HT
>		It probably shouldn't parse the non-LAPIC MADT entries

I would like to see HT_ONLY generalized to parsing the MADT for
I/O-APICs. The problem I have is that some mainboards, like my
i850 ASUS P4T-E, have I/O-APICs but no MP tables. The only way for
the Linux kernel to discover the I/O-APICs on these mainboard is
through MADT parsing.

However, this currently requires me to enable all of ACPI, which
I don't need or want for many reasons, including code bloat and
behavioural side-effects.

Replacing "HT_ONLY" with "MADT_PARSING_ONLY" would be ideal, IMO.


             reply	other threads:[~2003-07-15 18:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 18:49 Mikael Pettersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-16 20:55 ACPI patches updated (20030714) Mikael Pettersson
2003-07-16 20:36 Grover, Andrew
2003-07-16  9:47 Mikael Pettersson
2003-07-16  2:35 Brown, Len
2003-07-15 19:11 Grover, Andrew
2003-07-15 18:07 Brown, Len
2003-07-15 19:02 ` Hugh Dickins
2003-07-15 17:21 Grover, Andrew
2003-07-15 17:38 ` Hugh Dickins
2003-07-15 16:53 Grover, Andrew
2003-07-15 17:11 ` Hugh Dickins
2003-07-15 17:57 ` Tugrul Galatali

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).