FreeCalypso > hg > fc-magnetite
view cdg3/sap/mac.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 | c15047b3d00d |
| children |
line wrap: on
line source
;******************************************************************************** ;*** File : mac.pdf ;*** Creation : Wed Mar 11 09:58:17 CST 2009 ;*** 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 : mac ;*** Document No. : 8441.111.03.009 ;*** Document Date : 2003-02-26 ;*** Document Status: BEING_PROCESSED ;*** Document Author: SAB ;******************************************************************************** PRAGMA SRC_FILE_TIME "Thu Nov 29 09:45:32 2007" PRAGMA LAST_MODIFIED "2003-02-26" PRAGMA ID_AND_VERSION "8441.111.03.009" CONST MAC_MAX_TIMESLOTS 8 ; defines the maximum number of uplink data blocks CONST MAC_BURST_PER_BLOCK 4 ; number of bursts that compose a block CONST MAC_MAX_DL_DATA_BLCKS 4 ; maximum number of dowlink data blocks VALTAB VAL_bcch_level VAL 0 MAC_RXLEV_MIN "minimum receive signal level as defined in GSM 05.08" VAL 63 MAC_RXLEV_MAX "maximum receive signal level as defined in GSM 05.08" VAL 0x80 MAC_RXLEV_NONE "no valid receive signal level present" VALTAB VAL_crc_error VAL 0 GRLC_CRC_PASS "radio block is correctly received" VAL 1 GRLC_CRC_FAIL "radio block is not correctly received" VAR nts "Maximum number of Timeslots for uplink TBF" B VAR fn "Framenumber" L VAR rlc_blocks_sent "number of transmitted rlc/mac blocks (except polling)" B VAR rx_no "Number of received Timeslots" S VAR block_status "Block Status" S VAR tn "Timeslot number" S VAR ul_block "Uplink block" S VAR dl_block "Downlink block" S VAR last_poll_resp "Last Poll Response" B VAR ta_value "Timing Advance Value" B VAR d_macc "Accumulated Metric" S VAR d_nerr "Number of estimated erorrs" S VAR burst_level "Signal level of the first valid downlink PDCH; ." B VAR radio_freq "Radio frequency of the TDMA frame; ." S VAR bcch_level "Signal level of BCCH serving Cell; ." B VAL @p_mac - VAL_bcch_level@ VAR crc_error "CRC error; ." B VAL @p_mac - VAL_crc_error@ VAR assignment_id "assignment identifier; ." L COMP ul_poll_resp "Uplink Poll Response" { block_status ; Block Status tn ; Timeslot number ul_block [13] ; Uplink block } COMP ul_data "Uplink Data" { block_status ; Block Status ul_block [28] ; Uplink block } COMP dl_data "Downlink Data" { block_status ; Block Status tn ; Timeslot number d_macc ; Accumulated Metric d_nerr ; Number of estimated erorrs dl_block [27] ; Downlink block } ; MAC_DATA_REQ 0x3200 ; MAC_DATA_IND 0x7200 ; MAC_READY_IND 0x7201 ; MAC_POLL_REQ 0x3201 ; MAC_PWR_CTRL_IND 0x7202 PRIM MAC_DATA_REQ 0x3200 { ul_data ; Uplink Data } PRIM MAC_DATA_IND 0x7200 { fn ; Framenumber rx_no ; Number of received Timeslots dl_data ; Downlink Data } PRIM MAC_READY_IND 0x7201 { nts ; Maximum number of Timeslots for uplink TBF fn ; Framenumber rlc_blocks_sent ; number of transmitted rlc/mac blocks (except polling) last_poll_resp ; Last Poll Response ta_value ; Timing Advance Value } PRIM MAC_POLL_REQ 0x3201 { ul_poll_resp ; Uplink Poll Response } PRIM MAC_PWR_CTRL_IND 0x7202 { assignment_id ; Assignment identifier crc_error ; CRC error bcch_level ; Signal level of BCCH serving Cell radio_freq [MAC_BURST_PER_BLOCK] ; Radio frequency of the TDMA frame burst_level [MAC_BURST_PER_BLOCK] ; Signal level of the first valid downlink PDCH }
