HDCommon.h

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Merge branch 'develop' of ssh://dvm-linux02:7999/hd/hdfirmware into develop

Enabled a build switch

Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Sean Nash please reply.

Sean Nash please reply.

Good point, I updated it.

Good point, I updated it.

I uninitialized it.

I uninitialized it.

That is right.

That is right.

Sean Nash please reply.

Sean Nash please reply.

Sean Nash please respond,.

Sean Nash please respond,.

This code has been removed already.

This code has been removed already.

Yes. We might go back to it.

Yes. We might go back to it.

It must be removed.

It must be removed.

Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Shouldn't this include be in TaskGeneral.c?

Shouldn't this include be in TaskGeneral.c?

Is the commented test code still needed?

Is the commented test code still needed?

Venous pressure does not have an error count. Is it needed?

Venous pressure does not have an error count. Is it needed?

Do we want to keep this commented out defs?

Do we want to keep this commented out defs?

Should 300 be a magic number?

Should 300 be a magic number?

Should 300 be a magic number?

Should 300 be a magic number?

There are no changes in this file and its not a new file.

There are no changes in this file and its not a new file.

Did we ever get clarification on these threshold values?

Did we ever get clarification on these threshold values?

Is this supposed to be assigned to zero? it is unlike the other variables that have been changed

Is this supposed to be assigned to zero? it is unlike the other variables that have been changed

based on the struct, fanStatus.dutycycle does not need to be initialized NUM_OF_FANS_NAMES times.

based on the struct, fanStatus.dutycycle does not need to be initialized NUM_OF_FANS_NAMES times.

Do these variables need to be volatile?

Do these variables need to be volatile?

Bamboo Commit: Updated HDCommon.h with build versions from Bamboo