FreeCalypso > hg > fc-magnetite
view cdg211/prim/tra.pdf @ 636:57e67ca2e1cb
pcmdata.c: default +CGMI to "FreeCalypso" and +CGMM to model
The present change has no effect whatsoever on Falconia-made and Openmoko-made
devices on which /pcm/CGMI and /pcm/CGMM files have been programmed in FFS
with sensible ID strings by the respective factories, but what should AT+CGMI
and AT+CGMM queries return when the device is a Huawei GTM900 or Tango modem
that has been converted to FreeCalypso with a firmware change? Before the
present change they would return compiled-in defaults of "<manufacturer>" and
"<model>", respectively; with the present change the firmware will self-identify
as "FreeCalypso GTM900-FC" or "FreeCalypso Tango" on the two respective targets.
This firmware identification will become important if someone incorporates an
FC-converted GTM900 or Tango modem into a ZeroPhone-style smartphone where some
high-level software like ofono will be talking to the modem and will need to
properly identify this modem as FreeCalypso, as opposed to some other AT command
modem flavor with different quirks.
In technical terms, the compiled-in default for the AT+CGMI query (which will
always be overridden by the /pcm/CGMI file in FFS if one is present) is now
"FreeCalypso" in all configs on all targets; the compiled-in default for the
AT+CGMM query (likewise always overridden by /pcm/CGMM if present) is
"GTM900-FC" if CONFIG_TARGET_GTM900 or "Tango" if CONFIG_TARGET_TANGO or the
original default of "<model>" otherwise.
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Sun, 19 Jan 2020 20:14:58 +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 }
