public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: ykzhao <yakui.zhao@intel.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Rocky Craig <rocky.craig@hp.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"openipmi-developer@lists.sourceforge.net"
	<openipmi-developer@lists.sourceforge.net>,
	Myron Stowe <myron.stowe@hp.com>,
	"minyard@acm.org" <minyard@acm.org>,
	"lenb@kernel.org" <lenb@kernel.org>
Subject: Re: [Openipmi-developer] IPMI device discovery [was Re: [PATCH ] IPMI:	Locate the IPMI system interface in ACPI namespace]
Date: Thu, 19 Nov 2009 19:09:03 +0800	[thread overview]
Message-ID: <1258628943.2933.35.camel@localhost.localdomain> (raw)
In-Reply-To: <200911181419.27238.bjorn.helgaas@hp.com>

On Thu, 2009-11-19 at 05:19 +0800, Bjorn Helgaas wrote:
> On Wednesday 18 November 2009 01:40:57 pm Rocky Craig wrote:
> > Bjorn Helgaas emitted:
> > 
> > > Anything described by the SPMI should also be described in the namespace.
> > 
> > I believe that distinction/request/requirement was lost "back in the day".
> 
> I disagree that this requirement was lost.  The ACPI spec is regrettably
> vague, but I think it still contains the very general requirement that
> the ACPI namespace should describe everything that cannot be found by a
> standard hardware enumeration mechanism.
The detection of IPMI system interface in ACPI namespace is not defined
in ACPI spec. Instead it is defined in IPMI 2.0 spec. The SPMI detection
is also defined in IPMI 2.0 spec. 

ACPI 4.0 spec only defines that the ACPI aml code can access the BMC
controller. 
> 
> That requirement allows the OS to use a single coherent device
> discovery, driver binding, and resource management scheme to cover
> all these devices.  If we had to deal with all these devices piece-
> meal, with an SPMI table here, an SPCR table there, we'd go more
> mad than we already are.
> 
> There may be firmware that has an SPMI but neglects to put the device
> in the namespace.  In my opinion, that's clearly a defect.  I think
> it's unlikely since Windows relies on the namespace, but it's certainly
> a risk.
> 
> Bjorn


  parent reply	other threads:[~2009-11-20  2:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16  9:18 [PATCH ] IPMI: Locate the IPMI system interface in ACPI namespace yakui.zhao
2009-11-16 17:51 ` Bjorn Helgaas
2009-11-17  0:59   ` ykzhao
2009-11-17 14:59     ` Bjorn Helgaas
2009-11-18  3:41       ` ykzhao
2009-11-18 16:45         ` IPMI device discovery [was Re: [PATCH ] IPMI: Locate the IPMI system interface in ACPI namespace] Bjorn Helgaas
2009-11-18 20:40           ` [Openipmi-developer] " Rocky Craig
2009-11-18 21:19             ` Bjorn Helgaas
2009-11-18 21:53               ` Rocky Craig
2009-11-19 11:01                 ` ykzhao
2009-11-30 23:46                   ` Bela Lubkin
2009-11-19 11:09               ` ykzhao [this message]
2009-11-16 20:37 ` [Openipmi-developer] [PATCH ] IPMI: Locate the IPMI system interface in ACPI namespace Bela Lubkin

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=1258628943.2933.35.camel@localhost.localdomain \
    --to=yakui.zhao@intel.com \
    --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=rocky.craig@hp.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