FreeCalypso > hg > fc-magnetite
view src/aci2/bmi/mmiMmi.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 | 3c2acfa1a72f |
| children |
line wrap: on
line source
#ifndef _MMIMMI_H_ #define _MMIMMI_H_ 1 /******************************************************************************* CONDAT (UK) ******************************************************************************** This software product is the property of Condat (UK) Ltd and may not be disclosed to any third party without the express permission of the owner. ******************************************************************************** $Project name: Basic MMI $Project code: BMI (6349) $Module: MMI $File: MmiMmi.h $Revision: 1.0 $Author: Condat(UK) $Date: 25/10/00 ******************************************************************************** Description: This provides the root mofule for the basic MMI ******************************************************************************** $History: MmiMmi.h 25/10/00 Original Condat(UK) BMI version. $End *******************************************************************************/ #include "MmiResources.h" //for screen size #include "mfw_win.h" //for MfwWinAttr definition /******************************************************************************* Type definitions *******************************************************************************/ typedef void ( *MmiState )( int, void( * ) ( ) ); /******************************************************************************* Definitions provided by the root module *******************************************************************************/ /* Identifier ranges for applications. These are used to isolate particular message numbers for particular applications, hence preventing a rogue message being handled incorrectly. */ #define MenuDummy 0 #define ExtrasDummy 50 #define StartDummy 100 #define IdleDummy 200 #define GlobalDummy 300 #define ServicesDummy 400 #define SoundsDummy 500 #define TimeDateDummy 600 #define PhbkDummy 700 #define OrganiserDummy 800 #define CallDummy 900 #define PinsDummy 1000 #define SatDummy 1100 #define DialogsDummy 1200 #define MsgsDummy 1300 /* Define window areas */ //The following values are incorrect - but do I fix them? #define LCD_SX SCREEN_SIZE_X #define LCD_SY SCREEN_SIZE_Y /* Define charging states */ #define GlobalDefault 0x00 #define GlobalCharging 0x01 #define GlobalBatteryPower 0x02 #define GlobalMobileOn 0x04 #define GlobalDisplayFlag 0x08 /******************************************************************************* Global data elements *******************************************************************************/ /* Root module attribute structures */ extern MfwWinAttr g_MainWin; extern MfwWinAttr g_IconWin; extern MfwWinAttr g_KeyWin; /* Display screen sizes */ extern U16 mmiScrX, mmiScrY; /* Mode for the phone */ extern UBYTE globalMobileMode; /******************************************************************************* Public Prototypes *******************************************************************************/ void mmi_main (void); /* initial entry point */ void mmiInit (void); /* init MMI */ void mmiExit (void); /* exit MMI */ /******************************************************************************* End Of File *******************************************************************************/ #endif