public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: arch/ia64/kernel/mca.c and CONFIG_ACPI
Date: Wed, 08 Feb 2006 03:22:42 +0000	[thread overview]
Message-ID: <1139368962.26420.144.camel@localhost> (raw)
In-Reply-To: <10584.1139367384@kao2.melbourne.sgi.com>

On Wed, 2006-02-08 at 13:56 +1100, Keith Owens wrote:
> If CONFIG_ACPI is no then arch/ia64/kernel/mca.c drops the CPE handler,
> but not the CMC handler.  Also the CPE handler uses
> acpi_request_vector(), but CMC does not.  Why the differences?

   Probably a bug, because we could still poll for CPEs w/o ACPI.
Originally the CPE handler was only interrupt driven and the interrupt
is described as a platform interrupt source via ACPI.  So it made sense
then.  CMC have never had an ACPI dependency since the architecture
defines their setup and not the platform.

	Alex


      reply	other threads:[~2006-02-08  3:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08  2:56 arch/ia64/kernel/mca.c and CONFIG_ACPI Keith Owens
2006-02-08  3:22 ` Alex Williamson [this message]

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=1139368962.26420.144.camel@localhost \
    --to=alex.williamson@hp.com \
    --cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox