| jcarsey | 072d611 | 2011-04-19 16:43:53 +0000 | [diff] [blame^] | 1 | ============================================================================
|
| 2 | OVERVIEW
|
| 3 | ============================================================================
|
| 4 | 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.
|
| 5 |
|
| 6 | The following steps can help to re-generate these binaries for customization:
|
| 7 | 1. Check out EDK II to $(WORKSPACE)
|
| 8 | (svn https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2).
|
| 9 | 2. Under $(WORKSPACE) directory (i.e. c:\EdkII),
|
| 10 | To generate Shell, execute: "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE".
|
| 11 |
|
| 12 |
|
| 13 | ============================================================================
|
| 14 | HOW TO INCORPORATE THIS SHELL INTO NT32
|
| 15 | ============================================================================
|
| 16 | The instructions below are included as a sample and template on how a
|
| 17 | developer may integrate this code into an existing platform:
|
| 18 |
|
| 19 |
|
| 20 | 1. Update system PCDs to support this new module
|
| 21 | Update the PCD as follows using the Shell's PCD:
|
| 22 | gEfiIntelFrameworkModulePkgTokenSpaceGuid.PcdShellFile|{ 0x83, 0xA5, 0x04, 0x7C, 0x3E, 0x9E, 0x1C, 0x4F, 0xAD, 0x65, 0xE0, 0x52, 0x68, 0xD0, 0xB4, 0xD1 }
|
| 23 |
|
| 24 | 2. Remove the old shell from the NT32 Firmware list
|
| 25 | Remove the FILE APPLICATION section for the old shell.
|
| 26 |
|
| 27 | 3. Add this shell to the NT32 firmware list
|
| 28 | Add the Shell.INF to the end of the list of DXE modules.
|
| 29 |
|
| 30 | 4. Build NT32
|
| 31 |
|
| 32 | ============================================================================
|
| 33 | KNOWN LIMITATIONS
|
| 34 | ============================================================================
|
| 35 | 1. RM can delete current working directory via other map name.
|
| 36 | 2. DrvCfg is not functional.
|
| 37 | 3. ifConfig permanent settings are under investigation (may not function correctly)
|
| 38 | 4. Shell documentation is in development and forthcoming.
|
| 39 |
|
| 40 | ============================================================================
|