From 58e1d1ebb78bfdaf05f4c6e8abf8d4908dfa038a Mon Sep 17 00:00:00 2001

From: Laszlo Ersek <lersek@redhat.com>

Date: Thu, 20 Feb 2014 22:54:45 +0100

Subject: OvmfPkg: increase max debug message length to 512

Upstream prefers short debug messages (sometimes even limited to 80

characters), but any line length under 512 characters is just unsuitable

for effective debugging. (For example, config strings in HII routing,

logged by the platform driver "OvmfPkg/PlatformDxe" on DEBUG_VERBOSE

level, can be several hundred characters long.) 512 is an empirically good

value.

Notes about the 20160608b-988715a -> 20170228-c325e41585e3 rebase:

- no changes

Notes about the 20170228-c325e41585e3 -> 20171011-92d07e48907f rebase:

- no changes

Signed-off-by: Laszlo Ersek <lersek@redhat.com>

(cherry picked from commit bfe568d18dba15602604f155982e3b73add63dfb)

(cherry picked from commit 29435a32ec9428720c74c454ce9817662e601fb6)

---

 OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c | 2 +-

 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c b/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c

index 5435767..01016c3 100644

--- a/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c

+++ b/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c

@@ -27,7 +27,7 @@

 //

 // Define the maximum debug and assert message length that this library supports

 //

-#define MAX_DEBUG_MESSAGE_LENGTH  0x100

+#define MAX_DEBUG_MESSAGE_LENGTH  0x200

 /**

   This constructor function does not have to do anything.

-- 

1.8.3.1