audk/DuetPkg
erictian ff19726366 variable driver doesn't support EFI_AUTHENTICATED_WRITE_ACCESS. we use:
1. EFI_INVALID_PARAMETER as a return value of SetVariable() to indicate it does not support this feature.
2. EFI_NOT_FOUND will be a return value of QueryVariableInfo() to indicate it does not support this feature.

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@10280 6f19259b-4bc3-4df7-8a09-765794883524
2010-03-18 08:57:05 +00:00
..
AcpiResetDxe 1. Correct File header to ## @file 2010-02-24 00:21:16 +00:00
BiosVideoThunkDxe 1. Correct File header to ## @file 2010-02-24 00:21:16 +00:00
BootSector 1, Remove comma after year 2010-03-10 02:36:05 +00:00
CpuDxe Remove svn:executable on *.c, *.h, *.asm, *.S, *.inf and *.asl* 2010-02-25 18:17:41 +00:00
DataHubGenDxe Remove over-specified dependencies on IntelFrameworkPkg and IntelFrameworkModulePkg. 2010-03-03 03:21:43 +00:00
DxeIpl Change the PM Timer RegisterBitWidth according to the Flags 2010-03-11 09:33:40 +00:00
EfiLdr Remove over-specified dependencies on IntelFrameworkPkg and IntelFrameworkModulePkg. 2010-03-03 03:21:43 +00:00
FSVariable variable driver doesn't support EFI_AUTHENTICATED_WRITE_ACCESS. we use: 2010-03-18 08:57:05 +00:00
FvbRuntimeService Clean up EFI_SPECIFICATION_VERSION and PI_SPECIFICATION_VERSION. 2010-02-25 16:52:10 +00:00
Include 1, Remove comma after year 2010-03-10 02:36:05 +00:00
LegacyMetronome 1. Correct File header to ## @file 2010-02-24 00:21:16 +00:00
Library Remove over-specified dependencies on IntelFrameworkPkg and IntelFrameworkModulePkg. 2010-03-03 03:21:43 +00:00
PciBusNoEnumerationDxe DuetPkg: Fix build break caused by EFI_SPECIFICATION_VERSION usage 2010-02-26 00:30:20 +00:00
PciRootBridgeNoEnumerationDxe Remove over-specified dependencies on IntelFrameworkPkg and IntelFrameworkModulePkg. 2010-03-03 03:21:43 +00:00
RtPlatformStatusCode 1. Correct File header to ## @file 2010-02-24 00:21:16 +00:00
SmbiosGenDxe Remove over-specified dependencies on IntelFrameworkPkg and IntelFrameworkModulePkg. 2010-03-03 03:21:43 +00:00
CreateBootDisk.bat Separate IA32/X64 architecture into two DSC file to avoid the their output mixup. 2010-03-18 02:36:52 +00:00
CreateBootDisk.sh Separate IA32/X64 architecture into two DSC file to avoid the their output mixup. 2010-03-18 02:36:52 +00:00
DuetPkg.dec Cleanup license header 2010-03-10 01:23:13 +00:00
DuetPkg.fdf Remove FD section from DuetPkg.fdf and move the BlockSize/NumBlocks declaration from FD to FV. 2010-03-16 05:22:23 +00:00
DuetPkgIa32.dsc Separate IA32/X64 architecture into two DSC file to avoid the their output mixup. 2010-03-18 02:36:52 +00:00
DuetPkgX64.dsc Separate IA32/X64 architecture into two DSC file to avoid the their output mixup. 2010-03-18 02:36:52 +00:00
PostBuild.bat Separate IA32/X64 architecture into two DSC file to avoid the their output mixup. 2010-03-18 02:36:52 +00:00
PostBuild.sh Separate IA32/X64 architecture into two DSC file to avoid the their output mixup. 2010-03-18 02:36:52 +00:00
ReadMe.txt 1. update bat file to generate right bootia32.efi/bootx64.efi file according to command line parameters. 2010-01-19 08:28:28 +00:00

ReadMe.txt

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Developer's UEFI Emulation (DUET) on Edk2

A. Build DUET image on Windows Platform
========================================
1. Tools preparation

To build DUET image, following tools are required:

  1). *Visual Studio 2005*
      Assume installed at <VS_PATH>, 
      e.g.: C:\Program Files\Microsoft Visual Studio .NET 2003\.
  2). WinDDK
      Assume installed at <WIN_DDK_PATH>, e.g.: C:\WINDDK\3790.1830\.
      
2. Build steps

2.1 Build Duet Platform module   

  1). run cmd.exe to open command line window.
  2). enter workspace root directory such as c:\edk2_tree
  2). run "edksetup.bat"
  3). run "build -p DuetPkg\DuetPkg.dsc -a IA32" for IA32 architecture platform or 
          "build -p DuetPkg\DuetPkg.dsc -a X64" for X64 architecture platform.
 
2.2 Execute post build actions  
  1). enter <Workspace>\DuetPkg directory.
  2). run "PostBuild.bat IA32" for IA32 architecture platform or 
          "PostBuild.bat X64" for X64 architecture platform.

Create bootable disk
======================
  
3. Create boot disk
  The following steps are same for IA32 architecture platform or X64 architecture platform.
  
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 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 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 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
======================================        
1. Tools preparation

	To build DUET image, Mingw GCC is required:
	
		1).  Check out build tools project from svn repository: https://buildtools.tianocore.org/svn/buildtools/trunk/BaseTools
		2).  Assume check out directory is /R9/BaseTools, enter /R9/BaseTools/gcc directory. Please refer to README.txt install all the necessary
			 build packages following:
			 * Python 2.5
			 * texinfo
             * bison
             * flex
             * libmpfr
             * libgmp 
             * As well as (possibly) others tools and development packages
             
		3).  Run mingw-gcc-install.py from gcc folder, this script will download/build/install MingwGCC and BinUtil automatically
		4).  Create symbol link in linux environment at /opt to match default setting in tools_def.txt
			 "ln -s /R9/BaseTools/gcc/symlinks/ar   /opt/tiano/i386-tiano-pe/i386-tiano-pe/bin/ar"
			 "ln -s /R9/BaseTools/gcc/symlinks/gcc  /opt/tiano/i386-tiano-pe/i386-tiano-pe/bin/gcc"
			 "ln -s /R9/BaseTools/gcc/symlinks/ld   /opt/tiano/i386-tiano-pe/i386-tiano-pe/bin/ld"
		
	
2. Build steps

2.1 Build Duet Platform module   

  1). run cmd.exe to open command line window.
  2). enter workspace root directory such as /R9_tree
  2). run "edksetup.sh BaseTools"
  3). run "build -p DuetPkg/DuetPkg.dsc -a IA32 -t UNIXGCC" for IA32 architecture platform or 
          "build -p DuetPkg/DuetPkg.dsc -a X64 -t UNIXGCC" for X64 architecture platform.
  
2.2 Execute post build actions  
  1). enter /R9_tree/DuetPkg directory.
  2). run "./PostBuild.sh IA32" for IA32 architecture platform or 
          "./PostBuild.sh X64" for X64 architecture platform.

 NOTE: After post build action, you should check the size of EfiLdr at $WORKSPACE/Build/DuetPkg/DEBUG_UNIXGCC directory, it must less than 470k.
       If not, you should manually remove some unnecessary drivers at DuetPkg.fdf file.
 
3. Create bootable disk
   The following steps are same for IA32 architecture platform or X64 architecture platform.
   Now only support floopy.
   
   3.1 Create floppy boot disk
	  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 IA32"