view cdg211/prim/tra.pdf @ 685:3fb7384e820d

tpudrv12.h: FCDEV3B goes back to being itself A while back we had the idea of a FreeCalypso modem family whereby our current fcdev3b target would some day morph into fcmodem, with multiple FC modem family products, potentially either triband or quadband, being firmware-compatible with each other and with our original FCDEV3B. But in light of the discovery of Tango modules that earlier idea is now being withdrawn: instead the already existing Tango hw is being adopted into our FreeCalypso family. Tango cannot be firmware-compatible with triband OM/FCDEV3B targets because the original quadband RFFE on Tango modules is wired in TI's original Leonardo arrangement. Because this Leonardo/Tango way is now becoming the official FreeCalypso way of driving quadband RFFEs thanks to the adoption of Tango into our FC family, our earlier idea of extending FIC's triband RFFE control signals with TSPACT5 no longer makes much sense - we will probably never produce any new hardware with that once-proposed arrangement. Therefore, that triband-or-quadband FCFAM provision is being removed from the code base, and FCDEV3B goes back to being treated the same way as CONFIG_TARGET_GTAMODEM for RFFE control purposes.
author Mychaela Falconia <falcon@freecalypso.org>
date Thu, 24 Sep 2020 21:03:08 +0000
parents 56abf6cf8a0b
children
line wrap: on
line source

;********************************************************************************
;*** File           : tra.pdf
;*** Creation       : Fri Jun 08 13:58:41 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  : tra
;*** Document No.   : 8411.106.98.101
;*** Document Date  : 2002-06-10
;*** Document Status: BEING_PROCESSED
;*** Document Author: TVO
;********************************************************************************



PRAGMA 	SRC_FILE_TIME 	"Mon Nov 24 15:49:20 2003"
PRAGMA 	LAST_MODIFIED 	"2002-06-10"
PRAGMA 	ID_AND_VERSION 	"8411.106.98.101"






VALTAB 	VAL_entity_name
VAL 	6 	TRA_ENTITY_NAME_LEN 	"Max name length"

VALTAB 	VAL_ack_flg
VAL 	0 	TRA_ACK 	"acknowledged"
VAL 	1 	TRA_NAK 	"not acknowledged"

VALTAB 	VAL_dti_direction
VAL 	0 	TRA_DTI_NORMAL 	"DTI used normally"
VAL 	1 	TRA_DTI_INVERTED 	"DTI is inverted"

VALTAB 	VAL_dti_conn
VAL 	0 	TRA_CONNECT_DTI 	"Connect DTI to TRA"
VAL 	1 	TRA_DISCONNECT_DTI 	"Connect DTI to upper layer"




VAR 	entity_name 	"name of an neighbour entity" 	B

VAL 	@p_tra - VAL_entity_name@ 	

VAR 	ack_flg 	"acknowledge flag" 	B

VAL 	@p_tra - VAL_ack_flg@ 	

VAR 	link_id 	"link identifier" 	L


VAR 	dti_direction 	"DTI direction" 	B

VAL 	@p_tra - VAL_dti_direction@ 	

VAR 	dti_conn 	"DTI connect" 	B

VAL 	@p_tra - VAL_dti_conn@ 	







; TRA_ACTIVATE_REQ 	0x80000019
; TRA_ACTIVATE_CNF 	0x80004019
; TRA_DEACTIVATE_REQ 	0x80010019
; TRA_DEACTIVATE_CNF 	0x80014019
; TRA_DTI_REQ 	0x80020019
; TRA_DTI_CNF 	0x80024019
; TRA_DTI_IND 	0x80034019



PRIM 	TRA_ACTIVATE_REQ 	0x80000019
{
}






PRIM 	TRA_ACTIVATE_CNF 	0x80004019
{
 	ack_flg 	 ; acknowledge flag
}






PRIM 	TRA_DEACTIVATE_REQ 	0x80010019
{
}






PRIM 	TRA_DEACTIVATE_CNF 	0x80014019
{
}






PRIM 	TRA_DTI_REQ 	0x80020019
{
 	dti_conn 	 ; DTI connect
 	link_id 	 ; Link identifier of DTI
 	entity_name 	[TRA_ENTITY_NAME_LEN] 	 ; Communication entity name
 	dti_direction 	 ; DTI direction
}






PRIM 	TRA_DTI_CNF 	0x80024019
{
 	dti_conn 	 ; DTI connect
 	link_id 	 ; Link identifier
}






PRIM 	TRA_DTI_IND 	0x80034019
{
 	link_id 	 ; link identifier
}