Fix file guid conflict.

[mirror_edk2.git] / OvmfPkg / README

diff --git a/OvmfPkg/README b/OvmfPkg/README
index c37bfb6316f0cb82e48d7c0ac5c8f9f88533e2ba..d6b6f8c27d53dfca707db7789a75235bbfcfffc8 100644 (file)
--- a/OvmfPkg/README
+++ b/OvmfPkg/README
@@ -28,10 +28,9 @@ Current capabilities:
 \r
 Pre-requisites:\r
 * Build environment capable of build the edk2 MdeModulePkg.\r
-* A properly configured ASL compiler\r
-  * Intel ASL compiler: Available from http://www.acpica.org\r
-      or\r
-  * Microsoft ASL compiler: Available from http://www.acpi.info\r
+* A properly configured ASL compiler:\r
+  - Intel ASL compiler: Available from http://www.acpica.org\r
+  - Microsoft ASL compiler: Available from http://www.acpi.info\r
 \r
 Update Conf/target.txt ACTIVE_PLATFORM for OVMF:\r
                              PEI arch   DXE arch   UEFI interfaces\r
@@ -50,8 +49,8 @@ under the $WORKSPACE/Build/*/*/FV directory.  The actual path will
 depend on how your build is configured.  You can expect to find\r
 these binary outputs:\r
 * OVMF.FD\r
-  * Please note!  This filename has changed.  Older releases used OVMF.Fv.\r
-* CirrusLogic5446.rom\r
+  - Please note!  This filename has changed.  Older releases used OVMF.Fv.\r
+* OvmfVideo.rom\r
 \r
 More information on building OVMF can be found at:\r
 \r
@@ -61,7 +60,7 @@ http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=How_to_build_OVM
 \r
 * QEMU 0.9.1 or later is required.\r
 * Either copy, rename or symlink OVMF.FD => bios.bin\r
-* Either copy, rename or symlink CirrusLogic5446.rom => vgabios-cirrus.bin\r
+* Either copy, rename or symlink OvmfVideo.rom => vgabios-cirrus.bin\r
 * Be sure to use qemu-system-x86_64, if you are using and X64 firmware.\r
   (qemu-system-x86_64 works for the IA32 firmware as well, of course.)\r
 * Use the QEMU -L parameter to specify the directory where the bios.bin\r
@@ -76,15 +75,18 @@ http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=How_to_build_OVM
 \r
 === Build Scripts ===\r
 \r
-On environments with the bash shell you can use OvmfPkg/build32.sh and\r
-OvmfPkg/build64.sh to simplify building and running OVMF.\r
+On systems with the bash shell you can use OvmfPkg/build.sh to simplify\r
+building and running OVMF.\r
 \r
 So, for example, to build + run OVMF X64:\r
-$ OvmfPkg/build64.sh\r
-$ OvmfPkg/build64.sh qemu\r
+$ OvmfPkg/build.sh -a X64\r
+$ OvmfPkg/build.sh -a X64 qemu\r
 \r
 And to run a 64-bit UEFI bootable ISO image:\r
-$ OvmfPkg/build64.sh qemu -cdrom /path/to/disk-image.iso\r
+$ OvmfPkg/build.sh -a X64 qemu -cdrom /path/to/disk-image.iso\r
+\r
+To build a 32-bit OVMF without debug serial messages using GCC 4.5:\r
+$ OvmfPkg/build.sh -a IA32 -b RELEASE -t GCC45\r
 \r
 === Network Support ===\r
 \r