Address type in entity-manager repo
Deng Tyler
tyler.sabdon at gmail.com
Tue Jul 23 11:50:32 AEST 2019
Hi James:
Thank for your kindly reply and that really helps. I have another
question about entity-manager. In entity-manager, it add an dbus interface
"xyz.openbmc_project.Inventory.Manager" to object
"/xyz/openbmc_project/inventory" in its service.
Why do that? I checked code and found there is no property or object will
be added under this interface. Meanwhile anther service
"xyz.openbmc_project.Inventory.Manager" has same interface and cause ipmid
get wrong service if receiving a fru ipmi command. Do you have any
suggestions? thanks. Regards
Tyler
James Feist <james.feist at linux.intel.com> 於 2019年7月18日 週四 上午7:01寫道:
> On 7/16/19 12:15 AM, Deng Tyler wrote:
> > Hi All:
> > I am investigated entity-manager with dbus-sensors. In
> > entity-manager, the schema define Address type is string as below
> > ---------------------------------------------------
> > "type": "object",
> > "properties": {
> > "Exposes": {
> > "type": "array",
> > "items": {
> > "type": "object",
> > "properties": {
> > "Address": {
> > "type": "string" <== here
> > },
> > "Name": {
> > "type": "string"
> > },
> > --------------------------------------------------------
> > In dbus-sensor application, cpusensor get CPU configuration from DBUS.
> > But the type is mismatch and cause cpusensor terminated.
> > *journalctl:*
> > cpusensor[296]: terminate called after throwing an instance of
> > 'std::invalid_argument'
> > cpusensor[296]: what(): Cannot translate type to unsigned int
> >
> > I found code in cpusensor to get "Address" and type shall be integer
> > from dbus as below
> > image.png
> > But in dbus the Address property is string
> > image.png
> >
> > Is this code error? or I miss something? thanks.
>
> I would suggest updating EntityManager, looks like you are using an old
> version, SkylakeCPU change to XeonCpu a long time ago.
>
> Thanks,
>
> James
>
>
>
> >
> > Tyler
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190723/58ea47f0/attachment.htm>
More information about the openbmc
mailing list