linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: ykzhao <yakui.zhao@intel.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Myron Stowe <myron.stowe@hp.com>,
	"openipmi-developer@lists.sourceforge.net"
	<openipmi-developer@lists.sourceforge.net>,
	"lenb@kernel.org" <lenb@kernel.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [PATCH -v6 2/2] IPMI: use ACPI detection mechanism firstly to detect IPMI system interface
Date: Wed, 09 Jun 2010 22:12:35 -0500	[thread overview]
Message-ID: <4C105823.90301@acm.org> (raw)
In-Reply-To: <1276137295.4564.22.camel@localhost.localdomain>

ykzhao wrote:
> My first thought is to put the ACPI-IPMI opregion handler into ACPI
> subsystem. But Bjorn suggests that it can be put into the smi code. Then
> I follow his suggestion.
>
> OK. I will rewrite the code and don't tie the ACPI-IPMI opregion handler
> to the smi code.
>   
I think it's ok to be in the ipmi directory, just not directly with the 
SMI code.  I'd put it in its own file, I think.

>     
>   
>> Can you look and see if there is some other way to detect the ACPI 
>> function on a BMC with some other mechanism?  I think that would be 
>> better all around.  If it's the same BMC, the I can't imagine it matters 
>> if you send the messages via the PCI-detected or ACPI-detected mechanisms.
>>     
>
> OK. I will think about it again and try to figure out one solution that
> identify the same BMC via PCI-detected or ACPI-detected and avoids
> adjusting the discovery order. 
>   
Thanks.  If there's some unique message for this function that 
idempotent, you can simply send that message and see if you get an error 
response or not.  This is used for detection ATCA function in some 
cases, for instance.

-corey

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo

      reply	other threads:[~2010-06-10  3:12 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
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 [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=4C105823.90301@acm.org \
    --to=minyard@acm.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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).