FreeCalypso > hg > fc-magnetite
view src/cs/riviera/rv/rv_trace.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
/************************************************************************************* * * * Name rv_trace.h * * * * Function this file contains trace definitions for basic layers * * * * Date Modification * * ------------------------ * * 10/12/00 - Create Cristian Livadiotti - c-livadiotti@ti.com * * * * * * (C) Copyright 1999 by Texas Instruments Incorporated, All Rights Reserved * * * * --------------------------------------------------------------------------------- * * * * History: * * * * 10/18/2001 - Updated for R2D by Christophe Favergeon * * * *************************************************************************************/ #ifndef _RV_TRACE_H_ #define _RV_TRACE_H_ /* Define trace levels. */ #define RV_TRACE_LEVEL_ERROR (1) /* Error condition trace messages. */ /* Used when an unrecoverable error is found */ #define RV_TRACE_LEVEL_WARNING (2) /* Warning condition trace messages. */ /* Used when an error is found but is handled properly by the code*/ #define RV_TRACE_LEVEL_DEBUG_HIGH (3) /* Debug messages (high debugging). */ /* high = important debug message */ #define RV_TRACE_LEVEL_DEBUG_MEDIUM (4) /* Debug messages. */ #define RV_TRACE_LEVEL_DEBUG_LOW (5) /* Debug messages (low debugging). */ /* low = not important debug message */ /* temporary definition of this old flag for backward compatibility */ #define TRACE_RVTEST (0x001E0004) #endif /* _RV_GENERAL_H_*/