<feed xmlns='http://www.w3.org/2005/Atom'>
<title>phosphor-host-ipmid/test, branch master</title>
<subtitle>OpenBMC Phosphor local IPMI daemon sources</subtitle>
<id>https://git.raptorcs.com/git/phosphor-host-ipmid/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/phosphor-host-ipmid/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/'/>
<updated>2019-09-25T17:42:56+00:00</updated>
<entry>
<title>Implemented close session cmd in host interface</title>
<updated>2019-09-25T17:42:56+00:00</updated>
<author>
<name>Rajashekar Gade Reddy</name>
<email>raja.sekhar.reddy.gade@linux.intel.com</email>
</author>
<published>2019-07-10T16:54:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=e7023926675030a5976dffda0825445ca0b5ef84'/>
<id>urn:sha1:e7023926675030a5976dffda0825445ca0b5ef84</id>
<content type='text'>
This command can close any session via host interface.

Tested:

Close the existing valid session by session id
ipmitool raw 0x6 0x3c &lt;valid sesssion id &gt;
Response : 00  // success

Close the existing valid session by session handle
ipmitool raw 0x6 0x3c &lt;zero session id&gt; &lt;valid session handle&gt;
Response : 00  // success

Close the session by zero session id
ipmitool raw 0x6 0x3c &lt;zero session id&gt;
Response : 0x87  // inavlid session id

Close the session by zero session handle
ipmitool raw 0x6 0x3c &lt;zero session id&gt; &lt;zero session handle&gt;
Response : 0x88  // inavlid session handle

Close an inactive session.
ipmitool raw 0x6 0x3c &lt;valid session id&gt;
Response : 0xcc  // invalid data field in request

Close an inactive session.
ipmitool raw 0x6 0x3c &lt;zero session id&gt; &lt;valid session hnadle&gt;
Response : 0xcc  // invalid data field in request

Signed-off-by: Rajashekar Gade Reddy &lt;raja.sekhar.reddy.gade@linux.intel.com&gt;
Change-Id: I8af290001d8effbbcdbbe2dd93aabf1b015e7a88
</content>
</entry>
<entry>
<title>drop entity YAML in favor of json provided file</title>
<updated>2019-09-19T17:20:47+00:00</updated>
<author>
<name>Patrick Venture</name>
<email>venture@google.com</email>
</author>
<published>2019-08-19T19:25:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=1ad9da8a7882a643ca28fedbdc614f1855e3669a'/>
<id>urn:sha1:1ad9da8a7882a643ca28fedbdc614f1855e3669a</id>
<content type='text'>
Step 5 of moving from entity map from YAML to JSON drops support for a
built-in YAML mapping of the entity containers.

Tested: Not tested.  No platform upstream updates this YAML file in
their builds.
Signed-off-by: Patrick Venture &lt;venture@google.com&gt;
Change-Id: Ic2918f568f5a6f4a9f9135990889b3bb84a0c81d
</content>
</entry>
<entry>
<title>entitymap: move accessor to separate module</title>
<updated>2019-09-17T01:44:03+00:00</updated>
<author>
<name>Patrick Venture</name>
<email>venture@google.com</email>
</author>
<published>2019-08-23T16:02:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=99bf1c410f4521e1df05c41cd377e9d1232dbdba'/>
<id>urn:sha1:99bf1c410f4521e1df05c41cd377e9d1232dbdba</id>
<content type='text'>
Signed-off-by: Patrick Venture &lt;venture@google.com&gt;
Change-Id: I8c80acb694d067043b77d81dbb9a7ba0057fef56
</content>
</entry>
<entry>
<title>fix logic error for unpack vector of tuple</title>
<updated>2019-09-16T20:12:11+00:00</updated>
<author>
<name>Vernon Mauery</name>
<email>vernon.mauery@linux.intel.com</email>
</author>
<published>2019-07-23T23:49:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=caabc36b6a7596c6a6deb774770f4271f50942e9'/>
<id>urn:sha1:caabc36b6a7596c6a6deb774770f4271f50942e9</id>
<content type='text'>
Unpacking a vector of tuples is failing if the correct number of bytes
does not match an integral number of bytes needed to fully unpack all
the tuples.

Unpacking a tuple should return an error if it does not fully unpack all
the items. This will signal the vector unpack to bail and return however
many items it has unpacked to that point.

A vector unpack should always return success because no matter how many
items it has unpacked, it is fine, because a vector can have any number
of items.

Tested: Unit tests updated to check for proper unpacking of vectors and
        tuples (and optionals) as well as new unit tests added for more
        targetted testing.

