FreeCalypso > hg > fc-magnetite
view src/ui3/mfw/mfw_utils.h @ 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 | e8ddbb0837ed |
| children |
line wrap: on
line source
/* +--------------------------------------------------------------------+ | PROJECT: MMI-Framework (8417) $Workfile:: mfw_utils.h $| | $Author:: NDH $Revision:: 1 $| | CREATED: 6.1.2003 $Modtime:: 10.04.00 14:58 $| | STATE : code $| +--------------------------------------------------------------------+ MODULE : MFW_UTILS PURPOSE : This modul contains General Functional Utilities. HISTORY: Jun 05, 2004 REF: CRR 18262 NISHIKANT KULKARNI Description: The sample sends a STOP DTMF message without release of the key by the user Solution: Instead of sending DTMF commands in "VTS_MOD_Auto" mode, on key press DTMF tone is started using VTS_MOD_ManStart and on key release DTMF tone is stopped using VTS_MOD_ManStop mode. */ /* ** Limiting Macros */ #define MAX_CBUF_QUEUES 3 /* ** Return Value Macros */ #define MFW_CBUF_OK 1 #define MFW_CBUF_OK_DATA_LOSS 2 #define MFW_CBUF_INVALID_BUF_ID (-1) #define MFW_CBUF_NO_BUFS_AVAILABLE (-2) #define MFW_CBUF_MEM_ALLOC_FAILURE (-3) #define MFW_CBUF_INVALID_ITEM_SIZE (-4) #define MFW_CBUF_INVALID_MAX_ITEMS (-5) #define MFW_CBUF_INVALID_BUF_PTR (-6) #define MFW_CBUF_INVALID_STATIC_BUF (-7) #define MFW_CBUF_PUT_FAILED_Q_FULL (-8) #define MFW_CBUF_BUFFER_EMPTY (-9) /* ** Function Prototypes xnkulkar SPR-18262: Added the prototypes for mfw_cbuf_put_mode() and mfw_cbuf_get_mode() */ SHORT mfw_cbuf_create (USHORT max_num_items, USHORT item_size, UBYTE overwrite, UBYTE null_char, UBYTE static_buf, void *buffer_ptr); SHORT mfw_cbuf_delete (SHORT bufId); SHORT mfw_cbuf_reset (SHORT bufId); SHORT mfw_cbuf_put (SHORT bufId, void *data_ptr); SHORT mfw_cbuf_get (SHORT bufId, void *data_ptr); SHORT mfw_cbuf_put_mode (SHORT bufId,UBYTE vts_mode); //xnkulkar SPR-18262 SHORT mfw_cbuf_get_mode (SHORT bufId); //xnkulkar SPR-18262 USHORT mfw_cbuf_num_elements (SHORT bufId);
