FreeCalypso > hg > fc-magnetite
view src/ui3/mfw/mfw_nmi.h @ 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 | e8ddbb0837ed |
| children |
line wrap: on
line source
/* +--------------------------------------------------------------------+ | PROJECT: GSM-MFW (?) $Workfile:: mfw_nmi.h $| | $Author:: Vo $Revision:: 1 $| | CREATED: 07.10.98 $Modtime:: 21.10.99 12:18 $| | STATE : code | +--------------------------------------------------------------------+ PURPOSE : Internal definitions for network management History May 31, 2007 DR: OMAPS00133201 x0pleela Description: MS keeps searching networks and doesn't list available PLMNs after performing manual selection Solution : Modified the prototype of function nm_error_cops() */ #ifndef DEF_MFW_NMI_HEADER #define DEF_MFW_NMI_HEADER #define MAX_PREF_PLNM 8 #define MAX_PIN_COUNT 3 /* permit maximal entering for user */ #define MAX_PUK_COUNT 5 #define FIRST_SIM_INVAILD 1 #define SERVICE_OK 1 #define SERVICE_FAILURE 0 #define CMD_NOT_PRESENT 0 /* * Network Control Block */ typedef struct { T_MFW_EVENT emask; /* events of interest */ T_MFW_EVENT event; /* current event */ T_MFW_CB handler; T_MFW_NM_PARA para; } T_MFW_NM; EXTERN T_MFW_HND nm_install (T_MFW_HDR *w, T_MFW_HDR *h, T_MFW_NM *nm); EXTERN T_MFW_RES nm_remove (T_MFW_HDR *h); EXTERN void nm_activate (UBYTE result); #ifdef FF_2TO1_PS EXTERN void nm_mmi_parameters (T_SIM_imsi_field *imsi_field, T_SIM_pref_plmn *pref_plmn); #else EXTERN void nm_mmi_parameters (T_imsi_field *imsi_field); #endif EXTERN void nm_spn_cnf (USHORT error, T_EF_SPN *efspn); EXTERN void nm_ok_cops (void); //x0pleela 30 May, 2007 DR: OMAPS00133201 //Passing T_ACI_CME_ERR as parameter EXTERN void nm_error_cops ( T_ACI_CME_ERR err ); EXTERN void nm_req_imsi (UBYTE *imsi_id); EXTERN T_MFW nm_reg_flag_req (void); EXTERN void nm_ok_deregistration (void); EXTERN void nm_ok_pref_plmn (void); EXTERN void nm_error_pref_plmn (void); EXTERN void nm_sat_file_update (USHORT dataId); EXTERN void nm_ok_band (void); /*SPR919 - SH - added */ #endif