view cdg211/prim/tra.pdf @ 624:012028896cfb

FFS dev.c, Leonardo target: Fujitsu MB84VF5F5F4J2 #if 0'ed out The FFS code we got from TI/Openmoko had a stanza for "Fujitsu MB84VF5F5F4J2 stacked device", using a fake device ID code that would need to be patched manually into cfgffs.c (suppressing and overriding autodetection) and using an FFS base address in the nCS2 bank, indicating that this FFS config was probably meant for the MCP version of Leonardo which allows for 16 MiB flash with a second bank on nCS2. We previously had this FFS config stanza conditionalized under CONFIG_TARGET_LEONARDO because the base address contained therein is invalid for other targets, but now that we actually have a Leonardo build target in FC Magnetite, I realize that the better approach is to #if 0 out this stanza altogether: it is already non-functional because it uses a fake device ID code, thus it is does not add support for more Leonardo board variants, instead it is just noise.
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 22 Dec 2019 21:24:29 +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
}