<feed xmlns='http://www.w3.org/2005/Atom'>
<title>talos-hostboot/src/usr/isteps/pm, branch 07-25-2019</title>
<subtitle>Talos™ II hostboot sources</subtitle>
<id>https://git.raptorcs.com/git/talos-hostboot/atom?h=07-25-2019</id>
<link rel='self' href='https://git.raptorcs.com/git/talos-hostboot/atom?h=07-25-2019'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-hostboot/'/>
<updated>2020-01-22T15:45:00+00:00</updated>
<entry>
<title>Make RT_TARG id generation code common between IPL time and runtime</title>
<updated>2020-01-22T15:45:00+00:00</updated>
<author>
<name>Christian Geddes</name>
<email>crgeddes@us.ibm.com</email>
</author>
<published>2019-07-15T16:02:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-hostboot/commit/?id=f32aff51f83dcbcaa3857100c6e4e36ee7a8b84a'/>
<id>urn:sha1:f32aff51f83dcbcaa3857100c6e4e36ee7a8b84a</id>
<content type='text'>
For axone we are writing the OMI mmio bars into hdat so the hypervisor
know how to talk to the devices. IPL code needs to be able to lookup
the hbrt-style ids so we can use them to make hdat entries that the
hypervisor will be able to associate targets with. This commit also
move rt_targeting.H to the correct include directory and updates
everywhere that it is included.

Change-Id: I31deaa1a9c5a7523622a8b3b12ad459e2b2feed3
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/80419
Tested-by: Jenkins Server &lt;pfd-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP Build CI &lt;op-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP HW &lt;op-hw-jenkins+hostboot@us.ibm.com&gt;
Tested-by: FSP CI Jenkins &lt;fsp-CI-jenkins+hostboot@us.ibm.com&gt;
Reviewed-by: Daniel M Crowell &lt;dcrowell@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Final solution for Axone HCODE lid id</title>
<updated>2019-09-09T20:24:13+00:00</updated>
<author>
<name>Dan Crowell</name>
<email>dcrowell@us.ibm.com</email>
</author>
<published>2019-08-30T19:10:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-hostboot/commit/?id=cd820b6626a1af1e272e5d6457e233c1841db47f'/>
<id>urn:sha1:cd820b6626a1af1e272e5d6457e233c1841db47f</id>
<content type='text'>
Axone can just reuse the lid number that is assigned to Nimbus
since it is only used to map to a common PNOR partition.  There
is never a real lid load done with this value.

Change-Id: I7e1c2cc5f3f76e28b35dfd11e02a0af62c239c1b
RTC: 214257
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/83138
Tested-by: Jenkins Server &lt;pfd-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP Build CI &lt;op-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP HW &lt;op-hw-jenkins+hostboot@us.ibm.com&gt;
Tested-by: FSP CI Jenkins &lt;fsp-CI-jenkins+hostboot@us.ibm.com&gt;
Reviewed-by: Christian R Geddes &lt;crgeddes@us.ibm.com&gt;
Reviewed-by: Ilya Smirnov &lt;ismirno@us.ibm.com&gt;
Reviewed-by: Daniel M Crowell &lt;dcrowell@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Add temp workaround to force Axone to use Nimbus's hcode lid</title>
<updated>2019-08-07T16:32:00+00:00</updated>
<author>
<name>Christian Geddes</name>
<email>crgeddes@us.ibm.com</email>
</author>
<published>2019-08-06T22:16:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-hostboot/commit/?id=311f9e01703adecdd819f08ea61cde6c729abd25'/>
<id>urn:sha1:311f9e01703adecdd819f08ea61cde6c729abd25</id>
<content type='text'>
Until we get this sorted out for Axone the Nimbus image will work.

Change-Id: I539ddcba5954ea6cc4ed7b3768e52aa7bb8e610a
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/81819
Tested-by: Jenkins Server &lt;pfd-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP Build CI &lt;op-jenkins+hostboot@us.ibm.com&gt;
Tested-by: FSP CI Jenkins &lt;fsp-CI-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP HW &lt;op-hw-jenkins+hostboot@us.ibm.com&gt;
Reviewed-by: Daniel M Crowell &lt;dcrowell@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Unit test for the firmware request sendAttributes</title>
<updated>2019-07-02T18:44:57+00:00</updated>
<author>
<name>Roland Veloz</name>
<email>rveloz@us.ibm.com</email>
</author>
<published>2019-06-13T23:37:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-hostboot/commit/?id=d2d561f722aa8f85f60924718263a4b17fa840ba'/>
<id>urn:sha1:d2d561f722aa8f85f60924718263a4b17fa840ba</id>
<content type='text'>
Added a unit test for the firmware request sendAttributes.  The unit
test exercises and verifies the correctness of the sendAttribute
firmware request method.

