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.

/*
 * Limits on FFS filenames and pathnames
 *
 * The deepest pathname allowed is one of the form /1/2/3/4/5/6, where the
 * last component may be a file, a directory or a symlink; if this last
 * component is a directory, it has to be empty, because any child of
 * that directory would violate the depth limit.
 *
 * The proper FFS pathname form begins with a slash (all pathnames must
 * be absolute, no Unix processes in the fw means no current directories),
 * has exactly one slash in each separating place (no double slashes),
 * and no trailing slash except in the special case of the root directory,
 * whose full pathname is "/".
 *
 * Each component name is [1,20] characters long; combining this limit
 * with the maximum depth of 6 puts the maximum length of a properly-formed
 * full pathname at 126 characters.
 */

#define	MAX_FN_COMPONENT	20
#define	MAX_NAME_DEPTH		6
#define	MAX_FULL_PATHNAME	((MAX_FN_COMPONENT+1) * MAX_NAME_DEPTH)