<html><body><p>The question is "Which eeprom maps to FRU: 0x03".<br><br>Unless this is part of some MRW and things like that, there needs to be some way to communicate the eeprom info to HB.<br><br>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>----------------------------------------------------------------------------------<br><br><img width="16" height="16" src="cid:1__=EABBF50FDFBCE0098f9e8a93df938690918cEAB@" border="0" alt="Inactive hide details for Yi TZ Li---21/04/2016 01:53:20 pm---For question #1, is the FRU with ID "0x3" for motherboard (Plana"><font color="#424282">Yi TZ Li---21/04/2016 01:53:20 pm---For question #1, is the FRU with ID "0x3" for motherboard (Planar) VPD (Area CHASSIS_3)? It is mana</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Yi TZ Li/China/IBM</font><br><font size="2" color="#5F5F5F">To: </font><font size="2">Vishwanatha Subbanna/India/IBM@IBMIN</font><br><font size="2" color="#5F5F5F">Cc: </font><font size="2">anoo@us.ibm.com, OpenBMC Members, openbmc@lists.ozlabs.org</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">21/04/2016 01:53 pm</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: FRU VPD - MAC and UUID</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font face="Arial">For question #1, is the FRU with ID "0x3" for motherboard (Planar) VPD (Area CHASSIS_3)? It is managed by Hostboot.</font><br><font face="Arial"> </font><br><img src="cid:2__=EABBF50FDFBCE0098f9e8a93df938690918cEAB@" width="425" height="416"><br><font face="Arial"> </font><br><font face="Arial">Thanks,</font><br><font face="Arial"> </font><br><font face="Arial">Yi Li (Adam)<br>OpenBMC Developer<br>Office: 86-21-60928951<br>Mobile: 13524695440<br>Email: shliyi@cn.ibm.com </font><br><font face="Arial"> </font><br><font face="Arial"> </font><br><font face="Arial">----- 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> </font><font face="Arial"><br>Answering #2:</font><font face="Arial"><br></font><font face="Arial"><br>IPMI FRU format has 2 more sections namely, INTERNAL and MULTI although we have not been using this in our code.</font><font face="Arial"><br><br></font><img src="cid:3__=EABBF50FDFBCE0098f9e8a93df938690918cEAB@" width="242" height="328"><font face="Arial"><br></font><font face="Arial"><br>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><font face="Arial"><br></font><font face="Arial"><br>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><font face="Arial"><br></font><font face="Arial"><br>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><font face="Arial"><br></font><font face="Arial"><br>Also, if this VPD is readable by HB, I am guessing we would need to tell HB on this format.</font><font face="Arial"><br></font><font face="Arial"><br>We do not want to append MAC to product area since it overlaps with multi area and will result in corruption..</font><font face="Arial"><br></font><font face="Arial"><br>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><font face="Arial"><br></font><font face="Arial"><br>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><font face="Arial"><br><br></font><font color="#424282" face="Arial">"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><font face="Arial"><br></font><font color="#5F5F5F" face="Arial"><br>From: </font><font face="Arial">"Adriana Kobylak" <anoo@us.ibm.com></font><font color="#5F5F5F" face="Arial"><br>To: </font><font face="Arial">OpenBMC <openbmc@lists.ozlabs.org></font><font color="#5F5F5F" face="Arial"><br>Date: </font><font face="Arial">21/04/2016 02:22 am</font><font color="#5F5F5F" face="Arial"><br>Subject: </font><font face="Arial">FRU VPD - MAC and UUID</font><font color="#5F5F5F" face="Arial"><br>Sent by: </font><font face="Arial">"openbmc" <openbmc-bounces+vishwanath=in.ibm.com@lists.ozlabs.org></font><font face="Arial"> </font><hr width="100%" size="2" align="left"><font face="Arial"><br><br></font><font face="Arial"><br>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><font face="Arial"><br></font><font face="Arial"><br>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><font face="Arial"><br></font><font face="Arial"><br>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 size="4">_______________________________________________<br>openbmc mailing list<br>openbmc@lists.ozlabs.org</font></tt><tt><u><font size="4" color="#0000FF"><br></font></u></tt><a href="https://lists.ozlabs.org/listinfo/openbmc" target="_blank"><tt><u><font size="4" color="#0000FF">https://lists.ozlabs.org/listinfo/openbmc</font></u></tt></a><font face="Arial"><br> </font><br><br><BR>
</body></html>