archive mirror
 help / color / mirror / Atom feed
From: Artem Senichev <>
To: "Garrett, Mike (HPE Server Firmware)" <>
Cc: OpenBMC Maillist <>,
	"Pedrana, Nick" <>
Subject: Re: Leveraging and extending smbios-mdr
Date: Thu, 29 Jul 2021 10:49:04 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <DF4PR8401MB0634147E668CC84648DC883A8FE99@DF4PR8401MB0634.NAMPRD84.PROD.OUTLOOK.COM>

On Tue, Jul 27, 2021 at 03:47:04PM +0000, Garrett, Mike (HPE Server Firmware) wrote:
> Hello Artem and all,
> We are integrating smbios-mdr into our build.  Our SMBIOS info is downloaded and built as a file in the filesystem using proprietary means (our CHIF - channel interface).  Our hope is that we can simply point the smbios-mdr service at it and light up new information about the platform in dbus, Redfish, and the GUI.
> However, I can't find much in the way of documentation about smbios-mdr.

If we are talking about the MDR2 project (,
there is no documentation, but I don't think we really need it.
It is just a SMBIOS dump parser for some table types (CPU, DIMM).
The table format is fully documented in the SMBIOS specification:

> I'm especially interested in how to extend the functionality past just CPUs and DIMMs into things like OEM records supplied by the BIOS.

What about phosphor-inventory-manager?

> Seems like the possibilities are:
> 1. Smbios-mdr has a generic dbus API and we write an independent service to query it for this info and publish to dbus
> 2. We create a generic extension mechanism for smbios-mdr for vendors to add OEM support and push to dbus directly from smbios-mdr (like w/ CPUs/DIMMs)
> 3. We fork smbios-mdr and extend it (not preferred).
> I'd like to hear how best to leverage this recipe.

Artem Senichev
Software Engineer, YADRO.

  reply	other threads:[~2021-07-29  7:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 15:47 Leveraging and extending smbios-mdr Garrett, Mike (HPE Server Firmware)
2021-07-29  7:49 ` Artem Senichev [this message]
2021-08-17 21:29   ` Garrett, Mike (HPE Server Firmware)
2021-08-18  6:33     ` Andrei Kartashev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).