Firmware version under IPMB sensors

[Ambrozewicz, Adrian]

It's not clear for me how do you plan to expose this information.
Mentioned dbus-sensors service is mainly focused on exposing Sensor data 
compliant with following interface: 
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Sensor/Value.interface.yaml

Having FW revision exposed through stack 'dbus-sensors-like' is OK, as 
you could utilize following stack :
- EntityManager for configuration of monitored components (bus, address etc)
- higher level service dynamically spawning DBus objects with version 
information
- expose information in standardized way (probably 
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Software/Version.interface.yaml)

Regards,
Adrian

W dniu 10/5/2020 o 19:53, Jayashree D pisze:
> Classification: HCL Internal
> 
> Hi Ed Tanous,
> 
> We are using Twinlake for IPMB and plan to read all the firmware versions ( CPLD, ME, Bridge IC, VR) using OEM commands. Also display the firmware versions using dbus objects.
> 
> Regards,
> Jayashree
> 
> 
> 
> -----Original Message-----
> From: Ed Tanous <ed at tanous.net>
> Sent: Monday, October 5, 2020 7:55 PM
> To: Jayashree D <jayashree-d at hcl.com>
> Cc: openbmc at lists.ozlabs.org; Velumani T-ERS,HCLTech <velumanit at hcl.com>
> Subject: Re: Firmware version under IPMB sensors
> 
> [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.]
> 
> On Sun, Oct 4, 2020 at 11:43 PM Jayashree D <jayashree-d at hcl.com> wrote:
>>
>> Classification: HCL Internal
>>
>> Hi Team,
>>
>>
>>
>> In my system, host is connected to IPMB and host related information is retrieved using IPMB bus.
>> I plan to add firmware versions in the dbus-sensors. Adding this as another entity as like ipmbsensor.
>> This will help in having all transaction in IPMB sensor.
> 
> Sounds reasonable.  Do you intend on using the get device id command to determine the version number?  What piece of hardware are you connecting to?
> ::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.
> ________________________________
>