From: Andrew Geissler <geissonator@gmail.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: "Thomaiyar,
Richard Marian" <richard.marian.thomaiyar@linux.intel.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: System Firmware states on D-Bus
Date: Tue, 25 Feb 2020 13:10:14 -0600 [thread overview]
Message-ID: <E41FEB0F-FF3D-49CB-9416-76C2AC7B6EA4@gmail.com> (raw)
In-Reply-To: <20200225160412.GM67957@patrickw3-mbp.dhcp.thefacebook.com>
> On Feb 25, 2020, at 10:04 AM, Patrick Williams <patrick@stwcx.xyz> wrote:
>
> On Tue, Feb 25, 2020 at 07:47:42PM +0530, Thomaiyar, Richard Marian wrote:
>> Prefer D-Bus conveying details in finer / better manner, rather than tying
>> it towards any user facing application like Redfish / IPMI.
>
> I agree with this.
>
> Define internal D-Bus information with the most we have available and
> let external interfaces map this to their constrained subset as
> necessary. There is no reason to limit our own abilities because of the
> management interface du-jour.
Yep, no arguments from me here. The PLDM sensor(or whatever
the right term for it is) will support all defined values sent to it
by the system firmware.
bmcweb will translate what it can when responding to a Redfish
API query for the host state.
I’m thinking I’ll have phosphor-state-manager translate whatever
it can into the OperatingSystemState and BootProgress D-Bus
properties.
>
> --
> Patrick Williams
prev parent reply other threads:[~2020-02-25 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 17:27 System Firmware states on D-Bus Andrew Geissler
2020-02-25 14:17 ` Thomaiyar, Richard Marian
2020-02-25 16:04 ` Patrick Williams
2020-02-25 19:10 ` Andrew Geissler [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=E41FEB0F-FF3D-49CB-9416-76C2AC7B6EA4@gmail.com \
--to=geissonator@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
--cc=richard.marian.thomaiyar@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.