Change-Id: I4b45198f8bc4a49913beb923d10079983179402a
Signed-off-by: Vernon Mauery &lt;vernon.mauery@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>entitymap: add json parsing support</title>
<updated>2019-08-20T15:55:01+00:00</updated>
<author>
<name>Patrick Venture</name>
<email>venture@google.com</email>
</author>
<published>2019-08-16T17:50:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=02e32376817529e960bb918417bb6a55d646a3a3'/>
<id>urn:sha1:02e32376817529e960bb918417bb6a55d646a3a3</id>
<content type='text'>
Add a json parsing method that given an entity map in the format:
[
  {
     "id" : 1,
     "containerEntityId" : 2,
     "containerEntityInstance" : 3,
     "isList" : false,
     "isLinked" : false,
     "entities" : [
         {"id" : 1, "instance" : 2},
         {"id" : 1, "instance" : 3},
         {"id" : 1, "instance" : 4},
         {"id" : 1, "instance" : 5}
     ]
  }
]

is constructed into the entity map used by sensorhandler.  This is meant
as part of the transition from the entity map in YAML to JSON.

This is step 2.  Step 1 moved access to the object behind a method.
This adds JSON validation and parsing.  Step 3 will add a file path to
check and parse.  Step 4 will provide a call to parse that file if
present and use its data if non-empty.

Tested: The method added has not been tested beyond unit-test validation.
Signed-off-by: Patrick Venture &lt;venture@google.com&gt;
Change-Id: Ic29f022d3812fa9e3af775d542ad055629fd5a01
</content>
</entry>
<entry>
<title>message: Support prepending payloads</title>
<updated>2019-04-29T19:06:35+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2019-04-25T08:32:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=92476a84180ad4e60c698d21b6f14c368511ce6f'/>
<id>urn:sha1:92476a84180ad4e60c698d21b6f14c368511ce6f</id>
<content type='text'>
Needed solely so that we can support adding the necessary
bits for oem and group commands. We shouldn't be using this anywhere
else, which is why it is not generalized to non-payload types.

Change-Id: I6573f981fbe68cebb89abcdfb3de5de5d139e1e0
Signed-off-by: William A. Kennington III &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>message/pack: Allow packing payloads</title>
<updated>2019-04-29T19:06:35+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2019-04-24T21:45:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=e15e53eb5b3e8b279504710b5759fdfdd32bb128'/>
<id>urn:sha1:e15e53eb5b3e8b279504710b5759fdfdd32bb128</id>
<content type='text'>
Some IPMI handlers need the ability to support variable return types.
The easiest way to do that is to be able to return payloads and pack
them into the final payload.

Change-Id: I5098a1ab0998ada712096929eae40a3c88a6dea0
Signed-off-by: William A. Kennington III &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>message/pack: Support packing string_views</title>
<updated>2019-04-29T19:06:35+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2019-04-24T21:44:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=e2aec26caacdc65711a96ce3b6dbaa5ea526fc1f'/>
<id>urn:sha1:e2aec26caacdc65711a96ce3b6dbaa5ea526fc1f</id>
<content type='text'>
Now we don't need to make an intermediate copy of our data into an array
before packing it into a payload.

Change-Id: Iac79a79e0ae95835cb67d617a966a92ce8dcd5f8
Signed-off-by: William A. Kennington III &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>message/pack: Check for outstanding bits</title>
<updated>2019-04-29T19:06:35+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2019-04-24T21:44:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=906e0f802b56d26e7e0c65eba797fa8a596dee91'/>
<id>urn:sha1:906e0f802b56d26e7e0c65eba797fa8a596dee91</id>
<content type='text'>
Currently, if you pack a non-byte aligned member into a message and then
pack an array, it will do the wrong thing and treat the unaligned data
as being appended to the end of the message. Allowing for this behavior
is convoluted and probably not useful, so just return an error.

Change-Id: I6f200dbea96c41f49a110ba7536ccfd37115d277
Signed-off-by: William A. Kennington III &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>message/payload: Ignore unchecked unpack warning during unwind</title>
<updated>2019-04-29T19:06:35+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2019-04-24T08:53:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=f2fd17a41bf7e3afd4d69adf5f8ea5642bdfffcf'/>
<id>urn:sha1:f2fd17a41bf7e3afd4d69adf5f8ea5642bdfffcf</id>
<content type='text'>
If we are caught in an exception unwind we don't care that the
payload is not be fully checked. Otherwise, this encourages the pattern
of wrapping all handler code in try catch blocks that set trailingOk as
it is not required to read the entire payload when throwing an
exception.

Change-Id: I35149eedd33bd9fd41968e89d5a8614df7436872
Signed-off-by: William A. Kennington III &lt;wak@google.com&gt;
</content>
</entry>
</feed>
