view rvinterf/tmsh/ffs2resp.c @ 407:19e5a3e2f9c0

fcup-settime: moved time() retrieval a little closer to the output A fundamental problem with all simple time transfer tools is that there is always some delay between the time retrieval on the source system and that transmitted time being set on the destination, and the resulting time on the destination system is off by that delay amount. This delay cannot be fully eliminated when working in a simple environment like ours, but we should make our best effort to minimize it. In the present case, moving the atinterf_init() call before the time() retrieval should make a teensy-tiny improvement.
author Mychaela Falconia <falcon@freecalypso.org>
date Sat, 11 Aug 2018 21:52:17 +0000
parents e7502631a0f9
children
line wrap: on
line source

/*
 * Handling of TMFFS2 responses from ETM
 */

#include <sys/types.h>
#include <stdio.h>

extern u_char rvi_msg[];
extern int rvi_msg_len;

void
handle_ffs2_response()
{
	if (rvi_msg[3])
		print_etm_pkt_raw("FFS2 error");
	else if (rvi_msg_len == 5)
		async_msg_output("FFS2 command successful");
	else
		print_etm_pkt_raw("FFS2 response");
}