From: "Tinh Nguyen" <tinhnguyen@os.amperecomputing.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"rebecca@bsdio.com" <rebecca@bsdio.com>,
"richardho@ami.com" <richardho@ami.com>
Subject: Re: [edk2-devel] [PATCH v3 1/3] UsbNetworkPkg/UsbRndis: Add USB RNDIS devices support
Date: Thu, 16 Feb 2023 11:52:02 +0000 [thread overview]
Message-ID: <5bb09caf-693c-c60b-6ca4-586d4f1e8123@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <40f04734-1178-bc8d-cee5-5e6f829b8306@bsdio.com>
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
On 2/15/2023 10:13 PM, Rebecca Cran via groups.io wrote:
+[PcdsFixedAtBuild, PcdsPatchableInModule, PcdsDynamic, PcdsDynamicEx]
+ ## Support rate limiting
+ gUsbNetworkPkgTokenSpaceGuid.EnableRateLimiting|FALSE|BOOLEAN|0x00010001
+
+ ## The rate limiting Credit value is check in rate limiter event.
+ # It is to control the RateLimitingCreditCount max value.
+ gUsbNetworkPkgTokenSpaceGuid.RateLimitingCredit|10|UINT32|0x00010002
+
Is that valid to have all those PCD types in a single section?
I found this style in MdeModulePkg, and thanks to this Platform code may specify this PCD as the type they want to use
https://github.com/tianocore/edk2/blob/5c551d6d912967ada3084033acea8acf37256043/MdeModulePkg/MdeModulePkg.dec#L1637
But I have no idea whether that is valid or not.
oop it reminds me of my issue.
Recently you add ArmPlatformPkg/PrePeiCore: Print the firmware version early in boot · tianocore/edk2@56035d1 (github.com)<https://github.com/tianocore/edk2/commit/56035d1c8b255b33b34cd4625c26bc7d38504e30>
this causes a problem when using gEfiMdeModulePkgTokenSpaceGuid.PcdFirmwareVersionString as a dynamic PCD (PrePei doesn't support pcdlib);
e.g., we need to add information to PcdFirmwareVersionString (that can come from arm-tf or optionRom ...).
Thanks,
Tinh
[-- Attachment #2: Type: text/html, Size: 1947 bytes --]
prev parent reply other threads:[~2023-02-16 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 5:36 [PATCH v3 1/3] UsbNetworkPkg/UsbRndis: Add USB RNDIS devices support RichardHo [何明忠]
2023-02-15 5:36 ` [PATCH v3 2/3] UsbNetworkPkg/UsbCdcEcm: Add USB Cdc ECM " RichardHo [何明忠]
2023-02-15 5:36 ` [PATCH v3 3/3] UsbNetworkPkg/UsbCdcNcm: Add USB Cdc NCM " RichardHo [何明忠]
2023-02-15 5:47 ` [PATCH v3 1/3] UsbNetworkPkg/UsbRndis: Add USB RNDIS " Tony Lo (羅金松)
2023-02-15 17:28 ` [edk2-devel] " Rebecca Cran
2023-02-16 7:06 ` RichardHo [何明忠]
2023-02-15 10:23 ` Michael Brown
2023-02-16 2:21 ` RichardHo [何明忠]
2023-02-15 15:13 ` Rebecca Cran
2023-02-16 11:52 ` Tinh Nguyen [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=5bb09caf-693c-c60b-6ca4-586d4f1e8123@amperemail.onmicrosoft.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