FreeCalypso > hg > fc-magnetite
view cdg211/prim/sn.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 : sn.pdf ;*** Creation : Fri Jun 08 13:58:34 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 : sn ;*** Document No. : 8441.110.99.006 ;*** Document Date : 2001-10-08 ;*** Document Status: BEING_PROCESSED ;*** Document Author: Harald ;******************************************************************************** PRAGMA SRC_FILE_TIME "Thu Feb 17 14:43:54 2005" PRAGMA LAST_MODIFIED "2001-10-08" PRAGMA ID_AND_VERSION "8441.110.99.006" CONST MAX_PARAM_NUMBER 4 ; Maximal number of parameters per compressor unit CONST MAX_COMP_NUMBER 3 ; Currently there are 3 PCOMP values for V.42bis CONST MAX_ENT_NUMBER 1 ; There is 1 data compression entity currently and 1 header compression entity. VALTAB VAL_nsapi VAL 0 NSAPI_0 "escape mechanism for future extensions" VAL 1 NSAPI_1 "Point-To-Multipoint Multicast information" VAL 2 NSAPI_2 "reserved for future use" VAL 3 NSAPI_3 "reserved for future use" VAL 4 NSAPI_4 "reserved for future use" VAL 5 NSAPI_5 "dynamically allocated NSAPI value" VAL 6 NSAPI_6 "dynamically allocated NSAPI value" VAL 7 NSAPI_7 "dynamically allocated NSAPI value" VAL 8 NSAPI_8 "dynamically allocated NSAPI value" VAL 9 NSAPI_9 "dynamically allocated NSAPI value" VAL 10 NSAPI_10 "dynamically allocated NSAPI value" VAL 11 NSAPI_11 "dynamically allocated NSAPI value" VAL 12 NSAPI_12 "dynamically allocated NSAPI value" VAL 13 NSAPI_13 "dynamically allocated NSAPI value" VAL 14 NSAPI_14 "dynamically allocated NSAPI value" VAL 15 NSAPI_15 "dynamically allocated NSAPI value" VALTAB VAL_p_id VAL 0x21 PPP_PID_IP "simple ip packet" VAL 0x2D PPP_PID_CTCP "Van Jacobson compressed TCP/IP header" VAL 0x2F PPP_PID_UTCP "Van Jacobson uncompressed TCP/IP header" VALTAB VAL_ppp_hc VAL 0 SN_HC_OFF "no header compression" VAL 1 SN_HC_VJ "Van Jacobson header compression" VALTAB VAL_reset VAL 0 SN_RESET_NO "no reset" VAL 1 SN_RESET_YES "reset" VALTAB VAL_dti_direction VAL 1 SN_HOME "mapped to HOME from dti.h" VAL 0 SN_NEIGHBOR "mapped to NEIGHBOR from dti.h" VAR nsapi "network layer service access point identifier" B VAL @p_sn - VAL_nsapi@ VAR list_len "length in octets of whole data" S VAR first "pointer to generic data descriptors" L VAR p_id "protocol identifier" B VAL @p_sn - VAL_p_id@ VAR l_buf "length of content in bit" S VAR o_buf "offset of content in bit" S VAR buf "buffer content" B VAR reserved_data_ind2 "reserved octets" B VAR reserved_unitdata_ind2 "reserved octets" B VAR reserved_data_req1 "reserved octets" B VAR reserved_data_req3 "reserved octets" B VAR reserved_unitdata_req1 "reserved octets" B VAR reserved_unitdata_req3 "reserved octets" B VAR ref_nsapi "ref_nsapi" B VAR ref_npdu_num "ref_npdu_num" S VAR ref_seg_num "ref_seg_num" B VAR ppp_hc "header compression of PPP connection" B VAL @p_sn - VAL_ppp_hc@ VAR msid "max slot identifier" B VAR reset "reset flag" B VAL @p_sn - VAL_reset@ VAR octets_uplink "octets uplink" L VAR octets_downlink "octets downlink" L VAR packets_uplink "packets uplink" L VAR packets_downlink "packets downlink" L VAR dti_linkid "DTI link identifier" L VAR dti_neighbor "DTI neighbor entity name" L VAR dti_direction "direction of DTI connection" B VAL @p_sn - VAL_dti_direction@ COMP desc_list2 "list of generic data descriptors" { list_len ; length in octets of whole data first ; pointer to generic data descriptors } COMP sdu "service data unit" { l_buf ; length of content in bit o_buf ; offset of content in bit buf [1] ; buffer content } COMP reserved_data_ind1 "to the segment to be confirmed" { ref_nsapi ; ref_nsapi ref_npdu_num ; ref_npdu_num ref_seg_num ; ref_seg_num } TYPEDEF COMP reserved_data_ind1 reserved_unitdata_ind1 "to the segment to be confirmed" TYPEDEF COMP reserved_data_ind1 reserved_data_req2 "to the segment to be confirmed" TYPEDEF COMP reserved_data_ind1 reserved_unitdata_req2 "to the segment to be confirmed" ; SN_MODIFICATION_IND 0x6808 ; SN_COUNT_REQ 0x2808 ; SN_COUNT_CNF 0x6809 ; SN_SWITCH_REQ 0x2809 ; SN_SWITCH_CNF 0x680A PRIM SN_MODIFICATION_IND 0x6808 { ppp_hc ; header compression of PPP connection msid ; max slot identifier } PRIM SN_COUNT_REQ 0x2808 { nsapi ; network layer service access point identifier reset ; shall counters be reset } PRIM SN_COUNT_CNF 0x6809 { nsapi ; network layer service access point identifier octets_uplink ; octets uplink octets_downlink ; octets downlink packets_uplink ; packets uplink packets_downlink ; packets downlink } PRIM SN_SWITCH_REQ 0x2809 { nsapi ; network layer service access point identifier dti_linkid ; dti linkid dti_neighbor ; dti neighbor dti_direction ; dti direction } PRIM SN_SWITCH_CNF 0x680A { nsapi ; network layer service access point identifier }