view doc/Modem-operation @ 223:740a8e8fc9d7

startup sync logic rework for the new PWON button boot scheme Previously we added logic to the MMI task to hold off PEI init until R2D is running, and then extended that condition to wait for FCHG init too. However, the dependencies of MMI upon R2D and FCHG don't start until mmiInit(), and that call is driven by Switch_ON() code, hence the wait for R2D and FCHG init can be made in that code path instead of the MMI task. Furthermore, with our new way of signaling PWON button boot to MMI, we need a new wait to ensure that the MMI task is up - previously this assurance was provided by the wait for Kp pointers to be set. Solution: revert our previous PEI init hold-off additions to MMI, add a new flag indicating MMI task init done, and put the combined wait for all needed conditions into our new PWON button boot code in power.c.
author Mychaela Falconia <falcon@freecalypso.org>
date Tue, 27 Apr 2021 06:24:52 +0000
parents a62e5bf88434
children
line wrap: on
line source

FC Tourmaline stdmodem functional configuration is equivalent to Magnetite
hybrid.  The only intentional diff from Magnetite to Tourmaline in the modem
configuration is the change of Nucleus: Magnetite uses the blob version of
Nucleus which came with TCS211-20070608, whereas Tourmaline uses the source
version of Nucleus by Comrade XVilka.  It is essentially a change from an
unknown version of Nucleus to a known one, thus it should generally be
considered an improvement - but as always with such changes, extensive
verification and testing needs to be done in order to ensure that nothing got
broken.

Aside from the one intentional change of Nucleus version, FC Tourmaline is an
entirely new firmware source tree, thus it is always possible that something
could have got broken unintentionally, particularly in rarely-tested areas of
the firmware.  Therefore, extensive testing will need to be done before we can
declare Tourmaline stdmodem as officially replacing Magnetite hybrid for stable
modem products.