FreeCalypso > hg > fc-magnetite

view cdg211/msg/tst.mdf @ 600:8f50b202e81f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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           : tst.mdf
;*** Creation       : Fri Jun 08 13:59:02 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  : Air Interface Message Specification
;*** Document Name  : tst
;*** Document No.   : 8441.603.99.005
;*** Document Date  : 2000-10-23
;*** Document Status: BEING_PROCESSED
;*** Document Author: ANS
;********************************************************************************



PRAGMA 	SRC_FILE_TIME 	"Mon Nov 24 15:50:42 2003"
PRAGMA 	LAST_MODIFIED 	"2000-10-23"
PRAGMA 	ID_AND_VERSION 	"8441.603.99.005"



CONST 	L3MAX 	251 	; maximum size of a L3 buffer
CONST 	MAX_N_PDU_NUMBER_LIST 	11 	; maximum size of N-PDU number list



VALTAB 	VAL_no_of_pdus
VAL 	DEF 	 	"Number of PDUs to transmit"
VAL 	0 	TEST_INFINITIVE_NO 	"ciphering not used"

VALTAB 	VAL_dl_timeslot_offset
VAL 	0 	TEST_TN0 	"downlink timeslot offsett 0"
VAL 	1 	TEST_TN1 	"downlink timeslot offsett 1"
VAL 	2 	TEST_TN2 	"downlink timeslot offsett 2"
VAL 	3 	TEST_TN3 	"downlink timeslot offsett 3"
VAL 	4 	TEST_TN4 	"downlink timeslot offsett 4"
VAL 	5 	TEST_TN5 	"downlink timeslot offsett 5"
VAL 	6 	TEST_TN6 	"downlink timeslot offsett 6"
VAL 	7 	TEST_TN7 	"downlink timeslot offsett 7"

VALTAB 	VAL_mode_flag_val
VAL 	0 	TEST_RANDOM 	"pseudorandom data"
VAL 	1 	TEST_LOOP 	"loop back"




VAR 	msg_type 	"Message Type" 	
 	8


VAR 	no_of_pdus 	"Number of PDUs" 	
 	12

VAL 	@m_tst - VAL_no_of_pdus@ 	

VAR 	dl_timeslot_offset 	"Downlink Timeslot Offset" 	
 	3

VAL 	@m_tst - VAL_dl_timeslot_offset@ 	

VAR 	mode_flag_val 	"Mode Flag Value" 	
 	1

VAL 	@m_tst - VAL_mode_flag_val@ 	




COMP 	pdu_description 	"PDU Description"
{
 	.000  ; spare
 	 	no_of_pdus 	 ; Number
}



COMP 	pdu_description_ie 	"PDU Description IE"
{
 	CSN1_S1  	pdu_description 	 ; PDU Description
}



COMP 	mode_flag 	"Mode Flag"
{
 	.0000  ; spare
 	 	dl_timeslot_offset 	 ; Downlink Timeslot Offset
 	 	mode_flag_val 	 ; Mode Flag Value
}






MSG 	gprs_test_mode_cmd 	downlink 	36 ; gprs_test_mode_cmd
{
 	GSM3_V  	msg_type 	 ; Message Type
 	GSM3_V  	pdu_description_ie 	 ; PDU description
 	GSM3_V  	mode_flag 	 ; Mode Flag
}