Did some massive cleanup of the testing framework/harness.  It was
becoming unwieldy and cumbersome to update.  I create methods for the
individual firmware request test instead of having the test reside in
over bloated method.

Added a section, in the README file, on how to test new interfaces
that are added for firmware request lineup.

Change-Id: I0ff7c0e48211b12d81be1f179ad3ee08e4d254af
RTC: 208343
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/78934
Tested-by: Jenkins Server &lt;pfd-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP Build CI &lt;op-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP HW &lt;op-hw-jenkins+hostboot@us.ibm.com&gt;
Tested-by: FSP CI Jenkins &lt;fsp-CI-jenkins+hostboot@us.ibm.com&gt;
Reviewed-by: Glenn Miles &lt;milesg@ibm.com&gt;
Reviewed-by: Christian R. Geddes &lt;crgeddes@us.ibm.com&gt;
Reviewed-by: Daniel M. Crowell &lt;dcrowell@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Handle NVDIMM encryption errors</title>
<updated>2019-06-18T22:13:24+00:00</updated>
<author>
<name>Corey Swenson</name>
<email>cswenson@us.ibm.com</email>
</author>
<published>2019-06-12T16:59:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-hostboot/commit/?id=7508722e0908dae7096a98d502dbef9917f5857a'/>
<id>urn:sha1:7508722e0908dae7096a98d502dbef9917f5857a</id>
<content type='text'>
 Update ATTR_NVDIMM_ARMED and ATTR_NV_STATUS_FLAG
 Update notifyNvdimmProtectionChange()
 Set encryption error and check before arm/disarm

Change-Id: I1edf738af3460684ee93b02f06ff417c3e72d4e3
RTC:210689
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/78828
Tested-by: Jenkins Server &lt;pfd-jenkins+hostboot@us.ibm.com&gt;
Reviewed-by: Daniel M. Crowell &lt;dcrowell@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Add SMF mode flag to HOMER for use by OCC</title>
<updated>2019-04-30T18:27:01+00:00</updated>
<author>
<name>Chris Cain</name>
<email>cjcain@us.ibm.com</email>
</author>
<published>2019-04-22T20:22:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-hostboot/commit/?id=cbf60d385958cca0ad6c35926284cf35e62da65b'/>
<id>urn:sha1:cbf60d385958cca0ad6c35926284cf35e62da65b</id>
<content type='text'>
Change-Id: I03daab724811f09aa83c4e0d7929f0a013a2b731
RTC: 164116
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/76398
Tested-by: Jenkins Server &lt;pfd-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP Build CI &lt;op-jenkins+hostboot@us.ibm.com&gt;
Reviewed-by: Christopher J. Cain &lt;cjcain@us.ibm.com&gt;
Tested-by: FSP CI Jenkins &lt;fsp-CI-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP HW &lt;op-hw-jenkins+hostboot@us.ibm.com&gt;
Reviewed-by: Martha Broyles &lt;mbroyles@us.ibm.com&gt;
Reviewed-by: Sheldon Bailey &lt;baileysh@us.ibm.com&gt;
Reviewed-by: Daniel M. Crowell &lt;dcrowell@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>SMF: Logic For Creating Non-Secure HOMER Memory Space</title>
<updated>2019-04-12T17:12:11+00:00</updated>
<author>
<name>Ilya Smirnov</name>
<email>ismirno@us.ibm.com</email>
</author>
<published>2018-12-11T15:47:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-hostboot/commit/?id=a9addc3db4f8940ca38fb63c99fcab26126c88f0'/>
<id>urn:sha1:a9addc3db4f8940ca38fb63c99fcab26126c88f0</id>
<content type='text'>
For SMF to be enabled, HOMER requires a small amount of
non-SMF (unsecure) memory where the "jump to Ultravisor"
instruction can be put (to transition to UV mode). This
commit sets up a region of non-secure memory space for
that purpose.

