FreeCalypso > hg > fc-magnetite
view src/cs/riviera/rvm/rvm_ext_priorities.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 | 945cf7f506b2 |
| children |
line wrap: on
line source
/************************************************************************************* * * * Name rvm_ext_priorities.h * * * * Function this file priorities defintitions for basic SWEs * * It includes a file * * * * Version 0.1 * * * * Date Modification * * ------------------------------------ * * 10/11/2000 Create * * * * Author Cristian Livadiotti (c-livadiotti@ti.com) * * * * (C) Copyright 2000 by Texas Instruments Incorporated, All Rights Reserved * * * * --------------------------------------------------------------------------------- * * * * History: * * * * 10/18/2001 - Updated for R2D by Christophe Favergeon * * * *************************************************************************************/ #ifndef __RVM_EXT_PRIORITIES_H_ #define __RVM_EXT_PRIORITIES_H_ /* PRIORITIES SETTING: */ /* All user priority should be set under 250: */ /* Higher values are reserved */ /* ** External Priority definitions ** Note that RVM_EXPL_TASK_PRIORITY is used for testing purpose (refer to RTEST). ** Hence, users have to make sure that such a priority is lower than the software ** entity under test, not to starve the system. */ #define RVM_EXPL_TASK_PRIORITY (242) #define RVM_RGUI_TASK_PRIORITY (240) #define RVM_R2D_TASK_PRIORITY (239) #define RVM_DEV1_TASK_PRIORITY (245) #define RVM_DEV2_TASK_PRIORITY (245) #define RVM_DEV3_TASK_PRIORITY (245) #define RVM_UVM_TASK_PRIORITY (245) #define RVM_BTU_TASK_PRIORITY (248) /* was 240 */ #define RVM_BTUI_TASK_PRIORITY (240) #define RVM_BTA_TASK_PRIORITY (248) /* rl: was 200 */ #define RVM_BTH_TASK_PRIORITY (200) #endif /* __RVM_EXT_PRIORITIES_H_ */