public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Liu, Zhiguang" <zhiguang.liu@intel.com>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>
Cc: Rebecca Cran <rebecca@quicinc.com>
Subject: Re: [PATCH v2 1/1] MdePkg: Add new JedecJep106Lib to fetch JEDEC JEP106 manufacturer
Date: Fri, 7 Apr 2023 16:42:52 -0600	[thread overview]
Message-ID: <63b08db7-50cd-e319-ecab-3ec380337874@bsdio.com> (raw)
In-Reply-To: <CO1PR11MB4929A1B04CE6FDF2696B4F01D2969@CO1PR11MB4929.namprd11.prod.outlook.com>

On 4/7/23 2:25 PM, Kinney, Michael D wrote:
> Comments below.
>
> Hopefully this lib would only be used by modules that get compressed.
I guess so, but that's for the user to decide.
>
> Might add GLOBAL_REMOVE_IF_UNREFERENCED to the arrays of strings to
> help the optimizer remove the data that is not referenced.

Good idea - I'll add that.

>> +CONST CHAR8 *
>> +EFIAPI
>> +Jep106GetManufacturerName (
>> +  IN UINT8  Code,
>> +  IN UINT8  ContinuationBytes
>> +  )
>> +{
>> +  UINTN                      Index;
>> +  CONST JEDEC_MANUFACTURERS  *ManufacturersBank;
>> +
>> +  Index = 0;
>> +
>> +  if (ContinuationBytes >= JEP106_MANUFACTURERS_NUM_BANKS) {
>> +    ASSERT (0);
> Do you really want an ASSERT() from this?  If this is data from a DIMM
> I doubt we want platform to ASSERT().  Perhaps just return NULL?
I'll remove it. I added it for validation when I was writing the SPD 
parsing library.
>> +UINTN
>> +EFIAPI
>> +Jep106GetLongestManufacturerName (
>> +  VOID
>> +  )
> Why is this API needed?  Wouldn’t you really just need the
> longest of the ones present in the current boot to build the
> SMBIOS record?.  Not the longest of all in the banks?

I added it because it's useful to know the maximum possible size of the 
strings that could be in the SMBIOS Type 17 table before doing the SPD 
parsing.

I'll remove it for now, and if it's really needed I can add it back in.


-- 
Rebecca Cran


  reply	other threads:[~2023-04-07 22:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 16:19 [PATCH v2 0/1] MdePkg: Add new JedecJep106Lib to fetch JEDEC JEP106 manufacturer Rebecca Cran
2023-04-07 16:19 ` [PATCH v2 1/1] " Rebecca Cran
2023-04-07 20:25   ` Michael D Kinney
2023-04-07 22:42     ` Rebecca Cran [this message]
     [not found]     ` <1753C85A6247B7C4.11060@groups.io>
2023-04-07 22:58       ` [edk2-devel] " Rebecca Cran
2023-04-07 23:06         ` Michael D Kinney
2023-04-07 23:10           ` Rebecca Cran
2023-04-07 23:18             ` Michael D Kinney

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=63b08db7-50cd-e319-ecab-3ec380337874@bsdio.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