FreeCalypso > hg > fc-magnetite
view src/cs/layer1/gtt_include/ctm/diag_deinterleaver.h @ 600:8f50b202e81f
board preprocessor conditionals: prep for more FC hw in the future
This change eliminates the CONFIG_TARGET_FCDEV3B preprocessor symbol and
all preprocessor conditionals throughout the code base that tested for it,
replacing them with CONFIG_TARGET_FCFAM or CONFIG_TARGET_FCMODEM. These
new symbols are specified as follows:
CONFIG_TARGET_FCFAM is intended to cover all hardware designs created by
Mother Mychaela under the FreeCalypso trademark. This family will include
modem products (repackagings of the FCDEV3B, possibly with RFFE or even
RF transceiver changes), and also my desired FreeCalypso handset product.
CONFIG_TARGET_FCMODEM is intended to cover all FreeCalypso modem products
(which will be firmware-compatible with the FCDEV3B if they use TI Rita
transceiver, or will require a different fw build if we switch to one of
Silabs Aero transceivers), but not the handset product. Right now this
CONFIG_TARGET_FCMODEM preprocessor symbol is used to conditionalize
everything dealing with MCSI.
At the present moment the future of FC hardware evolution is still unknown:
it is not known whether we will ever have any beyond-FCDEV3B hardware at all
(contingent on uncertain funding), and if we do produce further FC hardware
designs, it is not known whether they will retain the same FIC modem core
(triband), if we are going to have a quadband design that still retains the
classic Rita transceiver, or if we are going to switch to Silabs Aero II
or some other transceiver. If we produce a quadband modem that still uses
Rita, it will run exactly the same fw as the FCDEV3B thanks to the way we
define TSPACT signals for the RF_FAM=12 && CONFIG_TARGET_FCFAM combination,
and the current fcdev3b build target will be renamed to fcmodem. OTOH, if
that putative quadband modem will be Aero-based, then it will require a
different fw build target, the fcdev3b target will stay as it is, and the
two targets will both define CONFIG_TARGET_FCFAM and CONFIG_TARGET_FCMODEM,
but will have different RF_FAM numbers. But no matter which way we are
going to evolve, it is not right to have conditionals on CONFIG_TARGET_FCDEV3B
in places like ACI, and the present change clears the way for future
evolution.
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Mon, 01 Apr 2019 01:05:24 +0000 |
| parents | 945cf7f506b2 |
| children |
line wrap: on
line source
/* ******************************************************************************* * * COPYRIGHT (C) 2000 BY ERICSSON EUROLAB DEUTSCHLAND GmbH * 90411 NUERNBERG, GERMANY, Tel Int + 49 911 5217 100 * * The program(s) may be used and/or copied only with the * written permission from Ericsson or in accordance * with the terms and conditions stipulated in the agreement or * contract under which the program(s) have been supplied. * ******************************************************************************* * * File : diag_interleaver.h * Purpose : diagonal (chain) deinterleaver routine * ******************************************************************************* */ #ifndef diag_deinterleaver_h #define diag_deinterleaver_h "$Id: $" #include "l1_confg.h" /* ******************************************************************************* * INCLUDE FILES ******************************************************************************* */ #include "init_interleaver.h" /* ******************************************************************************* * DECLARATION OF PROTOTYPES ******************************************************************************* */ /* ---------------------------------------------------------------------- */ /* diag_deinterleaver: */ /* Corresponding deinterleaver to diag_interleaver. */ /* An arbitrary number of bits can be interleaved, depending of the */ /* length of the vector "in". The vector "out", which must have the same */ /* length than "in", contains the interleaved samples. */ /* All states (memory etc.) of the interleaver are stored in the variable */ /* *intl_state. Therefore, a pointer to this variable must be handled to */ /* this function. This variable initially has to be initialized by the */ /* function init_interleaver, which offers also the possibility to */ /* specify the dimensions of the deinterleaver matrix. */ /* ---------------------------------------------------------------------- */ void diag_deinterleaver(WORD16 *out, WORD16 *in, WORD16 num_valid_bits, interleaver_state_t *intl_state); /* ---------------------------------------------------------------------- */ /* shift_deinterleaver: */ /* Shift of the deinterleaver buffer by <shift> samples. */ /* shift>0 -> shift to the right */ /* shift<0 -> shift to the left */ /* The elements from <insert_bits> are inserted into the resulting space. */ /* The vector <insert_bits> must have at least abs(shift) elements. */ /* ---------------------------------------------------------------------- */ void shift_deinterleaver(WORD16 shift, WORD16 *insert_bits, interleaver_state_t *ptr_state); #if(NEW_WKA_PATCH==1) void just_shift(WORD16 shift, WORD16* in_bits, interleaver_state_t *intl_state); #endif #if (TTY_SYNC_MCU == 1) void flush_and_shift_deinterleaver(WORD16 shift,WORD16 *insert_bits,interleaver_state_t *ptr_state); #endif #if(TTY_SYNC_MCU_2==1) WORD16 flush_diag_deint(WORD16 *out, WORD16 *in, interleaver_state_t *intl_state); void zero_pad_deint(interleaver_state_t *intl_state); #endif #if(OPTIMISED==1) void new_diag_deinterleaver(WORD16 *out, WORD16 jump, WORD16 *flush_vector, WORD16 *in, WORD16 num_valid_bits, interleaver_state_t *intl_state); #endif #endif