<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/provingground.git/settings/include, branch master</title>
<subtitle>Intel BMC provingground (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/atom?h=master</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/'/>
<updated>2020-02-24T16:49:07+00:00</updated>
<entry>
<title>Change the CapabilitiesFlags property into booleans</title>
<updated>2020-02-24T16:49:07+00:00</updated>
<author>
<name>Karthick Sundarrajan</name>
<email>karthick.sundarrajan@intel.com</email>
</author>
<published>2019-11-25T20:17:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=1a380b0a106eb9194fb271212e821141d09f0812'/>
<id>urn:sha1:1a380b0a106eb9194fb271212e821141d09f0812</id>
<content type='text'>
Each bit in CapabilitiesFlags dbus property is a chassis
capability. Setting a capability overwrites other capabilities.
Read-and-update of the property results in race condition/confusion.
To tackle this, added a boolean property for each of chassis
capability. The new properties will be read and updated in ipmi
command handling code.

The capabilities listed below are supported by Intel and so enabled
the corresponding bits/properties by default.
1. Intrusion sensor (bit 0)
2. Front panel lockout (bit 1)
3. NMI (bit 2)

The original CapabilitiesFlags property will be deprecated once the
changes are made to use new booleans in all the repos.

Tested:
------

root@intel-obmc:~# ipmitool raw 0x00 0x00
 07 22 44 66 88 aa

Change-Id: I7f9ec00c1bf94d550dd000634011ef8e7a460967
Signed-off-by: Karthick Sundarrajan &lt;karthick.sundarrajan@intel.com&gt;
</content>
</entry>
<entry>
<title>Increase the timeout value to fix netipmid crash issue during stress test</title>
<updated>2020-02-13T12:58:58+00:00</updated>
<author>
<name>Yong Li</name>
<email>yong.b.li@linux.intel.com</email>
</author>
<published>2020-02-13T12:56:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=414068e084f9865a1c3dc4fc98b7be3de4cdb667'/>
<id>urn:sha1:414068e084f9865a1c3dc4fc98b7be3de4cdb667</id>
<content type='text'>
During stress test, netipmid service will crash with "bad executor" error,
the current Character Accumulate Interval is too small,
after increase it to 100, no more crash issue.

Tested:
Start "ipmitool sel list", "ipmitool sensor list"
and "ipmitool sol looptest 200 500" at the same time,
no "sol looptest fail" error

Change-Id: Idf8ba1fdc3478bda408cf668f671411a02574b68
Signed-off-by: Yong Li &lt;yong.b.li@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Change the bios version dbus interface to align with bmcweb</title>
<updated>2020-01-13T00:34:49+00:00</updated>
<author>
<name>Yong Li</name>
<email>yong.b.li@linux.intel.com</email>
</author>
<published>2019-12-18T11:46:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=b6cdb90744eba8680dc0ac6ba6de31ec84cb500a'/>
<id>urn:sha1:b6cdb90744eba8680dc0ac6ba6de31ec84cb500a</id>
<content type='text'>
bmcweb uses the software interface for bios version query in redfish,
to align with it, the settings service implements the software interface,
this reference needs to be changed too

Tested:
AC cycle the host, BiosVersion is the correct bios version:
https://$BMCIP/redfish/v1/Systems/system

Change-Id: I619de9ff1a2356b7da1c59cfa139344cc2114eeb
Signed-off-by: Yong Li &lt;yong.b.li@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Implement Software interface to support bios version in redfish</title>
<updated>2019-12-18T00:56:21+00:00</updated>
<author>
<name>Yong Li</name>
<email>yong.b.li@linux.intel.com</email>
</author>
<published>2019-12-13T09:38:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=ed94916f1bfeb685071ee3c5ed9d9912c1929032'/>
<id>urn:sha1:ed94916f1bfeb685071ee3c5ed9d9912c1929032</id>
<content type='text'>
bmcweb uses the Software.Activation interface to query the bios version,
implement the Software.Activation
and Association.Definitions to support the query.

Tested:
 https://$BMCIP/redfish/v1/Systems/system contains the BiosVersion:
"BiosVersion": "NA",

Change-Id: I77fdefc5962bfc7715b125ccfec0ec57e9dd0f55
Signed-off-by: Yong Li &lt;yong.b.li@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Adding RequestedApplyTime property to settings</title>
<updated>2019-12-06T02:17:21+00:00</updated>
<author>
<name>Vikram Bodireddy</name>
<email>vikram.bodireddy@linux.intel.com</email>
</author>
<published>2019-12-05T09:35:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=eddf621897090ba346b1aaa81a4b8be12076ab60'/>
<id>urn:sha1:eddf621897090ba346b1aaa81a4b8be12076ab60</id>
<content type='text'>
Added "RequestedApplyTime" to settings service which
will be used in firmware update. This will give option
for user to set the firmware image activation like
activate image 'Immediate' or Activate image on 'OnReset'
etc.

Tested:
Changed the setting using Redfish, rebooted BMC and
validated the preserved 'RequestedApplyTime' setting.

Change-Id: Ib08bb82fcc651f5489d69928ddaa7e1f05ebfdcf
Signed-off-by: Vikram Bodireddy &lt;vikram.bodireddy@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Make SOL progess not persist</title>
<updated>2019-12-03T00:35:40+00:00</updated>
<author>
<name>James Feist</name>
<email>james.feist@linux.intel.com</email>
</author>
<published>2019-12-03T00:35:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=450456c8baad413d8d5fe9fc8a4720b173aaa433'/>
<id>urn:sha1:450456c8baad413d8d5fe9fc8a4720b173aaa433</id>
<content type='text'>
This gets initialized in IPMI to 0 every boot anyways,
might as well just make it not persist.

Tested: Doesn't persist

Change-Id: I068cc0fc48533f334752da68d8f51b208cfdbe48
Signed-off-by: James Feist &lt;james.feist@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Fix Settings Vector Problem</title>
<updated>2019-11-11T19:23:14+00:00</updated>
<author>
<name>James Feist</name>
<email>james.feist@linux.intel.com</email>
</author>
<published>2019-11-11T19:23:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=f80c33718f07dcb9be8d05a92c1e902e32947e08'/>
<id>urn:sha1:f80c33718f07dcb9be8d05a92c1e902e32947e08</id>
<content type='text'>
{} only initalizes the std::optional, not the thing
in the optional. Intialize it correctly.

Tested: Warnings went away, on reboot changes persisted

Change-Id: I3c40317f077d241f0dc938910a28876f911d8021
Signed-off-by: James Feist &lt;james.feist@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Move NMI source Property from intel-dbus-interface to phospher-dbus-interfaces</title>
<updated>2019-10-30T22:59:11+00:00</updated>
<author>
<name>Chen Yugang</name>
<email>yugang.chen@linux.intel.com</email>
</author>
<published>2019-10-30T00:28:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=cda29d96173253dbf8d806ae7ff3f46bfa178483'/>
<id>urn:sha1:cda29d96173253dbf8d806ae7ff3f46bfa178483</id>
<content type='text'>
System needs to keep the NMI signal event source by this Property, this
interface is used to support the access the Property with default value.
it's convenient for other repos to use it by moving from "com.intel" to
"xyz.openbmc_project".

Tested
it's tested in system for IPMI OEM command - get/set NMI source

Change-Id: I2df4e577eff30b4a82b2face0c6dead2a20a6e2d
Signed-off-by: Chen Yugang &lt;yugang.chen@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Remove RestartCause setting</title>
<updated>2019-09-19T21:38:08+00:00</updated>
<author>
<name>Jason M. Bills</name>
<email>jason.m.bills@linux.intel.com</email>
</author>
<published>2019-09-19T21:01:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=75ccc327b196f3eacea9612f226fd971ea3ff82d'/>
<id>urn:sha1:75ccc327b196f3eacea9612f226fd971ea3ff82d</id>
<content type='text'>
RestartCause is handled by power-control, so remove it from
settings.

Tested:
Combined with the power-control changes, triggered software, command,
button, watchdog, and power restore restart types and confirmed that
the restart cause was correctly reported.

Change-Id: I748c70749bdb7169e483758e6af7a58fef2319a5
Signed-off-by: Jason M. Bills &lt;jason.m.bills@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Add setting for ResetOnSMI option</title>
<updated>2019-08-19T17:53:39+00:00</updated>
<author>
<name>Jason M. Bills</name>
<email>jason.m.bills@linux.intel.com</email>
</author>
<published>2019-08-16T19:44:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=3834cee5c0cf03a4ef11e860a0355fcb0c7dd95c'/>
<id>urn:sha1:3834cee5c0cf03a4ef11e860a0355fcb0c7dd95c</id>
<content type='text'>
Tested:
Combined with the IPMI command, confirmed that when I enable
and disable reset on SMI, the value is correctly stored in
the setting.

Change-Id: I83be31b9edb4758639ab1e242752ae38ef180085
Signed-off-by: Jason M. Bills &lt;jason.m.bills@linux.intel.com&gt;
</content>
</entry>
</feed>
