All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deepak Kodihalli <dkodihal@linux.vnet.ibm.com>
To: Sunitha Harish <sunithaharish04@gmail.com>,
	patrick@stwcx.xyz, dkodihal@in.ibm.com,
	suryakanth.sekar@linux.intel.com,
	openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Storing host data on the BMC
Date: Mon, 4 May 2020 21:26:24 +0530	[thread overview]
Message-ID: <f4df91bd-d60c-5f4b-ef08-2e3fdd163b4e@linux.vnet.ibm.com> (raw)
In-Reply-To: <CADeuMvXQfS01sdwpiM+POkaqdVesj64XGDqPWAPreo_TPbuV8A@mail.gmail.com>

On 04/05/20 8:22 pm, Sunitha Harish wrote:
> Hi,
> 
> We have some user defined host settings which we are presently keeping 
> it in phosphor-settings-manager and the associated pldm bios attributes 
> are there in the pldm BIOS table. Few properties in the object hosted by 
> the phosphor-settings-manager are read-only for out of band but through 
> in-band it can be changed.
> 
> For example; the IP origin (static/dhcp) in the below commit.
> https://gerrit.openbmc-project.xyz/#/c/openbmc/meta-ibm/+/30205/

Is the Origin property here a host setting/BIOS attribute? I don't 
believe it is. From a PLDM perspective, this is a sensor that the host 
can update and notify the BMC via an event, for eg. Even if you make it 
read-only, it is not a setting for the host firmware - which is what 
BIOS attributes are meant for.

Thanks,
Deepak

  reply	other threads:[~2020-05-04 15:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 14:52 Storing host data on the BMC Sunitha Harish
2020-05-04 15:56 ` Deepak Kodihalli [this message]
2020-05-05  6:42   ` Sunitha Harish
2020-05-05  6:59     ` Deepak Kodihalli
2020-05-06  7:23       ` Sunitha Harish
2020-05-11  6:14         ` Sunitha Harish
2020-05-11 12:07           ` Patrick Williams
2020-05-11 16:05             ` Sunitha Harish
2020-05-13 15:07               ` Sunitha Harish
2020-05-13 15:27                 ` Deepak Kodihalli
2020-05-13 21:18                 ` Patrick Williams
2020-05-14  3:43                   ` Deepak Kodihalli
2020-05-14 12:33                     ` Patrick Williams
2020-05-18 11:53                       ` Sunitha Harish
2020-05-21  5:12                         ` Sunitha Harish
2020-05-21  5:16                           ` Deepak Kodihalli
2020-05-21 10:30                             ` Sunitha Harish
2020-05-22  3:59                             ` Sunitha Harish
2020-05-29 10:57                               ` Sunitha Harish
2020-05-29 11:03                                 ` Deepak Kodihalli
2020-05-29 11:26                                   ` Sunitha Harish

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=f4df91bd-d60c-5f4b-ef08-2e3fdd163b4e@linux.vnet.ibm.com \
    --to=dkodihal@linux.vnet.ibm.com \
    --cc=dkodihal@in.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    --cc=sunithaharish04@gmail.com \
    --cc=suryakanth.sekar@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.