public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: Blibbet <blibbet@gmail.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Carsey, Jaben" <jaben.carsey@intel.com>
Subject: Re: *BinPkg question
Date: Mon, 6 Mar 2017 16:33:02 +0000	[thread overview]
Message-ID: <CB6E33457884FA40993F35157061515C54B9755D@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <73bb0ed5-1490-4aaa-e38a-c388fae518a6@gmail.com>

Few thoughts - with the UEFI Shell Specification complaint shell binary from ShellBinPkg (not the minimal one of course), you have all the documented commands.  There was no reason to provide individual binaries per command.  That was dropped completely with the standardization with the spec.  What "external command" is missing from the shell?  Except for the DP command (which is not in the spec), I am unaware of "missing" commands.

BCFG command can configure the BOOTXXXX and DRIVERXXXX variables.

-Jaben

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Blibbet
> Sent: Saturday, March 04, 2017 1:14 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] *BinPkg question
> Importance: High
> 
> I've been working on building thumbdrives that boot into the UEFI Shell,
> and have a few end-user questions, please.
> 
> I've always been unclear which version of EFI/UEFI Apple includes on
> their hardware. Are the older EdkShellBinPkg shells suitable for modern
> Apple boxes, or will the modern UEFI Shell work on them?
> 
> What is the point of shipping compiled full/minimal UEFI Shells, and not
> shipping the related external tools? I presumed the point of shipping
> the shell.efi binaries in the EDK2 was to help users who need to add a
> shell to their system for some diagnostic reasons. If that's the point,
> wouldn't it be useful to have the related external shell commands that
> help with diagnosis and configuring boot### variables?
> 
> It appears older EFI Shell did include external binaries, but results
> vary greatly by architecture, it appears AArch32 includes the most
> commands. Some use an ./Apps subdirectory, others do not.
> 
> https://github.com/tianocore/edk2/tree/master/EdkShellBinPkg/Bin/
> 
> but modern bin package only include shells (and omits IPF binaries,
> unlike earlier EdkShellBinPkg):
> 
> https://github.com/tianocore/edk2/tree/master/ShellBinPkg
> 
> I am unclear why include just a shell and not include the related
> external commands in the ShellBinPkg.
> 
> Is there a reason for modern released systems that these older
> EdkShellBinPkg shells/commands will be needed?
> 
> Is there another source of precompiled external shell commands, beyond
> ShellBinPkg, that would work with the shells included in the ShellBinPkg?
> 
> The target audience for this is sysadmins, so telling them to build it
> from source is not an option for audience.
> 
> Thanks for *any* advise!
> 
> Lee Fisher
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2017-03-06 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04 21:14 *BinPkg question Blibbet
2017-03-06 16:33 ` Carsey, Jaben [this message]
2017-03-07  0:33   ` Blibbet

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=CB6E33457884FA40993F35157061515C54B9755D@FMSMSX103.amr.corp.intel.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