Re: [Openipmi-developer] IPMI device discovery [was Re: [PATCH ] IPMI: Locate the IPMI system interface in ACPI namespace]

[Rocky Craig <rocky.craig@hp.com>]

Bjorn Helgaas emitted:

> I think the only reason
> the SPMI table exists at all is to allow an OS to find an IPMI system
> interface during early boot, before the OS is prepared to parse the
> ACPI namespace. 

Correct.  This was driven by HP-UX as an extension to both ACPI and
IPMI specifications.  The HP-UX kernel is "IPMI-aware" (specifically,
writing the SEL) whereas Linux is not.

> Anything described by the SPMI should also be described in the namespace.

I believe that distinction/request/requirement was lost "back in the day".

> Linux does not need to use IPMI during that early boot phase, so I
> think the SPMI detection should be dropped completely, 

I don't know if SPMI caught on with other hardware vendors.  As it is in the
two specifications, dropping it should be given some thought.

Corey, any idea on general SPMI use?

> I have been told that Windows is similar in that it does not use IPMI
> during early boot, and that it does not look at the SPMI table at all,
> so I think relying on the namespace would be fairly safe.

Sounds like a good vote to drop.  Another vote for dropping comes from
incomplete info in the SPMI table regarding interrupt type and polarity.
Relying on SPMI almost forces you to run the driver in polled mode.

Rocky