From: Matthew Garrett <mjg59@srcf.ucam.org>
To: yakui.zhao@intel.com
Cc: minyard@acm.org, lenb@kernel.org,
openipmi-developer@lists.sourceforge.net,
linux-acpi@vger.kernel.org, Bjorn Helgaas <bjorn.helgaas@hp.com>,
Myron Stowe <myron.stowe@hp.com>
Subject: Re: [PATCH -v6 2/2] IPMI: use ACPI detection mechanism firstly to detect IPMI system interface
Date: Mon, 7 Jun 2010 13:52:13 +0100 [thread overview]
Message-ID: <20100607125213.GA8277@srcf.ucam.org> (raw)
In-Reply-To: <1275902842-19895-3-git-send-email-yakui.zhao@intel.com>
On Mon, Jun 07, 2010 at 05:27:22PM +0800, yakui.zhao@intel.com wrote:
> Use the ACPI detection mechanism firstly to detect the IPMI system interface
> so that we can know which IPMI system interface is detected in ACPI namespace and
> then install the IPMI opregion to enable ACPI to access the BMC controller.
> But the hardcode detection mechanism is still put in the first order.
This is less than ideal. I've seen several machines where the PCI IPMI
device is the only one to provide interrupts, so using the ACPI one and
refusing to register the PCI one isn't really an option.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-06-07 12:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 9:27 [PATCH -v6 0/2] IPMI: Install the ACPI IPMI opregion yakui.zhao
2010-06-07 9:27 ` [PATCH -v6 1/2] IPMI: Install the IPMI space handler to enable ACPI to access the BMC controller yakui.zhao
2010-06-07 9:27 ` [PATCH -v6 2/2] IPMI: use ACPI detection mechanism firstly to detect IPMI system interface yakui.zhao
2010-06-07 12:52 ` Matthew Garrett [this message]
2010-06-08 1:28 ` ykzhao
2010-06-08 1:34 ` Matthew Garrett
2010-06-08 5:10 ` ykzhao
2010-06-09 3:02 ` Myron Stowe
2010-06-09 13:08 ` Corey Minyard
2010-06-10 2:34 ` ykzhao
2010-06-10 3:12 ` Corey Minyard
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=20100607125213.GA8277@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=minyard@acm.org \
--cc=myron.stowe@hp.com \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=yakui.zhao@intel.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 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).