summaryrefslogtreecommitdiffstats
path: root/DuetPkg/ReadMe.txt
diff options
context:
space:
mode:
authoreric_tian <eric_tian@6f19259b-4bc3-4df7-8a09-765794883524>2010-01-19 08:28:28 +0000
committereric_tian <eric_tian@6f19259b-4bc3-4df7-8a09-765794883524>2010-01-19 08:28:28 +0000
commite843cdd7d9ed9e72e0df61f46e5a073a0797615e (patch)
tree6a74c4f5488988289007ad6875a0add39f21464f /DuetPkg/ReadMe.txt
parent1ccdbf2a3e61fe9494fcd39432107ba0eb74f584 (diff)
downloadedk2-e843cdd7d9ed9e72e0df61f46e5a073a0797615e.tar.gz
edk2-e843cdd7d9ed9e72e0df61f46e5a073a0797615e.tar.bz2
edk2-e843cdd7d9ed9e72e0df61f46e5a073a0797615e.zip
1. update bat file to generate right bootia32.efi/bootx64.efi file according to command line parameters.
2. fix a print error in which a %x in format string exists but the corresponding variable argument is not present! 3. fix CONSUME_MEMORY too small issue. In X64 arch, cpu may cause the paging table is too big and beyond the pei memory scope between EfiMemoryTop and EfimemoryBottom. for example, a cpu support 44bits addressing memory space may occupied ~64M paging table. git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@9794 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'DuetPkg/ReadMe.txt')
-rw-r--r--DuetPkg/ReadMe.txt20
1 files changed, 12 insertions, 8 deletions
diff --git a/DuetPkg/ReadMe.txt b/DuetPkg/ReadMe.txt
index 173851b5a1..caaa4fbbf1 100644
--- a/DuetPkg/ReadMe.txt
+++ b/DuetPkg/ReadMe.txt
@@ -36,17 +36,21 @@ Create bootable disk
3.1 Create floppy boot disk
1). enter <Workspace>\DuetPkg directory.
2). Insert a floppy disk to drive
- 3). run "CreateBootDisk.bat floppy a: FAT12" if floppy drive is a: disk.
-
+ 3). run "CreateBootDisk.bat floppy a: FAT12 IA32" if floppy drive is a: disk and Arch to boot is IA32.
+ or
+ run "CreateBootDisk.bat floppy a: FAT12 X64" if floppy drive is a: disk and Arch to boot is X64.
3.2 Create usb boot disk
1). enter <Workspace>\DuetPkg directory.
2). Plugin usb disk
- 3). run "CreateBootDisk.bat usb e: FAT16" if usb drive is e: and FAT format is FAT16 or
- "CreateBootDisk.bat usb e: FAT32" if usb drive is e: and FAT format is FAT32
+ 3). run "CreateBootDisk.bat usb e: FAT16 IA32" if usb drive is e: and FAT format is FAT16 and Arch to boot is IA32.
+ or "CreateBootDisk.bat usb e: FAT16 X64" if usb drive is e: and FAT format is FAT16 and Arch to boot is X64.
+ or "CreateBootDisk.bat usb e: FAT32 IA32" if usb drive is e: and FAT format is FAT32 and Arch to boot is IA32.
+ or "CreateBootDisk.bat usb e: FAT32 X64" if usb drive is e: and FAT format is FAT32 and Arch to boot is X64.
4). UnPlug usb disk and plugin it again.
- 5). run "CreateBootDisk.bat usb e: FAT16 step2" if usb drive is e: and FAT format is FAT16 or
- "CreateBootDisk.bat usb e: FAT32 step2" if usb drive is e: and FAT format is FAT32.
-
+ 5). run "CreateBootDisk.bat usb e: FAT16 IA32 step2" if usb drive is e: and FAT format is FAT16 and Arch to boot is IA32.
+ or "CreateBootDisk.bat usb e: FAT16 X64 step2" if usb drive is e: and FAT format is FAT16 and Arch to boot is X64.
+ or "CreateBootDisk.bat usb e: FAT32 IA32 step2" if usb drive is e: and FAT format is FAT32 and Arch to boot is IA32.
+ or "CreateBootDisk.bat usb e: FAT32 X64 step2" if usb drive is e: and FAT format is FAT32 and Arch to boot is X64.
B. Build DUET image on Linux Platform
======================================
@@ -98,4 +102,4 @@ B. Build DUET image on Linux Platform
1). enter /R9_tree/DuetPkg directory.
2). Insert a floppy disk to drive
3). run "CreateBootDisk.sh" to build floppy drive
- such as "./CreateBootDisk.sh floppy /media/floppy0 /dev/fd0 FAT12" \ No newline at end of file
+ such as "./CreateBootDisk.sh floppy /media/floppy0 /dev/fd0 FAT12 IA32" \ No newline at end of file