view src/condat2/com/include/rx.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 93999a60b835
children
line wrap: on
line source

/* 
+----------------------------------------------------------------------------- 
|  Project :  GSM (6301)
|  Modul   :  
+----------------------------------------------------------------------------- 
|  Copyright 2002 Texas Instruments Berlin, AG 
|                 All rights reserved. 
| 
|                 This file is confidential and a trade secret of Texas 
|                 Instruments Berlin, AG 
|                 The receipt of or possession of this file does not convey 
|                 any rights to reproduce or disclose its contents or to 
|                 manufacture, use, or sell anything it may describe, in 
|                 whole, or in part, without the specific written consent of 
|                 Texas Instruments Berlin, AG. 
+----------------------------------------------------------------------------- 
|  Purpose :  Types definitions for the fieldstrength driver
|             .
+----------------------------------------------------------------------------- 
*/ 

#ifndef RX_H
#define RX_H

/*
 * Signal Values
 */
#define RX_QUAL_UNAVAILABLE   0xFF /* should be kept identically   */ 
                                   /* with the value defined in RR */

/*
 * Signal Types
 */
#define RX_SIGTYPE_RXLEVEL    0

/*
 * Status Type
 */
typedef struct rx_Status_Type
{
  UBYTE actLevel;
  UBYTE gsmLevel;
  UBYTE rxQuality;
} rx_Status_Type;

/*
 * Driver Control Block
 */
typedef struct rx_DCB_Type
{
  UBYTE    Steps;
} rx_DCB_Type;

#if defined (NEW_FRAME)
/*
 * to achieve backward compatibility with older definitions
 */
#define drv_SignalCB_Type           T_DRV_CB_FUNC
#define drv_SignalID_Type           T_DRV_SIGNAL
#define T_VSI_THANDLE               USHORT
#endif
/*
 * Prototypes
 */
EXTERN UBYTE rx_Init        (drv_SignalCB_Type   in_SignalCBPtr);
EXTERN void  rx_Exit        (void);
EXTERN UBYTE rx_SetConfig   (rx_DCB_Type       * in_DCBPtr);
EXTERN UBYTE rx_GetConfig   (rx_DCB_Type       * out_DCBPtr);
EXTERN UBYTE rx_GetStatus   (rx_Status_Type    * out_StatusPtr);
EXTERN void  rx_timeout     (T_VSI_THANDLE       rx_handle);
#endif