Add support for e1000 NICs to OVMF

1) Update README describing the QEMU version required for e1000, where to download the UEFI drivers for e1000, and how to enable network drivers in the platform firmware
2) Update DSC/FDF files NETWORK_ENABLE switch to enable e1000 and network driver support




git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@10697 6f19259b-4bc3-4df7-8a09-765794883524

1 files changed, 22 insertions, 4 deletions

diff --git a/OvmfPkg/README b/OvmfPkg/README
index 1c0646f20a..4220d34c50 100644
--- a/OvmfPkg/README
+++ b/OvmfPkg/README
@@ -16,6 +16,7 @@ Current capabilities:
 * QEMU (0.9.1 or later)

   - Video, keyboard, IDE, CD-ROM, serial

   - Runs UEFI shell

+  - Optional NIC support.  Requires QEMU (0.12.2 or later)

 * UEFI Linux has booted (but is not stable)

 

 === FUTURE PLANS ===

@@ -32,6 +33,11 @@ Pre-requisites:
       or

   * Microsoft ASL compiler: Available from http://www.acpi.info

 

+Optional Pre-requisites:

+* UEFI drivers for the e1000 NIC supported by QEMU

+  * http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=17515&lang=eng

+  * Install the drivers into a directory called Intel3.5 in your WORKSPACE

+  

 Update Conf/target.txt ACTIVE_PLATFORM for OVMF:

                              PEI arch   DXE arch   UEFI interfaces

 * OvmfPkg/OvmfPkgIa32.dsc      IA32       IA32           IA32

@@ -48,10 +54,13 @@ Following the edk2 build process, you will find the OVMF binaries
 under the $WORKSPACE/Build/*/*/FV directory.  The actual path will

 depend on how your build is configured.  You can expect to find

 these binary outputs:

-* OVMF.Fv

-  * Please note!  This filename has changed.  Older releases used OVMF.fd.

+* OVMF.FD

+  * Please note!  This filename has changed.  Older releases used OVMF.Fv.

 * CirrusLogic5446.rom

 

+To enable network support add -D NETWORK_ENABLE to the build.exe command

+* build -D NETWORK_ENABLE

+

 More information on building OVMF can be found at:

 

 http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=How_to_build_OVMF

@@ -59,7 +68,7 @@ http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=How_to_build_OVM
 === RUNNING OVMF on QEMU ===

 

 * QEMU 0.9.1 or later is required.

-* Either copy, rename or symlink OVMF.Fv => bios.bin

+* Either copy, rename or symlink OVMF.FD => bios.bin

 * Either copy, rename or symlink CirrusLogic5446.rom => vgabios-cirrus.bin

 * Be sure to use qemu-system-x86_64, if you are using and X64 firmware.

   (qemu-system-x86_64 works for the IA32 firmware as well, of course.)

@@ -72,4 +81,13 @@ http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=How_to_build_OVM
   removable media.

 * On Linux, newer version of QEMU may enable KVM feature, and this might cause OVMF

   to fail to boot.  The QEMU '-no-kvm' may allow OVMF to boot.

-

+* Use the QEMU -net parameter to enable NIC support.

+  * QEMU does not support UEFI DHCP or UEFI PXE Boot, so lomg timeouts will occur

+    when NICs are enabled.  The long timeouts can be avoided by interrupts the 

+    boot sequence by pressing a key when the logo appears. 

+  * Enable e1000 NIC with a DHCP server and restrict packet forwarding

+    -net nic,model=e1000 -net user,restrict=yes -net user,dhcpstart=10.0.2.10

+  * Enable e1000 NIC with a DHCP server, restrict packet forwarding, and generate PCAP file

+    -net nic,model=e1000 -net user,restrict=yes -net user,dhcpstart=10.0.2.10 -net dump,file=a.pcap

+  * Enable 2 e1000 NICs with a DHCP server and restrict packet forwarding

+    -net nic,model=e1000,addr=3 -net nic,model=e1000,addr=4 -net user,restrict=yes -net user,dhcpstart=10.0.2.10