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 <patrickx.benavoli@intel.com>
Reviewed-on: http://android.intel.com:8080/16880
Reviewed-by: Mahe, Erwan <erwan.mahe@intel.com>
Tested-by: Barthes, FabienX <fabienx.barthes@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
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 @@
// Checksum
uint8_t CMessage::computeChecksum() const
{
- uint8_t uiChecksum = (_ucMsgId & 0xFF) + (_ucMsgId >> 8);
+ uint8_t uiChecksum = _ucMsgId;
uint32_t uiIndex;