From: Ryan Harkin <ryan.harkin@linaro.org>
To: Shaveta Leekha <shaveta.leekha@nxp.com>
Cc: "linaro-uefi@lists.linaro.org" <linaro-uefi@lists.linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Varun Sethi <V.Sethi@nxp.com>
Subject: Re: SMBIOS/DMI data creation
Date: Fri, 4 Nov 2016 09:07:59 +0000 [thread overview]
Message-ID: <CAD0U-hL-6dU6pDT1NfM1=-g5=gXYdHzB_LHXd+tj2raJ0k7=HQ@mail.gmail.com> (raw)
In-Reply-To: <DB5PR0401MB198941FBEBB7C327C91F8D728FA20@DB5PR0401MB1989.eurprd04.prod.outlook.com>
On 4 November 2016 at 07:22, Shaveta Leekha <shaveta.leekha@nxp.com> wrote:
> Hi,
>
> I was adding SMBIOS DMI data in UEFI for our ARM64 platform.
> One patch that I referred is of ARM JUNO platform:
> ArmPlatformPkg/ArmJunoPkg: Create SMBIOS/DMI data for Juno
>
> In it, almost all SMBIOS table entries/structures are populated statically with information.
> Is it preliminary support?
I think so.
> can we fill most of the information like:
> Memory module information
> Cache related info etc by reading from registers or from system at run time instead of filling it statically?
>
I think that would be the nicest way to do it. Static configuration
isn't ideal, IMO. But on a board like Juno, where the config isn't
likely to change, I think it's acceptable to hard code it; or at
least, it's better than doing nothing.
> Any views?
>
> Thanks and Regards,
> Shaveta
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2016-11-04 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 7:22 SMBIOS/DMI data creation Shaveta Leekha
2016-11-04 9:07 ` Ryan Harkin [this message]
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-list 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='CAD0U-hL-6dU6pDT1NfM1=-g5=gXYdHzB_LHXd+tj2raJ0k7=HQ@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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