diff doc/TIFFS-Overview @ 482:3100f534340b

doc updates for Compal FFS
author Mychaela Falconia <falcon@freecalypso.org>
date Thu, 07 Mar 2019 01:28:32 +0000
parents 579441d7dcd8
children 23f41a61ff7a
line wrap: on
line diff
--- a/doc/TIFFS-Overview	Wed Mar 06 21:12:43 2019 +0000
+++ b/doc/TIFFS-Overview	Thu Mar 07 01:28:32 2019 +0000
@@ -143,8 +143,9 @@
 
 * On Motorola/Compal C139/140 phones, the FFS used by the original proprietary
   fw occupies 5 sectors of 64 KiB each (320 KiB in total), starting at 0x370000.
-  C11x/123 use smaller FFS configurations, whereas C155/156 seem to have
-  switched to some other FFS format, different from our familiar TIFFS.
+  C11x/12x use smaller FFS configurations, whereas C155/156 use a different FFS
+  implementation with a completely different on-flash format - see the new
+  Compal-FFS article for more details.
 
 * On our own FreeCalypso hardware family we have put our FFS in the first 8
   sectors (of 256 KiB each) in the 2nd flash chip select bank, which appears at
@@ -340,18 +341,19 @@
 
 The above description refers to TI's vanilla reference version, and it seems
 like Openmoko (FIC) was the only phone/modem manufacturer (prior to us!) who
-followed it without major deviations.  In contrast, both Compal (Mot C1xx) and
-Foxconn (Pirelli DP-L10) moved their vital per-unit factory data (IMEI and RF
-calibration) out of the FFS into their own ad hoc flash data structures (which
-are very difficult to reverse-engineer and make use of, unfortunately), leaving
-their FFS only for less critical data.
+followed it without major deviations.  In contrast, both Compal (Motorola C1xx
+and Sony Ericsson J100) and Foxconn (Pirelli DP-L10) moved their vital per-unit
+factory data (IMEI and RF calibration) out of the FFS into their own ad hoc
+flash data structures (which are very difficult to reverse-engineer and make
+use of, unfortunately), leaving their FFS only for less critical data.
 
-In Compal's case (at least on the C139 model with which I have extensive
-personal experience) the FFS stores only users' personal information and nothing
-more.  One can turn the phone off, use fc-loadtool to erase the FFS sectors, and
-boot the regular fw back up; the fw will automatically do a new FFS format (it
-even displays a message on the LCD as it does so) and carry on happily as a
-"fresh" or "blank", perfectly functional and usable phone.
+In Compal's case (all C1xx models and SE J100) the FFS stores only users'
+personal information and nothing more.  One can turn the phone off, use
+fc-loadtool to erase the FFS sectors, and boot the regular fw back up; the fw
+will automatically do a new FFS format (it even displays a message on the LCD
+as it does so) and carry on happily as a "fresh" or "blank", perfectly
+functional and usable phone.  Please see the new Compal-FFS article for further
+details.
 
 In Pirelli's case, booting their official fw with blank FFS sectors will also
 result in the FFS being automatically formatted, but their fw expects some
@@ -389,7 +391,7 @@
 to run our FreeCalypso fw entirely out of RAM without flashing; the C155/156
 subfamily does have enough RAM to allow a complete FC GSM fw image to be loaded
 and run via fc-xram under some conditions (we previously supported such usage
-in our now-retired Citrine fw and may bring it back in the gcc-built config of
+in our now-retired Citrine fw and we also support it in the gcc-built config of
 FC Selenite), but there is no place in the flash where we can put our
 aftermarket FFS without overwriting some part of the original fw or its data -
 thus our general procedure for running FreeCalypso on any C1xx model is to
@@ -398,7 +400,7 @@
 aftermarket FFS in a flash area designated by us.
 
 It was already mentioned earlier that the factory RF calibration values on these
-alien phones are stored in non-TIFFS flash data structures of Mot/Compal's or
+alien phones are stored in non-TIFFS flash data structures of Compal's or
 Foxconn's invention, and our currently supported FreeCalypso firmwares
 (Magnetite and Selenite) do not contain any code for reading these alien data
 structures.  (FC Citrine could read directly from Pirelli's factory data block,
@@ -420,8 +422,8 @@
   tool, and then later in the procedure when you initialize your aftermarket FFS
   with fc-fsio, upload these extracted and format-converted RF calibration files
   as one of the several steps involved.  You will need to enter your IMEI
-  manually: we never figured out where Mot/Compal have it stored and how it is
-  obfuscated.
+  manually: we never figured out where Mot/SE/Compal have it stored and how it
+  is obfuscated.
 
 FreeCalypso host tools for TIFFS
 ================================