<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div dir="ltr" >For question #1, is the FRU with ID "0x3" for motherboard (Planar) VPD (Area CHASSIS_3)? It is managed by Hostboot.</div>
<div dir="ltr" > </div>
<div dir="ltr" ><img alt="" src="cid:14612172046951" height="416" width="425" ></div>
<div dir="ltr" > </div>
<div dir="ltr" >Thanks,</div>
<div dir="ltr" > </div>
<div dir="ltr" >Yi Li (Adam)<br>OpenBMC Developer<br>Office: 86-21-60928951<br>Mobile: 13524695440<br>Email: shliyi@cn.ibm.com
<div> </div>
<div> </div>
<blockquote data-history-content-modified="1" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" >----- Original message -----<br>From: Vishwanatha Subbanna/India/IBM<br>To: "Adriana Kobylak" <anoo@us.ibm.com><br>Cc: OpenBMC <openbmc@lists.ozlabs.org>, OpenBMC Members<br>Subject: Re: FRU VPD - MAC and UUID<br>Date: Thu, Apr 21, 2016 3:19 PM<br> <br><font size="2" >Answering #2:</font><br><br><font size="2" >IPMI FRU format has 2 more sections namely, INTERNAL and MULTI although we have not been using this in our code.</font><br><br><img src="cid:14612172046950" height="328" width="242" ><br><br><font size="2" >I would vote for appending the MAC as part of product or board and then updating the offsets+size accordingly in the area specific header that would now tell the size including the MAC data. What this also means is that common header meta data would change.</font><br><br><font size="2" >Another approach would be looking at what areas have *not* been populated for some FRU that is on the board and then squeeze this new one into that un-populated area and populate that area specific header and common header.</font><br><br><font size="2" >All the FRU's may not necessarily have all the areas populated. What I have seen most is just 2 areas ( Board, Product) / ( Chassis, Board) / (Chassis, Product) so we can use whatever that is not populated and put this new one there.</font><br><br><font size="2" >Also, if this VPD is readable by HB, I am guessing we would need to tell HB on this format.</font><br><br><font size="2" >We do not want to append MAC to product area since it overlaps with multi area and will result in corruption..</font><br><br><font size="2" >Last resort, we can either use INTERNAL -or- MULTI but using INTERNAL area looks a more cleaner -but- that needs a code change since we have not been supporting it. So I would nto vote for this....</font><br><br><font size="2" >Thanks<br><br>-------------------------------------------------------------------------------------<br>Thanks and Regards,<br>Vishwanath.<br>Advisory Software Engineer,<br>Power Firmware Development,<br>Systems &Technology Lab,<br>MG2-6F-255 , Manyata Embassy Business Park,<br>Bangalore , KA , 560045<br>Ph: +91-80-46678255<br>E-mail: vishwanath@in.ibm.com<br>----------------------------------------------------------------------------------</font><br><br><img alt="Inactive hide details for "Adriana Kobylak" ---21/04/2016 02:22:18 am---Mfg will be storing the MAC address and UUID of the Bar" src="/icons/graycol.gif" height="16" border="0" width="16" ><font color="#424282" size="2" >"Adriana Kobylak" ---21/04/2016 02:22:18 am---Mfg will be storing the MAC address and UUID of the Barreleye system in the FRU VPD so that we can</font><br><br><font color="#5F5F5F" size="2" >From: </font><font size="2" >"Adriana Kobylak" <anoo@us.ibm.com></font><br><font color="#5F5F5F" size="2" >To: </font><font size="2" >OpenBMC <openbmc@lists.ozlabs.org></font><br><font color="#5F5F5F" size="2" >Date: </font><font size="2" >21/04/2016 02:22 am</font><br><font color="#5F5F5F" size="2" >Subject: </font><font size="2" >FRU VPD - MAC and UUID</font><br><font color="#5F5F5F" size="2" >Sent by: </font><font size="2" >"openbmc" <openbmc-bounces+vishwanath=in.ibm.com@lists.ozlabs.org></font>
<hr style="color:#8091A5; " align="left" size="2" width="100%" ><br><br><br><font size="2" >Mfg will be storing the MAC address and UUID of the Barreleye system in the FRU VPD so that we can persist it better. Couple questions:</font><br><br><font size="2" >1. The UUID is planned to be stored in the motherboard VPD. Anybody has the info on which eeprom is the motherboard VPD? Seems the only chips under /sys/bus/i2c/devices/ with vpd are the ones from the i/o, expander, and hdd cards (0-0050, 6-0055, 6-0051).</font><br><br><font size="2" >2. The MAC is planned to be stored at the end of the i/o board VPD. All of the FRU VPD follow the format of header->chassis_info->board_info->product_info. The header contains the offset to the *_info areas. Without an offset to the MAC (which would be stored after the product_info area), we could just read passed the product_area and if it's not 0s, assume it's the MAC. Would it be better to ask Mfg to add the offset to the MAC to header although this breaks the IPMI formatting, or get the MAC into one of the custom fields inside the product info area. Thoughts?</font><tt><font face="" size="3" >_______________________________________________<br>openbmc mailing list<br>openbmc@lists.ozlabs.org</font></tt><br><tt><font face="" size="3" ><a href="https://lists.ozlabs.org/listinfo/openbmc" target="_blank" >https://lists.ozlabs.org/listinfo/openbmc</a></font></tt><br> </blockquote></div></div>
<BR>