Enable Undi driver to support multicast MAC address mapped from IPv6 address

[mirror_edk2.git] / BuildNotes.txt

diff --git a/BuildNotes.txt b/BuildNotes.txt
index 7c2f8eed249f88df084e0db84fc32e2b1d9d8b33..3783da56a98c1d1eff2d66ba558213b6b4047087 100644 (file)
--- a/BuildNotes.txt
+++ b/BuildNotes.txt
@@ -35,8 +35,8 @@ license, on the TianoCore.org website: https://fat-driver2.tianocore.org
   EdkFatPkg      - A package containing source DXE drivers for the Fat 32 file\r
                    system\r
 \r
-Documents have the following filenames (to download these documents, see \93Notes\r
-on Documentation?later in these Release Notes):\r
+Documents have the following filenames (to download these documents, see "Notes\r
+on Documentation" later in these Release Notes):\r
   EDK II Module Development Environment Library Specification, v0.58\r
       (MDE_Library_Spec_0_58.rtf)\r
   EDK II Build and Packaging Architecture Specification, v0.53\r
@@ -153,7 +153,7 @@ Java Development Kit:
        For Bea Systems:\r
               set JAVA_HOME=c:\Java\jrockit-R26.0.0-jdk1.5.0_04\r
 \r
-  ?When using the Sun JDK5.0:\r
+   When using the Sun JDK5.0:\r
     During installation, you should specify the install directory as C:\Java\r
     instead of C:\Program Files\(or some other drive letter.)  While installing\r
     to this non-standard location is not required, in practice, it seems to work\r
@@ -406,8 +406,8 @@ Once this is completed, you are ready to test the build, by executing:
 This command builds the active platform specified in text file target.txt. If\r
 the active platform is not specified target.txt, you must execute the build\r
 command from the sub-directory that contains FPD files. For more information\r
-about the active platform policy, see the \93EDK II Build and Packaging\r
-Architecture Specification.?\r
+about the active platform policy, see the "EDK II Build and Packaging\r
+Architecture Specification."\r
 \r
 -------------------------------------------------------------------------------\r
 Detailed Starting Instructions\r
@@ -467,8 +467,8 @@ Once this is completed, you are ready to test the build, by executing:
 This command builds the active platform specified in text file target.txt. If\r
 the active platform is not specified, go to the sub-directory that contains FPD\r
 files and execute the build command. For more information about the active\r
-platform policy, see the \93EDK II Build and Packaging Architecture\r
-Specification.?\r
+platform policy, see the "EDK II Build and Packaging Architecture\r
+Specification."\r
 \r
 --------------------------\r
 Individual Platform Builds\r
@@ -483,15 +483,15 @@ or
 \r
   Note that the active platform specified in target.txt overrides the platform\r
   specified by any FPD file in the current directory. For more   information\r
-  about active platform policy, see the \93EDK II Build and Packaging Architecture\r
-  Specification.?\r
+  about active platform policy, see the "EDK II Build and Packaging Architecture\r
+  Specification."\r
 \r
 To run the Nt32 emulation platform under Microsoft Windows, go to\r
 <full build path>\DEBUG\MSFT\IA32 and execute SecMain.exe\r
 \r
-To exit the Nt32 emulation platform, type \93reset?at the EFI Shell>\r
+To exit the Nt32 emulation platform, type "reset" at the EFI Shell>\r
 command prompt.  Alternatively, from the graphical interface, select the Boot\r
-Maintenance Manager's \93Reset System?command.\r
+Maintenance Manager's "Reset System" command.\r
 \r
       NOTE: When creating a new platform, the Platform Name is restricted\r
       to a single word containing alphanumeric characters, underscore, dash,\r
@@ -532,8 +532,8 @@ A) The Surface Area Package Description (SPD) file contains information about
 the modules that the package contains, including the location of all MSA files,\r
 and public library names and headers that might be provided by a module in the\r
 package.  Packages are defined by SPD files.  (Found in the root of the Package\r
-subdirectory (i.e. EdkNt32Pkg).) The SPD file is further explained in \93EDK II\r
-Build and Packaging Architecture Specification.?\r
+subdirectory (i.e. EdkNt32Pkg).) The SPD file is further explained in "EDK II\r
+Build and Packaging Architecture Specification."\r
 \r
 B) Module Surface Area Definition (MSA) files.  A description of a module's\r
 surface area, with all module specific default flags and features specified.\r