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.

/*
 * The interactive command entry (editing) function in libcommon
 * will call mygetchar() for its character input.  It is supposed
 * to be a blocking wait for input, but in some programs other
 * processing can be done while waiting - for example, check for
 * keypad presses as well.  This is the basic version which waits
 * for serial input and nothing else.
 */

extern int serial_in_poll();

int
mygetchar()
{
	register int c;

	do
		c = serial_in_poll();
	while (c < 0);
	return c;
}