view src/cs/layer1/dsp1/patch_file36_10.c @ 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 d6da3c06d484
children
line wrap: on
line source

/*
 * The only DSP patch code we have for 36_10 is the dynamic download version
 * which we have extracted from the world's last surviving copy of TCS211 fw
 * for Calypso modems.  The purpose of this cheesy patch_file36_10.c wrapper
 * is to allow experimental builds with L1_DYN_DSP_DWNLD=0: we use the static
 * portion of our only available patch code, and simply not do the dynamic part.
 *
 * This configuration is intended only for experiments, not for production!
 * The dynamic parts of the DSP patch code which this configuration omits
 * are surely there for some good reason, and we can only guess what we are
 * going to destabilize by disabling them.
 */

#include "patch_file36_10_dyn_dwl.c"