FreeCalypso > hg > fc-magnetite
comparison doc/Modem-configs @ 312:e60d7a32ae2a
doc/Modem-configs: deblobbing status update
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Fri, 03 Nov 2017 21:07:17 +0000 |
parents | 1811c418461b |
children | e80e43185ca1 |
comparison
equal
deleted
inserted
replaced
311:86a89a21078f | 312:e60d7a32ae2a |
---|---|
10 libraries are used; the only components that are recompiled | 10 libraries are used; the only components that are recompiled |
11 from source are those which we got in source form with our copy | 11 from source are those which we got in source form with our copy |
12 of TCS211 from Sotovik. This config can only be built for the | 12 of TCS211 from Sotovik. This config can only be built for the |
13 fcdev3b and gtamodem targets, not for c139 or pirelli. | 13 fcdev3b and gtamodem targets, not for c139 or pirelli. |
14 | 14 |
15 l1reconst In this configuration most of L1 (GSM Layer 1) is recompiled | 15 l1reconst In this configuration the Layer1 component of the firmware |
16 from reconstructed source, although this deblobbing of L1 is | 16 (which came as a blob in our copy of TCS211) is recompiled from |
17 not 100% complete yet: for the GPRS-specific L1 modules the | 17 reconstructed source, and the same is done for the system |
18 original binary object blobs are still used. Some housekeeping | 18 initialization code in main.lib. The entire chipsetsw division |
19 pieces are also recompiled from source that had to be | 19 of the firmware (now in src/cs) is thus recompiled from source, |
20 reconstructed. This config can be built for all targets. | 20 either original or reconstructed, and the only components that |
21 are used as blobs are the G23M PS, GPF and Nucleus. This | |
22 config can be built for all targets. | |
21 | 23 |
22 hybrid This configuration is a TCS2/TCS3 hybrid. Instead of using the | 24 hybrid This configuration is a TCS2/TCS3 hybrid. Instead of using the |
23 TCS211 version of the G23M protocol stack which we got only as | 25 TCS211 version of the G23M protocol stack which we got only as |
24 binary blobs, this config uses the G23M PS version from the | 26 binary blobs, this config uses the G23M PS version from the |
25 TCS3.2/LoCosto source, backported to work with L1 and the fw | 27 TCS3.2/LoCosto source, backported to work with L1 and the fw |
26 foundation layers from TCS211. ACI also had to be replaced with | 28 foundation layers from TCS211. ACI also had to be replaced with |
27 the TCS3 version, and a special hybrid version of the cdginc | 29 the TCS3 version, and a special hybrid version of the cdginc |
28 headers had to be constructed. L1 is also deblobbed to the | 30 headers had to be constructed. L1 and the init code are also |
29 same extent as in l1reconst. Like l1reconst, this config can | 31 deblobbed as in l1reconst. Like l1reconst, this config can be |
30 be built for all targets, and it is currently the most deblobbed | 32 built for all targets, and it is currently the most deblobbed |
31 (closest to full source) Magnetite config. | 33 (closest to full source) Magnetite config: the only remaining |
34 blobs are GPF and Nucleus. | |
32 | 35 |
33 All 3 of the above configurations have CSD, fax and GPRS enabled; this | 36 All 3 of the above configurations have CSD, fax and GPRS enabled; this |
34 functionality can only be exercised on those hardware targets on which both | 37 functionality can only be exercised on those hardware targets on which both |
35 Calypso UARTs are brought out, with the MODEM UART presenting a standard ASCII | 38 Calypso UARTs are brought out, with the MODEM UART presenting a standard ASCII |
36 AT command interface including data functions, while the IrDA UART carries the | 39 AT command interface including data functions, while the IrDA UART carries the |
38 interacting with your Calypso target modem or pseudo-modem solely through | 41 interacting with your Calypso target modem or pseudo-modem solely through |
39 RVTMUX, without access to the ASCII AT command interface on the dedicated MODEM | 42 RVTMUX, without access to the ASCII AT command interface on the dedicated MODEM |
40 UART, then the data functions of the firmware are inaccessible and act as dead | 43 UART, then the data functions of the firmware are inaccessible and act as dead |
41 weight. | 44 weight. |
42 | 45 |
43 Having deblobbed all of L1 except GPRS-specific modules, we are now in a | 46 Having fully deblobbed all of L1, we are now in a position where we can build a |
44 position where we can build a hybrid config with GPRS excluded, optionally | 47 hybrid config with GPRS and/or FAX_AND_DATA excluded, but I (Mychaela) would |
45 including or excluding FAX_AND_DATA, but I (Mychaela) would like to thoroughly | 48 like to thoroughly exercise the hybrid config in its current everything-enabled |
46 exercise the hybrid config in its current everything-enabled state before making | 49 state before making further changes to it. |
47 further changes to it. | |
48 | 50 |
49 The deblobbing of L1 has been done in a very meticulous manner, ensuring that | 51 The deblobbing of L1 has been done in a very meticulous manner, ensuring that |
50 each individual reconstructed C module compiles into a strict functional | 52 each individual reconstructed C module compiles into a strict functional |
51 equivalent of the original binary blob, sometimes even matching bit for bit - | 53 equivalent of the original binary blob, sometimes even matching bit for bit - |
52 thus no regressions are expected with the classic->l1reconst transition, and no | 54 thus no regressions are expected with the classic->l1reconst transition, and no |