view rvinterf/lowlevel/client.h @ 497:74610c4f10f7

target-utils: added 10 ms delay at the end of abb_power_off() The deosmification of the ABB access code (replacement of osmo_delay_ms() bogus delays with correctly-timed ones, which are significantly shorter) had one annoying side effect: when executing the poweroff command from any of the programs, one last '=' prompt character was being sent (and received by the x86 host) as the Calypso board powers off. With delays being shorter now, the abb_power_off() function was returning and the standalone program's main loop was printing its prompt before the Iota chip fully executed the switch-off sequence! I thought about inserting an endless tight loop at the end of the abb_power_off() function, but the implemented solution of a 10 ms delay is a little nicer IMO because if the DEVOFF operation doesn't happen for some reason in a manual hacking scenario, there won't be an artificial blocker in the form of a tight loop keeping us from further poking around.
author Mychaela Falconia <falcon@freecalypso.org>
date Sat, 25 May 2019 20:44:05 +0000
parents e7502631a0f9
children
line wrap: on
line source

/*
 * The structure defined in this header file is malloced in rvinterf
 * for every client program connection.
 */

#define	MAX_RVT_INTEREST	4

typedef	unsigned u32;

struct client {
	struct	client *next;
	int	fd;
	int	rx_state;
	u_char	rx_buf[LOCALSOCK_MAX_MSG];
	int	rx_msglen;
	u_char	*rx_ptr;
	int	rx_left;
	int	int_rvt_count;
	u32	int_rvt_mask[MAX_RVT_INTEREST];
	u32	int_rvt_match[MAX_RVT_INTEREST];
	char	int_proto[12];
};