view src/cs/services/atp/atp_gsm_gsm_api_dummy.c @ 600:8f50b202e81f

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.
author Mychaela Falconia <falcon@freecalypso.org>
date Mon, 01 Apr 2019 01:05:24 +0000
parents 945cf7f506b2
children
line wrap: on
line source

/*******************************************************************************
*
* File Name : atp_gsm_gsm_api.c
*
* This file contains dummy definition of all functions called by the ATP-GSM plug-in.
* These functions must be provided by CONDAT with their PS
*
*
* Version number	: 0.1      Date : 19-Dec-2001
*
* History			: 0.1  - Created 
*
* Author			: 
*
*   (C) Copyright 2001 by Texas Instruments Incorporated 
*****************************************************************************/

#ifdef _WINDOWS
// In this case, no GSM PS
// So need to define these dummy functions

#include "rv/rv_general.h"
#include "atp/atp_gsm_bt_api.h"
#include "atp/bti_at.h"

#if ( ((ATP_REGR != SW_COMPILED) && (ATP_MISC != SW_COMPILED))  )

/* functions define in GSM side and called by BT side */
void bti_at_init_cnf(T_BTI_ACK ack)
{

}

void bti_at_deinit_ind(void)
{
}
 
void bti_at_open_port_ind(T_BTI_PORT_NB gsm_port_nb,T_BTI_BT_PORT_INFO bt_custom_info)
{

}

void bti_at_close_port_ind(T_BTI_PORT_NB gsm_port_nb)
{
}
void bti_at_cmd_ind(T_BTI_PORT_NB gsm_port_nb,char * cmd)
{
}
void bti_at_cmd_cnf(T_BTI_PORT_NB gsm_port_nb)
{
}
void bti_at_abort_ind(T_BTI_PORT_NB gsm_port_nb)
{
}
void bti_data_ready_ind(T_BTI_PORT_NB port_nb,unsigned long nb_of_data)
{
}
void bti_get_gsm_data(T_BTI_PORT_NB port_nb,char * buffer, unsigned long nb_of_data)
{
}
void bti_data_ready_cnf(T_BTI_PORT_NB port_nb)
{
}

#endif

#endif