From 1387bda01b089d8e8df06339d9c15d53b3de6725 Mon Sep 17 00:00:00 2001 From: Patrick Benavoli Date: Wed, 31 Aug 2011 11:23:24 +0200 Subject: Min/max value computation; Tuning lock handling BZ: 7466 - Min/max values are now correctly computed. They concern integer and fixed point parameters - tuning mode lock issue solved: created an AutoLock class for safe lock handling - added configuration files for a demo on Ubuntu environment - had AMIXER subsystem plugin compliant for derivation - LPE library: add carriage return on logs - removed obsolete files - some cosmetics Change-Id: Ife7a4799fd48dd4a1ca25dae666c4e453815881e Orig-Change-Id: I72fc5c1ff6abf638b43266a75bc00e21ad412349 Signed-off-by: Patrick Benavoli Reviewed-on: http://android.intel.com:8080/16880 Reviewed-by: Mahe, Erwan Tested-by: Barthes, FabienX Reviewed-by: buildbot Tested-by: buildbot --- remote-processor/Message.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'remote-processor') diff --git a/remote-processor/Message.cpp b/remote-processor/Message.cpp index 5679501..4454b1c 100644 --- a/remote-processor/Message.cpp +++ b/remote-processor/Message.cpp @@ -236,7 +236,7 @@ bool CMessage::serialize(CSocket* pSocket, bool bOut) // Checksum uint8_t CMessage::computeChecksum() const { - uint8_t uiChecksum = (_ucMsgId & 0xFF) + (_ucMsgId >> 8); + uint8_t uiChecksum = _ucMsgId; uint32_t uiIndex; -- cgit v1.1