From: "Garrett, Mike (HPE Server Firmware)" <mike.garrett@hpe.com>
To: Andrei Kartashev <a.kartashev@yadro.com>,
Thang Nguyen <thang@amperemail.onmicrosoft.com>,
openbmc <openbmc@lists.ozlabs.org>
Subject: RE: Read smbios2 file failed
Date: Wed, 15 Sep 2021 13:18:57 +0000 [thread overview]
Message-ID: <DF4PR8401MB06341BDD6521896375C0CF498FDB9@DF4PR8401MB0634.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <4bda1bb5f09395003c95c645518f34828105b160.camel@yadro.com>
We recently did the same thing and got it working. All you have to do is take the RAW smbios records blob in binary form (delivered as noted below in whatever way you choose) and prepend a specific header: https://github.com/openbmc/smbios-mdr/blob/33c948a473bd273fea0cff82d4c99b70b7784be6/include/smbios_mdrv2.hpp#L114
It is a little bit fragile as it introduces a dependency on the file download logic to write a non-standard header defined in another service that could potentially change.
Mike
> -----Original Message-----
> From: openbmc <openbmc-
> bounces+mike.garrett=hpe.com@lists.ozlabs.org> On Behalf Of Andrei
> Kartashev
> Sent: Wednesday, September 15, 2021 3:17 AM
> To: Thang Nguyen <thang@amperemail.onmicrosoft.com>; openbmc
> <openbmc@lists.ozlabs.org>
> Subject: Re: Read smbios2 file failed
>
> I don't know what is format of "dmidecode --dump-bin", but if it just raw
> dump of smbios then you only need to add mdr header.
>
> See answer for the same question here:
> INVALID URI REMOVED
> 021-July/026882.html__;!!NpxR!2w0FkPs2KyaB6XOvB8et52bWKqAMLImmL-
> iUk9A_zZbJ8WLhMeXdvRAp-pcxt8Q$
>
> On Wed, 2021-09-15 at 12:41 +0700, Thang Nguyen wrote:
> > Hi Andrei,
> >
> > I see output of "dmidecode --dump-bin" follows SMBIOS specification.
> > As
> > the data for smbios-mdr does not follow this, do you know about the
> > document or any information I can reference to prepare data to send to
> > BMC??
> >
> >
> > Best Regards,
> >
> > Thang Q. Nguyen
> >
> > On 14/09/2021 15:51, Andrei Kartashev wrote:
> > > No, it is not same as "dmidecode --dump-bin".
> > >
> > > On Tue, 2021-09-14 at 13:46 +0700, Thang Nguyen wrote:
> > > > On 13/09/2021 23:56, Andrei Kartashev wrote:
> > > > > You need to somehow deliver smbios data image to BMC. This
> > > > > means, your BIOS should implementat some logic to transfer this
> > > > > data.
> > > > > For BMC side see example here:
> > > > > https://github.com/openbmc/intel-ipmi-
> oem/blob/master/src/smbios
> > > > > mdrv2handler.cpp
> > > > Hi Andrei,
> > > >
> > > > What is the format of smbios data to transfer to BMC? Is it the
> > > > same content of "dmidecode --dump-bin" command from Host Linux?
> or
> > > > anything special in formatting the content to send?
> > > >
> > > > > On Mon, 2021-09-13 at 17:40 +0300, Alexander Raih wrote:
> > > > > > Hi guys, I am beginner in openbmc I build openbmc with
> > > > > > smbios-mdr repository and I have error:
> > > > > >
> > > > > > Read data from flash error - Open MDRV2 table file failure
> > > > > >
> > > > > > There isnt file in /var/lib/smbios/smbios2
> > > > > >
> > > > > > How I can resolve this problem?
> > > > > > Help me please!!!
>
>
> --
> Best regards,
> Andrei Kartashev
>
next prev parent reply other threads:[~2021-09-15 13:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 14:40 Read smbios2 file failed Alexander Raih
2021-09-13 16:56 ` Andrei Kartashev
2021-09-14 6:46 ` Thang Nguyen
2021-09-14 8:51 ` Andrei Kartashev
2021-09-15 5:41 ` Thang Nguyen
2021-09-15 8:16 ` Andrei Kartashev
2021-09-15 13:18 ` Garrett, Mike (HPE Server Firmware) [this message]
2021-09-16 2:40 ` CS20 CHLi30
2021-09-16 11:18 ` Thang Nguyen
2021-09-16 22:36 ` Jie Yang
2021-09-17 13:40 ` Thang Nguyen
2022-08-19 9:50 ` 回覆: " Chris Chen (TPI)
2022-08-23 7:38 ` Chris Chen (TPI)
2022-08-23 16:43 ` Brandon Kim
2022-08-24 9:25 ` 回覆: " Chris Chen (TPI)
2022-08-24 16:37 ` Brandon Kim
2022-08-29 3:51 ` Thang Q. Nguyen
2022-08-29 17:56 ` Brandon Kim
2022-08-30 1:09 ` Thang Q. Nguyen
2022-08-30 7:39 ` Chris Chen (TPI)
2022-08-30 16:22 ` Brandon Kim
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DF4PR8401MB06341BDD6521896375C0CF498FDB9@DF4PR8401MB0634.NAMPRD84.PROD.OUTLOOK.COM \
--to=mike.garrett@hpe.com \
--cc=a.kartashev@yadro.com \
--cc=openbmc@lists.ozlabs.org \
--cc=thang@amperemail.onmicrosoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).