FreeCalypso > hg > fc-magnetite
view cdg211/prim/gmmsms.pdf @ 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 | 56abf6cf8a0b |
children |
line wrap: on
line source
;******************************************************************************** ;*** File : gmmsms.pdf ;*** Creation : Fri Jun 08 13:57:30 CST 2007 ;*** XSLT Processor : Apache Software Foundation / http://xml.apache.org/xalan-j / supports XSLT-Ver: 1 ;*** Copyright : (c) Texas Instruments AG, Berlin Germany 2002 ;******************************************************************************** ;*** Document Type : Service Access Point Specification ;*** Document Name : gmmsms ;*** Document No. : 8441.105.99.001 ;*** Document Date : 1999-06-22 ;*** Document Status: BEING_PROCESSED ;*** Document Author: ANS ;******************************************************************************** PRAGMA SRC_FILE_TIME "Mon Nov 24 15:50:12 2003" PRAGMA LAST_MODIFIED "1999-06-22" PRAGMA ID_AND_VERSION "8441.105.99.001" VALTAB VAL_reg_state VAL 0 SMS_RS_DEREGISTERED "GMM context for SMS is removed" VAL 1 SMS_RS_REGISTERED "GMM context for SMS is built" VALTAB VAL_radio_priority_level VAL DEF "priority level 4" VAL 1 SMS_RP_LEVEL_1 "priority level 1" VAL 2 SMS_RP_LEVEL_2 "priority level 2??????????" VAL 3 SMS_RP_LEVEL_3 "priority level 3" VAL 4 SMS_RP_LEVEL_4 "priority level 4" VAR reg_state "Registration state" B VAL @p_gmmsms - VAL_reg_state@ VAR radio_priority_level "Radio priority level" B VAL @p_gmmsms - VAL_radio_priority_level@ ; GMMSMS_REG_STATE_REQ 0x2300 ; GMMSMS_REG_STATE_CNF 0x6300 PRIM GMMSMS_REG_STATE_REQ 0x2300 { } PRIM GMMSMS_REG_STATE_CNF 0x6300 { reg_state ; Registration state radio_priority_level ; Radio priority level }