From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=none (no SPF record) smtp.mailfrom=linux.intel.com (client-ip=192.55.52.88; helo=mga01.intel.com; envelope-from=richard.marian.thomaiyar@linux.intel.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4BqtYC2cBmzDqML for ; Tue, 15 Sep 2020 03:25:33 +1000 (AEST) IronPort-SDR: oH18V+Tgkfw7Xe/HJmR5bjmwEFsH8dwGhSzNxIZl1eAgFEMJFCu6BF59rPFbPeTKMK1n7rWoRC bWx7ovYkHelg== X-IronPort-AV: E=McAfee;i="6000,8403,9744"; a="177186142" X-IronPort-AV: E=Sophos;i="5.76,426,1592895600"; d="scan'208,217";a="177186142" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2020 10:25:31 -0700 IronPort-SDR: Yk92CnJKLVoZ6/CPiNUnEFYKksPFrMKJZk+Zl/ghfBITebc/WAfhpXhts9isQO4Kbustmbq0u9 NmF7IULN++Kw== X-IronPort-AV: E=Sophos;i="5.76,426,1592895600"; d="scan'208,217";a="507219923" Received: from rthomaiy-mobl.gar.corp.intel.com (HELO [10.213.74.176]) ([10.213.74.176]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2020 10:25:28 -0700 Subject: Re: Read FRU of host through ipmi in Entity manager. To: Kumar Thangavel , "openbmc@lists.ozlabs.org" Cc: Jae Hyun Yoo , Vernon Mauery , "vijaykhemka@fb.com" , James Feist , "Velumani T-ERS, HCLTech" , Patrick Williams References: From: "Thomaiyar, Richard Marian" Message-ID: Date: Mon, 14 Sep 2020 22:55:24 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------08F15B9053498176C6A9E590" Content-Language: en-US X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2020 17:25:36 -0000 This is a multi-part message in MIME format. --------------08F15B9053498176C6A9E590 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Hi Kumar, Better to expose IPMI FRU of the host read via IPMB through FRU Interface (i.e. say xyz.openbmc_project.IPMB.FruDevice daemon, which can expose all the FRU's read through the same). In this way, current EntityManager probe will still work. (Note: We can add the support in FRUDevice if it is IPMB read of raw FRU data, so that conversion code in FRUDevice can still be used). Current plan (under discussion - Needs to finalize) to expose the PLDM FRU in separate daemon under interface (https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/xyz/openbmc_project/Inventory/Source/PLDM) James, Do you see any issue with this approach / comments ? Regards, Richard On 9/14/2020 10:25 PM, Kumar Thangavel wrote: > > Classification: *HCL Internal* > > Hi All, > >          We are working on the Platform which has multi host and the > host are FRUs.  The host and BMC communication is based on IPMB. We > have each host is connected in separate ipmb bus. > >          Existing Entity manager has the FRU read info from EEPROM > (I2C)in the form of bin file. >          We understand that entity manager does not support ipmb based > host fru. > >          So, we are proposing the design to support ipmb based FRU in > entity manager. >          From Entity manager, we will send the generic "read host fru" > command request to ipmbbrige to read the host FRU. > >          Then, store the host fru info in the bin file to process and > creating dbus objects in the entity manager. > >          Please let us know your comments on this. > > Thanks, > > Kumar. > > ::DISCLAIMER:: > ------------------------------------------------------------------------ > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be > intercepted, corrupted, lost, destroyed, arrive late or incomplete, or > may contain viruses in transmission. The e mail and its contents (with > or without referred errors) shall therefore not attach any liability > on the originator or HCL or its affiliates. Views or opinions, if any, > presented in this email are solely those of the author and may not > necessarily reflect the views or opinions of HCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, > modification, distribution and / or publication of this message > without the prior written consent of authorized representative of HCL > is strictly prohibited. If you have received this email in error > please delete it and notify the sender immediately. Before opening any > email and/or attachments, please check them for viruses and other defects. > ------------------------------------------------------------------------ --------------08F15B9053498176C6A9E590 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit

Hi Kumar,

Better to expose IPMI FRU of the host read via IPMB through FRU Interface (i.e. say xyz.openbmc_project.IPMB.FruDevice daemon, which can expose all the FRU's read through the same). In this way, current EntityManager probe will still work. (Note: We can add the support in FRUDevice if it is IPMB read of raw FRU data, so that conversion code in FRUDevice can still be used).

Current plan (under discussion - Needs to finalize) to expose the PLDM FRU in separate daemon under interface (https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/xyz/openbmc_project/Inventory/Source/PLDM)

James, Do you see any issue with this approach / comments ?

Regards,
Richard

On 9/14/2020 10:25 PM, Kumar Thangavel wrote:

Classification: HCL Internal

Hi All,

 

         We are working on the Platform which has multi host and the host are FRUs.  The host and BMC communication is based on IPMB. We have each host is connected in separate ipmb bus.

         Existing Entity manager has the FRU read info from EEPROM (I2C)in the form of bin file.
         We understand that entity manager does not support ipmb based host fru.

 

         So, we are proposing the design to support ipmb based FRU in entity manager.
         From Entity manager, we will send the generic "read host fru" command request to ipmbbrige to read the host FRU.

         Then, store the host fru info in the bin file to process and creating dbus objects in the entity manager.

 

         Please let us know your comments on this. 

 

Thanks,

Kumar.

 

 

 

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.

--------------08F15B9053498176C6A9E590--