FreeCalypso > hg > fc-magnetite
view src/g23m-fad/t30/cus_t30.h @ 685:3fb7384e820d
tpudrv12.h: FCDEV3B goes back to being itself
A while back we had the idea of a FreeCalypso modem family whereby our
current fcdev3b target would some day morph into fcmodem, with multiple
FC modem family products, potentially either triband or quadband, being
firmware-compatible with each other and with our original FCDEV3B. But
in light of the discovery of Tango modules that earlier idea is now being
withdrawn: instead the already existing Tango hw is being adopted into
our FreeCalypso family.
Tango cannot be firmware-compatible with triband OM/FCDEV3B targets
because the original quadband RFFE on Tango modules is wired in TI's
original Leonardo arrangement. Because this Leonardo/Tango way is now
becoming the official FreeCalypso way of driving quadband RFFEs thanks
to the adoption of Tango into our FC family, our earlier idea of
extending FIC's triband RFFE control signals with TSPACT5 no longer makes
much sense - we will probably never produce any new hardware with that
once-proposed arrangement. Therefore, that triband-or-quadband FCFAM
provision is being removed from the code base, and FCDEV3B goes back to
being treated the same way as CONFIG_TARGET_GTAMODEM for RFFE control
purposes.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Thu, 24 Sep 2020 21:03:08 +0000 (2020-09-24) |
parents | 90eb61ecd093 |
children |
line wrap: on
line source
/* +----------------------------------------------------------------------------- | Project : GSM-F&D (8411) | Modul : CUS_T30 +----------------------------------------------------------------------------- | 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 : Custom dependent definitions for the | Protocol Stack Entity | T30 +----------------------------------------------------------------------------- */ #ifndef CUS_T30_H #define CUS_T30_H /*==== CONSTANTS ==================================================*/ /* * TIMER_VALUES * * Description : The constants define the timer values * for the T30 timers * If the target system uses other units please * change the values. */ #define T1_VALUE 35000 /* ms +/- 5000 ms */ #define T2_VALUE 6000 /* ms +/- 1000 ms */ #define T4_VALUE 3000 /* ms +/- 15% */ #define DCN_VALUE 500 #define MSG_VALUE 12500 #define FRAMES_400 1846 /* * TIMER IDENTIFIER * * Description : The constants define the identifier of the * timer resources of T30. The identifier is used * to reference a timer in a config primitive */ #define T1_NAME "T1" #define T2_NAME "T2" #define T4_NAME "T4" /* * MAX_T30_TIMER * * Description : The constant define the number of timer * available in the timer pool. This should be * the amount of timer which can be active * simultaneously. */ #define MAX_T30_TIMER 3 /* * VERSION * * Description : The constants define the type and the value * of a version identification. The version * is part of the monitor struct. */ #define T_VERSION char #define VERSION_T30 "T30 2.0" /* NEW_FRAME only */ /* * VSI_CALLER * * Description : For multithread applications the constant VSI_CALLER * must be defined to identify the calling thread of the * VSI-Interface. This must be done correponding to the * type of T_VSI_CALLER in VSI.H. The comma symbol is * neccessary because the vsi-functions are called * like this vsi_t30 (VSI_CALLER par2, par3 ...) */ #ifdef OPTION_MULTITHREAD #define VSI_CALLER t30_handle, #define VSI_CALLER_SINGLE t30_handle #else #define VSI_CALLER #define VSI_CALLER_SINGLE #endif #endif