public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, quic_tpilar@quicinc.com
Cc: Ray Ni <ray.ni@intel.com>, Zhichao Gao <zhichao.gao@intel.com>
Subject: Re: [edk2-devel] [PATCH v3 1/1] ShellPkg: Export default shell delay as PCD
Date: Thu, 19 Jan 2023 19:25:03 -0700	[thread overview]
Message-ID: <bf40af60-51d5-d47c-9d82-5a1d1d35403a@bsdio.com> (raw)
In-Reply-To: <c411f119-09ed-bed3-b035-896b4499e3e1@quicinc.com>

Could someone review this please?


--

Rebecca Cran


On 1/10/23 05:09, Tomas Pilar (tpilar) wrote:
> Hi,
>
> Any chance you could review this change? It's fairly simple.
>
> Cheers,
> Tom
>
> On 03/01/2023 17:02, Tomas Pilar (tpilar) wrote:
>> From: Tomas Pilar <quic_tpilar@quicinc.com>
>>
>> Create PcdShellDefaultDelay to configure the default
>> delay the shell provides for the user at the start time
>> if the user wishes to cancel the execution of a potential
>> startup script.
>>
>> The shell application already allows the user to override
>> the delay default value by specifying the -delay cmdline
>> argument. This however cannot be used when loading the
>> shell application using direct boot or when integrating
>> the shell into the platform firmware build.
>>
>> Thus, a PCD can be easily configurerd by the developer
>> either at build time, or even at runtime.
>>
>> Cc: Ray Ni <ray.ni@intel.com>
>> Cc: Zhichao Gao <zhichao.gao@intel.com>
>> Signed-off-by: Tomas Pilar <tomas@quicinc.com>
>> ---
>>   ShellPkg/ShellPkg.dec                | 4 ++++
>>   ShellPkg/Application/Shell/Shell.inf | 1 +
>>   ShellPkg/Application/Shell/Shell.c   | 2 +-
>>   3 files changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/ShellPkg/ShellPkg.dec b/ShellPkg/ShellPkg.dec
>> index 7b2d1230bd2c..2ebea0a2615f 100644
>> --- a/ShellPkg/ShellPkg.dec
>> +++ b/ShellPkg/ShellPkg.dec
>> @@ -136,3 +136,7 @@ [PcdsFixedAtBuild, PcdsPatchableInModule, 
>> PcdsDynamic, PcdsDynamicEx]
>>     # Up to this many bytes of vendor specific data will be used. 
>> Default is 0
>>     # (disabled).
>> gEfiShellPkgTokenSpaceGuid.PcdShellVendorExtendedDecode|0|UINT32|0x00000013
>> +
>> +  ## Controls the default delay the shell will offer to the user at the
>> +  # start to check if the user wishes to cancel the script autostart
>> + gEfiShellPkgTokenSpaceGuid.PcdShellDefaultDelay|5|UINT32|0x00000015
>> diff --git a/ShellPkg/Application/Shell/Shell.inf 
>> b/ShellPkg/Application/Shell/Shell.inf
>> index 4c32960a9687..f1e41de133d1 100644
>> --- a/ShellPkg/Application/Shell/Shell.inf
>> +++ b/ShellPkg/Application/Shell/Shell.inf
>> @@ -103,3 +103,4 @@ [Pcd]
>>     gEfiShellPkgTokenSpaceGuid.PcdShellForceConsole           ## 
>> CONSUMES
>>     gEfiShellPkgTokenSpaceGuid.PcdShellSupplier               ## 
>> CONSUMES
>>     gEfiShellPkgTokenSpaceGuid.PcdShellMaxHistoryCommandCount ## 
>> CONSUMES
>> +  gEfiShellPkgTokenSpaceGuid.PcdShellDefaultDelay           ## CONSUMES
>> diff --git a/ShellPkg/Application/Shell/Shell.c 
>> b/ShellPkg/Application/Shell/Shell.c
>> index df00adfdfa5b..0ae6e14a34bf 100644
>> --- a/ShellPkg/Application/Shell/Shell.c
>> +++ b/ShellPkg/Application/Shell/Shell.c
>> @@ -990,7 +990,7 @@ ProcessCommandLine (
>>     ShellInfoObject.ShellInitSettings.BitUnion.Bits.Delay = FALSE;
>>     ShellInfoObject.ShellInitSettings.BitUnion.Bits.Exit = FALSE;
>>     ShellInfoObject.ShellInitSettings.BitUnion.Bits.NoNest = FALSE;
>> -  ShellInfoObject.ShellInitSettings.Delay = 5;
>> +  ShellInfoObject.ShellInitSettings.Delay = PcdGet32 
>> (PcdShellDefaultDelay);
>>       //
>>     // Start LoopVar at 0 to parse only optional arguments at Argv[0]
>
>
>
> 
>
>

  reply	other threads:[~2023-01-20  2:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 17:02 [PATCH v3 1/1] ShellPkg: Export default shell delay as PCD Tomas Pilar (tpilar)
2023-01-10 12:09 ` [edk2-devel] " Tomas Pilar (tpilar)
2023-01-20  2:25   ` Rebecca Cran [this message]
2023-01-20 15:55 ` Michael D Kinney
2023-01-20 16:44   ` 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=bf40af60-51d5-d47c-9d82-5a1d1d35403a@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