board preprocessor conditionals: prep for more FC hw in the future This change eliminates the CONFIG_TARGET_FCDEV3B preprocessor symbol and all preprocessor conditionals throughout the code base that tested for it, replacing them with CONFIG_TARGET_FCFAM or CONFIG_TARGET_FCMODEM. These new symbols are specified as follows: CONFIG_TARGET_FCFAM is intended to cover all hardware designs created by Mother Mychaela under the FreeCalypso trademark. This family will include modem products (repackagings of the FCDEV3B, possibly with RFFE or even RF transceiver changes), and also my desired FreeCalypso handset product. CONFIG_TARGET_FCMODEM is intended to cover all FreeCalypso modem products (which will be firmware-compatible with the FCDEV3B if they use TI Rita transceiver, or will require a different fw build if we switch to one of Silabs Aero transceivers), but not the handset product. Right now this CONFIG_TARGET_FCMODEM preprocessor symbol is used to conditionalize everything dealing with MCSI. At the present moment the future of FC hardware evolution is still unknown: it is not known whether we will ever have any beyond-FCDEV3B hardware at all (contingent on uncertain funding), and if we do produce further FC hardware designs, it is not known whether they will retain the same FIC modem core (triband), if we are going to have a quadband design that still retains the classic Rita transceiver, or if we are going to switch to Silabs Aero II or some other transceiver. If we produce a quadband modem that still uses Rita, it will run exactly the same fw as the FCDEV3B thanks to the way we define TSPACT signals for the RF_FAM=12 && CONFIG_TARGET_FCFAM combination, and the current fcdev3b build target will be renamed to fcmodem. OTOH, if that putative quadband modem will be Aero-based, then it will require a different fw build target, the fcdev3b target will stay as it is, and the two targets will both define CONFIG_TARGET_FCFAM and CONFIG_TARGET_FCMODEM, but will have different RF_FAM numbers. But no matter which way we are going to evolve, it is not right to have conditionals on CONFIG_TARGET_FCDEV3B in places like ACI, and the present change clears the way for future evolution.

/*
+--------------------------------------------------------------------+
| PROJECT : XXX                        SOURCE : CUS_CST.H            |
| AUTHOR  : XXX                        VERSION: 1.0                  |
| CREATED : 01.02.99                   STATE  : code                 |
+--------------------------------------------------------------------+

   MODULE  : CUS_CST

   PURPOSE : Custom dependent definitions for the CST entity of the
             mobile station.

             Use this header for definitions to integrate the protocol
             stack entity CST in your target system.
*/

#ifndef CUS_CST_H
#define CUS_CST_H


/*==== CONSTANTS ==================================================*/
/*
 * TIMER_VALUES
 *
 * Description :  The constants define the timer values for the CST
 *                timer TXXX depending on the various channel types
 *                and service access point identifiers.
 *
 *                If your target system uses other units please
 *                change the values.
 */

/*
 * Unit is 1 ms 
 */
#define T_RX_VALUE              1000
#define TICS_PER_DECIHOURS      (1000*60*6)


/*
 * MAX_CST_TIMER
 *
 * Description :  The constant define the number of timer available
 *                in the timer pool.
 */
#define MAX_CST_TIMER 4

/*
 * VERSION
 *
 * Description :  The constants define the type and the value of a
 *                version identification. The version is part of the
 *                monitor struct.
 */
#define T_VERSION   char
#define VERSION_CST  "CST 1.0"

/*
 * VSI_CALLER
 *
 * Description :  For multithread applications the constant VSI_CALLER
 *                must be defined to identify the calling thread of the
 *                VSI-Interface. This must be done correponding to the
 *                type of T_VSI_CALLER in VSI.H. The comma symbol is
 *                neccessary because the vsi-functions are called
 *                like this vsi_xxx (VSI_CALLER par2, par3 ...)
 */

#ifdef OPTION_MULTITHREAD
#define VSI_CALLER cst_handle,
#define VSI_CALLER_SINGLE cst_handle
#else
#define VSI_CALLER
#define VSI_CALLER_SINGLE
#endif

#endif // CUS_CST_H