GateMP: Fix maxValueLen for GateMP's NameServer3.50.04.08B3.50

Commit id 16c8220d5d895329de83b52060928968958f8a3d intruduced
a change to the max size of the value that GateMP will add
to its internal NameServer. However, the GateMP module's
setting for its NameServer's maxValueLen was not updated to
reflect the new max possible value for the case where
hostSupport is set to FALSE.

This patch updates the maxValueLen to be large enough
to accommodate the max value size used.

Signed-off-by: Angela Stegmaier <angelabaker@ti.com>

1 files changed, 3 insertions, 2 deletions

diff --git a/packages/ti/sdo/ipc/GateMP.xs b/packages/ti/sdo/ipc/GateMP.xs
index 9dfb165..d7022c1 100644
--- a/packages/ti/sdo/ipc/GateMP.xs
+++ b/packages/ti/sdo/ipc/GateMP.xs
@@ -133,11 +133,12 @@ function module$static$init(mod, params)
     }
     else {
         /*
-         *  Need 2 words:
+         *  Need 3 words:
          *    1 word for the SharedRegion Ptr.
          *    1 word for the proc id of creator and if remote is allowed.
+         *    1 word for upper 32-bits in case of > 32-bit address
          */
-        GateMP.nameSrvPrms.maxValueLen = 2 * target.stdTypes["t_Int32"].size;
+        GateMP.nameSrvPrms.maxValueLen = 3 * target.stdTypes["t_Int32"].size;
 	mod.hostSupport = false;
     }