* IPMI - get device ID
@ 2017-10-26 16:59 Dave Cobbley
2017-10-27 11:52 ` tomjose
0 siblings, 1 reply; 3+ messages in thread
From: Dave Cobbley @ 2017-10-26 16:59 UTC (permalink / raw)
To: OpenBMC Maillist
I noticed a bit of the get-device-id information in
phosphor-ipmi-host/apphandler is hard coded.
Much of this info should be determined at compile time - would the
inventory manager be the appropriate place that all platforms under the
OpenBMC umbrella would like to store this information?
• Device ID
• Device Revision
• IANA
• Product ID
• Auxiliary
Thanks,
-Dave Cobbley
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: IPMI - get device ID
2017-10-26 16:59 IPMI - get device ID Dave Cobbley
@ 2017-10-27 11:52 ` tomjose
2017-10-27 16:54 ` Dave Cobbley
0 siblings, 1 reply; 3+ messages in thread
From: tomjose @ 2017-10-27 11:52 UTC (permalink / raw)
To: Dave Cobbley, OpenBMC Maillist; +Cc: chinari, Brad Bishop
Hello Dave,
https://github.com/openbmc/openbmc/issues/495
We had this issue open to fix the hardcoded Product ID, Manufacturing
ID..etc. Since these fields are IPMI specific, we do not plan to create
D-Bus properties for that.
The solution we have in mind is to have these values specified in a yaml
in the openbmc machine specific layer. This gives the advantage that we
have these values as machine specific and can be taken care at compile
time. We would add code in phosphor-host-ipmid, to generate code out of
this yaml file and serve the Get Device ID command.
Dinesh is working on this and he would share the code on gerrit to
solicit your feedback. Let me know your thoughts.
Regards,
Tom
On Thursday 26 October 2017 10:29 PM, Dave Cobbley wrote:
> I noticed a bit of the get-device-id information in
> phosphor-ipmi-host/apphandler is hard coded.
>
> Much of this info should be determined at compile time - would the
> inventory manager be the appropriate place that all platforms under
> the OpenBMC umbrella would like to store this information?
>
> • Device ID
> • Device Revision
> • IANA
> • Product ID
> • Auxiliary
>
> Thanks,
>
> -Dave Cobbley
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: IPMI - get device ID
2017-10-27 11:52 ` tomjose
@ 2017-10-27 16:54 ` Dave Cobbley
0 siblings, 0 replies; 3+ messages in thread
From: Dave Cobbley @ 2017-10-27 16:54 UTC (permalink / raw)
To: tomjose, OpenBMC Maillist; +Cc: chinari, Brad Bishop
Sounds great!
Looking forward to seeing the pull request in gerrit.
Thanks,
-Dave
On 10/27/2017 04:52 AM, tomjose wrote:
> Hello Dave,
>
> https://github.com/openbmc/openbmc/issues/495
>
> We had this issue open to fix the hardcoded Product ID, Manufacturing
> ID..etc. Since these fields are IPMI specific, we do not plan to
> create D-Bus properties for that.
>
> The solution we have in mind is to have these values specified in a
> yaml in the openbmc machine specific layer. This gives the advantage
> that we have these values as machine specific and can be taken care at
> compile time. We would add code in phosphor-host-ipmid, to generate
> code out of this yaml file and serve the Get Device ID command.
>
> Dinesh is working on this and he would share the code on gerrit to
> solicit your feedback. Let me know your thoughts.
>
> Regards,
> Tom
>
> On Thursday 26 October 2017 10:29 PM, Dave Cobbley wrote:
>> I noticed a bit of the get-device-id information in
>> phosphor-ipmi-host/apphandler is hard coded.
>>
>> Much of this info should be determined at compile time - would the
>> inventory manager be the appropriate place that all platforms under
>> the OpenBMC umbrella would like to store this information?
>>
>> • Device ID
>> • Device Revision
>> • IANA
>> • Product ID
>> • Auxiliary
>>
>> Thanks,
>>
>> -Dave Cobbley
>>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-10-27 16:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-10-26 16:59 IPMI - get device ID Dave Cobbley
2017-10-27 11:52 ` tomjose
2017-10-27 16:54 ` Dave Cobbley
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.