command: Directly call command_sendf() for ack/nak messages

Don't use the sendf() macro for ack and nak messages - directly call
the command_sendf() code instead.

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
Kevin O'Connor 2017-06-20 12:09:55 -04:00
parent 849096d5f3
commit c1bd628ce5
2 changed files with 8 additions and 11 deletions

View file

@ -222,6 +222,11 @@ command_lookup_parser(uint8_t cmdid)
return &command_index[cmdid];
}
// Empty message (for ack/nak transmission)
const struct command_encoder encode_acknak PROGMEM = {
.max_size = MESSAGE_MIN,
};
enum { CF_NEED_SYNC=1<<0, CF_NEED_VALID=1<<1 };
// Find the next complete message.
@ -256,7 +261,7 @@ command_find_block(char *buf, uint8_t buf_len, uint8_t *pop_count)
goto nak;
}
next_sequence = ((msgseq + 1) & MESSAGE_SEQ_MASK) | MESSAGE_DEST;
sendf(""); // An empty message with a new sequence number is an ack
command_sendf(&encode_acknak);
return 1;
need_more_data:
@ -282,7 +287,7 @@ need_sync: ;
return -1;
sync_state |= CF_NEED_VALID;
nak:
sendf(""); // An empty message with a duplicate sequence number is a nak
command_sendf(&encode_acknak);
return -1;
}