X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=ShellBinPkg%2FReadMe.txt;h=2e3355b3e796ce1aae208deba85c4437b2e4ec58;hb=c030e74c67b2caec4113e8255e74ccbbe0fcd051;hp=344f8a7f1cc8844783e955353e6ac92c261924af;hpb=072d611689f18d203c922786113c6e39c6f4b878;p=mirror_edk2.git

diff --git a/ShellBinPkg/ReadMe.txt b/ShellBinPkg/ReadMe.txt
index 344f8a7f1c..2e3355b3e7 100644
--- a/ShellBinPkg/ReadMe.txt
+++ b/ShellBinPkg/ReadMe.txt
@@ -1,14 +1,19 @@
 ============================================================================
                                  OVERVIEW
 ============================================================================
-The binaries of ShellBinPkg are generated with ShellPkg project and built with BaseTools Package (r11544). The binaries are built with no debug information by building with "RELEASE" target.
+The binaries of ShellBinPkg are generated with ShellPkg project and built with 
+BaseTools Package (r16473). The binaries are built with no debug information 
+by building with "RELEASE" target.
 
 The following steps can help to re-generate these binaries for customization:
 1. Check out EDK II to $(WORKSPACE) 
-(svn https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2).
-2. Under $(WORKSPACE) directory (i.e. c:\EdkII),
-   To generate Shell, execute: "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE".
+(svn https://svn.code.sf.net/p/edk2/code/trunk/edk2).
 
+2. Under $(WORKSPACE) directory (i.e. c:\EdkII),
+   To generate Shell, execute:
+        "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE"
+   To generate Minimal Shell, execute:
+        "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE -D NO_SHELL_PROFILES"
 
 ============================================================================
                     HOW TO INCORPORATE THIS SHELL INTO NT32
@@ -16,10 +21,11 @@ The following steps can help to re-generate these binaries for customization:
 The instructions below are included as a sample and template on how a 
 developer may integrate this code into an existing platform:
 
-
 1. Update system PCDs to support this new module
    Update the PCD as follows using the Shell's PCD:
-   gEfiIntelFrameworkModulePkgTokenSpaceGuid.PcdShellFile|{ 0x83, 0xA5, 0x04, 0x7C, 0x3E, 0x9E, 0x1C, 0x4F, 0xAD, 0x65, 0xE0, 0x52, 0x68, 0xD0, 0xB4, 0xD1 }
+   gEfiIntelFrameworkModulePkgTokenSpaceGuid.PcdShellFile|{ 0x83, 0xA5, 
+    0x04, 0x7C, 0x3E, 0x9E, 0x1C, 0x4F, 0xAD, 0x65, 0xE0, 0x52, 0x68, 0xD0, 
+    0xB4, 0xD1 }
 
 2. Remove the old shell from the NT32 Firmware list
    Remove the FILE APPLICATION section for the old shell.
@@ -33,8 +39,7 @@ developer may integrate this code into an existing platform:
                           KNOWN LIMITATIONS
 ============================================================================
 1. RM can delete current working directory via other map name.
-2. DrvCfg is not functional.
-3. ifConfig permanent settings are under investigation (may not function correctly)
-4. Shell documentation is in development and forthcoming.
+2. DrvCfg does not overlap boot manager functionality.
+3. Shell documentation is in development and forthcoming.
 
 ============================================================================