FreeCalypso > hg > fc-magnetite
view src/cs/riviera/rv_template/xxx_state_i.h @ 673:62a5285e014a
Lorekeeping: allow tpudrv-leonardo.lib on Leonardo/Tango
Back in 2015 the Mother's idea was to produce a FreeCalypso development
board that would be a clone of TI Leonardo, including the original
quadband RFFE; one major additional stipulation was that this board
needed to be able to run original unmodified TCS211-20070608 firmware
with all blobs intact, with only minimal binary patches to main.lib
and tpudrv.lib. The necessary patched libs were produced at that time
in the tcs211-patches repository.
That plan was changed and we produced FCDEV3B instead, with Openmoko's
triband RFFE instead of Leonardo quadband, but when FC Magnetite started
in 2016, a TPUDRV_blob= provision was still made, allowing the possibility
of patching OM's tpudrv.lib for a restored Leonardo RFFE.
Now in 2020 we have FC Tango which is essentially a verbatim clone of
Leonardo core, including the original quadband RFFE. We have also
deblobbed our firmware so much that we have absolutely no real need
for a blob version of tpudrv.lib - but I thought it would be neat to put
the ancient TPUDRV_blob= mechanism (classic config) to its originally
intended use, just for the heck of it.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Fri, 29 May 2020 03:55:36 +0000 |
parents | 945cf7f506b2 |
children |
line wrap: on
line source
/** * @file xxx_state_i.h * * Internal definitions for XXX state machine, * i.e. the states and the functions corresponding to the states. * * The messages are declared in xxx_message.h, since they can * be seen from outside. * * @author Your name here (your_email_here) * @version 0.1 */ /* * History: * * Date Author Modification * ------------------------------------------------------------------- * // Create. * * (C) Copyright 2001 by Texas Instruments Incorporated, All Rights Reserved */ #ifndef __XXX_STATE_I_H_ #define __XXX_STATE_I_H_ #include "rv/rv_general.h" /** * XXX states. * * XXX instance is a state machine with several possible states. * Based on the current state, XXX handle different kind of messages/events. * States are listed in the order they should normally be sequenced. * * See the Readme file for a description of the state machine. */ typedef enum { XXX_STATE_1, XXX_STATE_2 } T_XXX_INTERNAL_STATE; /* * Optional but recommanded, define a function for the processing * in each state, like: * T_XXX_RETURN xxx_state_1 (T_RV_HDR * message_p); * T_XXX_RETURN xxx_state_2 (T_RV_HDR * message_p); */ #endif /* __XXX_STATE_I_H_ */