FPOperationModes.h

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 2 more files in changeset.
Updated, Thanks

Updated, Thanks

Fix return description. This function is not setting anything. Should be something like TRUE if request handled successfully.

Fix return description. This function is not setting anything. Should be something like TRUE if request handled successfully.

LDT-3159 addressed CR review comments

Fixed

Fixed

Fix comment.

Fix comment.

LEAHI-DD-FIRMWARE-LDT-3159_[Request] A getter function to read the DD FW for the defeatureized state
LEAHI-DD-FIRMWARE-LDT-3159_[Request] A getter function to read the DD FW for the defeatureized state
LDT-3159 added dialin test funcion to return FP defeatured status

  1. … 2 more files in changeset.
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 121 more files in changeset.
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 121 more files in changeset.
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 121 more files in changeset.
Done

Done

No I removed it.

No I removed it.

I will resolve this for now, but I don't think ACKs are necessary and I'm pretty sure TD is not looking for a response. TD may be waiting for DD to change mode by looking at DD mode broadcasts.

I will resolve this for now, but I don't think ACKs are necessary and I'm pretty sure TD is not looking for a response. TD may be waiting for DD to change mode by looking at DD mode broadcasts.

fixed. thanks

fixed. thanks

I think so. the TD needs to know if we are successful in stopping Gen mode for either the DD or the FP. Otherwise, TD is waiting for something else that'll never happen. whether that should be a s...

I think so. the TD needs to know if we are successful in stopping Gen mode for either the DD or the FP. Otherwise, TD is waiting for something else that'll never happen.

whether that should be a separate message response or ACK is up for discussion.

I think so. the TD needs to know if we are successful in transitioning to PreGen for either the DD or the FP. Otherwise, TD is waiting for something else that'll never happen. whether that should ...

I think so. the TD needs to know if we are successful in transitioning to PreGen for either the DD or the FP. Otherwise, TD is waiting for something else that'll never happen.

whether that should be a separate message response or ACK is up for discussion.

I think so. the TD needs to know if we are successful in transitioning to PreGen for either the DD or the FP. Otherwise, TD is waiting for something else that'll never happen. whether that should ...

I think so. the TD needs to know if we are successful in transitioning to PreGen for either the DD or the FP. Otherwise, TD is waiting for something else that'll never happen.

whether that should be a separate message response or ACK is up for discussion.

fixed. thanks

fixed. thanks

Ok, but see my next comment below. Do we need to ACK with a result at all? Does TD require this?

Ok, but see my next comment below. Do we need to ACK with a result at all? Does TD require this?

updated to now change result to FALSE if we get a rr that is not NONE

updated to now change result to FALSE if we get a rr that is not NONE

updated to now change result to FALSE if we get a rr that is not NONE

updated to now change result to FALSE if we get a rr that is not NONE

reworked to use the request stop functions in their respective op modes.

reworked to use the request stop functions in their respective op modes.