FreeCalypso > hg > fc-magnetite
view src/ui3/mfw/mfw_bt_private.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
/*******************************************************************************\ * * * TEXAS INSTRUMENTS ISRAEL PROPRIETARY AND CONFIDENTIAL INFORMATION * * * * LEGAL NOTE: THE TRANSFER OF THE TECHNICAL INFORMATION IS BEING MADE * * UNDER AN EXPORT LICENSE ISSUED BY THE ISRAELI GOVERNMENT AND THAT THE * * APPLICABLE EXPORT LICENSE DOES NOT ALLOW THE TECHNICAL INFORMATION TO * * BE USED FOR THE MODIFICATION OF THE BT ENCRYPTION OR THE DEVELOPMENT * * OF ANY NEW ENCRYPTION. THE INFORMATION CAN BE USED FOR THE INTERNAL * * DESIGN AND MANUFACTURE OF TI PRODUCTS THAT WILL CONTAIN THE BT IC. * * * \*******************************************************************************/ /*******************************************************************************\ * * FILE NAME: mfw_bt_Private.h * * DESCRIPTION: This file defines the structures needed for BMI BT interface * that are not exposed to BT * * AUTHOR: Anandhi Ramesh * * Rev 0.1 * \*******************************************************************************/ #ifndef __MFW_BT_PRIVATE #define __MFW_BT_PRIVATE #include "mfw_fm.h" #include "mfw_bt_api.h" #define BMI_BT_NOTCONNECTED 0 #define BMI_BT_CONNECTED 1 /*---------------------------------------------------------------------------*/ /* * BMI_BT_CMD_SRCTYPE * Contains the types of commands that can occur. */ /*---------------------------------------------------------------------------*/ typedef enum { BMI_BT_COMMAND_NONE = 0, BMI_BT_HANDSET_COMMAND, BMI_BT_HEADSET_COMMAND }BMI_BT_CMD_SRCTYPE; /*---------------------------------------------------------------------------*/ /* * BMI_BT_STRUCTTYPE * Global structure that contains the following information * Connection status * State of audio - play/pause/stop etc * Source of the command - could be from headset or handset * callback function for BT */ /*---------------------------------------------------------------------------*/ typedef struct { BOOL bConnected; T_FM_AUD_STATE tAudioState; BMI_BT_CMD_SRCTYPE tCmdSrc; void (*BmiEventCallback)(BmiAvEvent); }BMI_BT_STRUCTTYPE; #endif // __MFW_BT_PRIVATE