Change-Id: Ib91ec69f49a4e174e65f3c2aad337a68eaa0803b
RTC: 205986
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/70699
Reviewed-by: Prem Shanker Jha &lt;premjha2@in.ibm.com&gt;
Tested-by: Jenkins Server &lt;pfd-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP Build CI &lt;op-jenkins+hostboot@us.ibm.com&gt;
Tested-by: FSP CI Jenkins &lt;fsp-CI-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP HW &lt;op-hw-jenkins+hostboot@us.ibm.com&gt;
Reviewed-by: Nicholas E. Bofferding &lt;bofferdn@us.ibm.com&gt;
Reviewed-by: Daniel M. Crowell &lt;dcrowell@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Get ring override failing</title>
<updated>2019-04-03T14:16:05+00:00</updated>
<author>
<name>Chen Du</name>
<email>duchen@us.ibm.com</email>
</author>
<published>2019-03-25T20:39:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-hostboot/commit/?id=5da79e14c3166022a34c993246a439e9a6df0836'/>
<id>urn:sha1:5da79e14c3166022a34c993246a439e9a6df0836</id>
<content type='text'>
Get ring override is an optional code path but it halts the boot
process when it returns a failure. Optional code path should still
continue the boot process as normal even on a failure. Error
logs should still continue as normal.

Change-Id: I869e7bcaee5993b601af1e63273f597e1310fbfd
CQ: SW455865
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/74978
Reviewed-by: Ilya Smirnov &lt;ismirno@us.ibm.com&gt;
Tested-by: Jenkins Server &lt;pfd-jenkins+hostboot@us.ibm.com&gt;
Tested-by: FSP CI Jenkins &lt;fsp-CI-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP Build CI &lt;op-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP HW &lt;op-hw-jenkins+hostboot@us.ibm.com&gt;
Reviewed-by: Michael Baiocchi &lt;mbaiocch@us.ibm.com&gt;
Reviewed-by: Nicholas E. Bofferding &lt;bofferdn@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>HB:Cme fir attribute reset fix</title>
<updated>2019-02-23T01:46:54+00:00</updated>
<author>
<name>Prasad Bg Ranganath</name>
<email>prasadbgr@in.ibm.com</email>
</author>
<published>2019-02-19T17:14:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-hostboot/commit/?id=2a2071cb681555449f12769c8c3e3d7e03a37d8e'/>
<id>urn:sha1:2a2071cb681555449f12769c8c3e3d7e03a37d8e</id>
<content type='text'>
CQ:SW455727
Change-Id: I854779403ab138f193ad7fc3ff188b4e7d48388e
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/72122
Tested-by: Jenkins Server &lt;pfd-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP Build CI &lt;op-jenkins+hostboot@us.ibm.com&gt;
Tested-by: FSP CI Jenkins &lt;fsp-CI-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP HW &lt;op-hw-jenkins+hostboot@us.ibm.com&gt;
Reviewed-by: Prem Shanker Jha &lt;premjha2@in.ibm.com&gt;
Reviewed-by: Daniel M. Crowell &lt;dcrowell@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Disable NVDIMM Trigger Before Draminit and Deassert DDR_RESETn During MPIPL</title>
<updated>2019-02-12T16:50:42+00:00</updated>
<author>
<name>Tsung Yeung</name>
<email>tyeung@us.ibm.com</email>
</author>
<published>2018-12-20T16:39:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-hostboot/commit/?id=b2027cd8b704587be6ce4dd14327e6730f9d519b'/>
<id>urn:sha1:b2027cd8b704587be6ce4dd14327e6730f9d519b</id>
<content type='text'>
- Per the JEDEC spec, DDR_RESETn is masked from the DRAM when the NVDIMM
is armed. This could cause the training to fail if the trigger is not
disabled before training. Two scenarios where this can happen are warm
reboot and cold boot before the backup power module can deplete the
charge

- Deassert DDR_RESETn in MPIPL before triggering the restore.
- Fix the config flag to enable NVDIMM code

Change-Id: I9d25c2f653fc54d379f0dbab49218f5b59a407a0
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/70035
Reviewed-by: Matt Derksen &lt;mderkse1@us.ibm.com&gt;
Tested-by: Jenkins Server &lt;pfd-jenkins+hostboot@us.ibm.com&gt;
Tested-by: FSP CI Jenkins &lt;fsp-CI-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP Build CI &lt;op-jenkins+hostboot@us.ibm.com&gt;
Tested-by: Jenkins OP HW &lt;op-hw-jenkins+hostboot@us.ibm.com&gt;
Reviewed-by: Daniel M. Crowell &lt;dcrowell@us.ibm.com&gt;
</content>
</entry>
</feed>
