BaseTools/BinToPcd: Fix Python 2.7.x compatibility issue

[mirror_edk2.git] / SourceLevelDebugPkg / Readme.txt

diff --git a/SourceLevelDebugPkg/Readme.txt b/SourceLevelDebugPkg/Readme.txt
index e43ed18b427d72f72656185d1887f827a747a0c8..cb5d976d770651e7c527015cbd4da4b1d0de93df 100644 (file)
--- a/SourceLevelDebugPkg/Readme.txt
+++ b/SourceLevelDebugPkg/Readme.txt
@@ -1,8 +1,6 @@
-UDK based firmware on UEFI IA-32 and UEFI x64 platforms may be debugged using Microsoft(R) Debugging Tools for Windows(R) (WinDbg). Debug capability is enabled with SourceLevelDebugPkg in conjunction with the Intel(R) UEFI Development Kit Debugger Tool (Intel(R) UDK Debugger Tool).\r
+UDK based firmware on UEFI IA-32 and UEFI x64 platforms can be debugged with\r
+SourceLevelDebugPkg in conjunction with Intel(R) UEFI Development Kit Debugger\r
+Tool (Intel (R) UDK Debugger Tool).\r
 \r
-The Intel(R) UDK Debugger Tool and its detailed user manual may be obtained from:\r
-http://www.intel.com/technology/efi. \r
-\r
-NOTE: In addition to the known issues listed in the user manual, the following anomalies have been observed:\r
-\r
-1) When using a USB debug cable, after the TARGET completes a reset during memory initialization, the connection between the HOST and the TARGET may be lost (e.g. WinDbg reports busy status and does not respond to a break request). A work around for this issue is to unplug the USB debug cable and then plug the cable back in. A new debug session may then be started.
\ No newline at end of file
+The Intel(R) UDK Debugger Tool and its detailed user manual can be obtained\r
+from: http://www.uefidk.com/develop.\r