<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p>Thanks, this is exactly what we needed, especially the part about
what uses which parts of HOMER.</p>
<p>Just FYI, it seems that the structure I am parsing (created by
<a class="moz-txt-link-freetext" href="https://git.raptorcs.com/git/talos-hostboot/log/?h=07-25-2019">https://git.raptorcs.com/git/talos-hostboot/log/?h=07-25-2019</a>) is
slightly newer, e.g. SR and STOP API versions in CPMR header are
both 2 and thread launcher size is 1K, which I guess is a
consequence of different version. Current upstream master uses SR
version 3 and has reverted commit with thread launcher size and
accompanying changes.<br>
</p>
<div class="moz-cite-prefix">On 19.07.2021 20:02, Daniel M Crowell
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:OF35B7DDA8.49FB3AF8-ON86258717.0063117D-86258717.00631BDE@ibm.com">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<p><font size="2" face="sans-serif">Check out </font><a
href="https://github.com/open-power/docs/blob/master/occ/p9_pmcd_homer.pdf"
target="_blank" moz-do-not-send="true"><font size="2"
face="sans-serif" color="#0000FF"><u>https://github.com/open-power/docs/blob/master/occ/p9_pmcd_homer.pdf</u></font></a><font
size="3" face="serif"> </font><font size="2" face="sans-serif"> to
see if it helps.</font><br>
<font size="2" face="sans-serif"><br>
--<br>
Dan Crowell<br>
Senior Software Engineer - Power Systems Enablement Firmware<br>
IBM Rochester: t/l 553-2987<br>
<a class="moz-txt-link-abbreviated" href="mailto:dcrowell@us.ibm.com">dcrowell@us.ibm.com</a></font><br>
<br>
<img src="cid:part2.98F2F864.10A6D645@3mdeb.com" alt="Inactive
hide details for Krystian Hebel ---07/15/2021 01:18:21
PM---Hello, Our work on coreboot port for Talos II got to the
p" class="" width="16" height="16" border="0"><font size="2"
face="sans-serif" color="#424282">Krystian Hebel ---07/15/2021
01:18:21 PM---Hello, Our work on coreboot port for Talos II
got to the point where we have to</font><br>
<br>
<font size="1" face="sans-serif" color="#5F5F5F">From: </font><font
size="1" face="sans-serif">Krystian Hebel
<a class="moz-txt-link-rfc2396E" href="mailto:krystian.hebel@3mdeb.com"><krystian.hebel@3mdeb.com></a></font><br>
<font size="1" face="sans-serif" color="#5F5F5F">To: </font><font
size="1" face="sans-serif"><a class="moz-txt-link-abbreviated" href="mailto:openpower-firmware@lists.ozlabs.org">openpower-firmware@lists.ozlabs.org</a></font><br>
<font size="1" face="sans-serif" color="#5F5F5F">Cc: </font><font
size="1" face="sans-serif"><a class="moz-txt-link-abbreviated" href="mailto:firmware@3mdeb.com">firmware@3mdeb.com</a></font><br>
<font size="1" face="sans-serif" color="#5F5F5F">Date: </font><font
size="1" face="sans-serif">07/15/2021 01:18 PM</font><br>
<font size="1" face="sans-serif" color="#5F5F5F">Subject: </font><font
size="1" face="sans-serif">[EXTERNAL] [OpenPower-Firmware]
HOMER structure</font><br>
<font size="1" face="sans-serif" color="#5F5F5F">Sent by: </font><font
size="1" face="sans-serif">"OpenPower-Firmware"
<a class="moz-txt-link-rfc2396E" href="mailto:openpower-firmware-bounces+dcrowell=us.ibm.com@lists.ozlabs.org"><openpower-firmware-bounces+dcrowell=us.ibm.com@lists.ozlabs.org></a></font><br>
</p>
<hr style="color:#8091A5; " width="100%" size="2"
noshade="noshade" align="left"><br>
<br>
<br>
<tt><font size="2">Hello,<br>
<br>
Our work on coreboot port for Talos II got to the point where
we have to <br>
start<br>
cores other than the one booted by SBE. As part of the
procedure of bringing<br>
them up we have to prepare HOMER structure (istep 15.1 in
Hostboot, IPL<br>
documentation [1] swaps 15.1 with 15.2). So far we have been
trying to parse<br>
Hostboot's code that builds it, but that seems to take
eternity.<br>
<br>
Is there any documentation that would explain the layout
(preferably both<br>
structural and functional), better than the one that can be
found in IPL <br>
just<br>
after 24.1? This would make our job much easier. Otherwise we
are forced to<br>
keep on going through the code, not only Hostboot's, but
probably also HCODE<br>
and/or OCC to understand what happens there.<br>
<br>
[1] <br>
<a
href="https://raw.githubusercontent.com/open-power/docs/master/hostboot/P9_Boot_Flow_OpenPOWER.pdf"
moz-do-not-send="true">https://raw.githubusercontent.com/open-power/docs/master/hostboot/P9_Boot_Flow_OpenPOWER.pdf</a>
<br>
<br>
-- <br>
Krystian Hebel<br>
Firmware Engineer<br>
<a href="https://3mdeb.com" moz-do-not-send="true">https://3mdeb.com</a>
| @3mdeb_com<br>
<br>
_______________________________________________<br>
OpenPower-Firmware mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:OpenPower-Firmware@lists.ozlabs.org">OpenPower-Firmware@lists.ozlabs.org</a><br>
<a href="https://lists.ozlabs.org/listinfo/openpower-firmware"
moz-do-not-send="true">https://lists.ozlabs.org/listinfo/openpower-firmware</a>
</font></tt><br>
</blockquote>
<pre class="moz-signature" cols="72">--
Krystian Hebel
Firmware Engineer
<a class="moz-txt-link-freetext" href="https://3mdeb.com">https://3mdeb.com</a> | @3mdeb_com</pre>
</body>
</html>