]>
Commit | Line | Data |
---|---|---|
1 | ============================================================================\r | |
2 | OVERVIEW\r | |
3 | ============================================================================\r | |
4 | The binaries of ShellBinPkg are generated with ShellPkg project and built with\r | |
5 | BaseTools Package (git version: d2fc7711136a13ea3ea8e00de6d9651507b8ed50). The\r | |
6 | binaries are built with no debug information by building with "RELEASE" target.\r | |
7 | \r | |
8 | To generate Full Shell, execute:\r | |
9 | "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE"\r | |
10 | To generate Minimal Shell, execute:\r | |
11 | "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE -D NO_SHELL_PROFILES"\r | |
12 | \r | |
13 | ============================================================================\r | |
14 | HOW TO INCORPORATE THIS SHELL INTO NT32\r | |
15 | ============================================================================\r | |
16 | The instructions below are included as a sample and template on how a \r | |
17 | developer may integrate this code into an existing platform:\r | |
18 | \r | |
19 | 1. Update system PCDs to support this new module\r | |
20 | Update the PCD as follows using the Shell's PCD:\r | |
21 | gEfiIntelFrameworkModulePkgTokenSpaceGuid.PcdShellFile|{ 0x83, 0xA5, \r | |
22 | 0x04, 0x7C, 0x3E, 0x9E, 0x1C, 0x4F, 0xAD, 0x65, 0xE0, 0x52, 0x68, 0xD0, \r | |
23 | 0xB4, 0xD1 }\r | |
24 | \r | |
25 | 2. Remove the old shell from the NT32 Firmware list\r | |
26 | Remove the FILE APPLICATION section for the old shell.\r | |
27 | \r | |
28 | 3. Add this shell to the NT32 firmware list\r | |
29 | Add the Shell.INF to the end of the list of DXE modules.\r | |
30 | \r | |
31 | 4. Build NT32\r | |
32 | \r | |
33 | ============================================================================\r | |
34 | KNOWN LIMITATIONS\r | |
35 | ============================================================================\r | |
36 | 1. RM can delete current working directory via other map name.\r | |
37 | 2. DrvCfg does not overlap boot manager functionality.\r | |
38 | 3. Shell documentation is in development and forthcoming.\r | |
39 | \r | |
40 | ============================================================================\r |