FreeCalypso > hg > freecalypso-sw
comparison gsm-fw/cfgmagic/feature.pirhack-ffs @ 207:c70c077243dd
gsm-fw: beginning of config magic for FFS
| author | Michael Spacefalcon <msokolov@ivan.Harhan.ORG> |
|---|---|
| date | Wed, 25 Dec 2013 08:40:20 +0000 |
| parents | |
| children | 4d706a4134b0 |
comparison
equal
deleted
inserted
replaced
| 206:9539929b3414 | 207:c70c077243dd |
|---|---|
| 1 # Concerning the FFS, there is one fundamental difference between the gtamodem | |
| 2 # and pirelli targets: whereas the content of Openmoko's modem FFS is directly | |
| 3 # fit for reuse by our fw (resulting from the phylogenetic proximity of the two | |
| 4 # firmwares), Pirelli's original FFS has the same format, but its content is so | |
| 5 # different that trying to reuse it would be more trouble than it is worth. | |
| 6 # (And Pirelli's FFS contains no IMEI or RF calibration data to boot!) | |
| 7 # | |
| 8 # Therefore, I (FC developer Michael Spacefalcon) have decided that when | |
| 9 # targeting the Pirelli, it would be better for us to start from our own blank | |
| 10 # FFS than to deal with the original. This feature pirhack-ffs configures our | |
| 11 # GSM fw to put its FFS in the last 7 256 KiB sectors of the 2nd flash chip | |
| 12 # select: these sectors form an independent read/write bank, and are not used | |
| 13 # for FFS by Pirelli's fw, eliminating the possibility of accidental FFS | |
| 14 # cross-contamination between the two very different firmwares on the same hw. | |
| 15 | |
| 16 if [ $TARGET != pirelli ] | |
| 17 then | |
| 18 echo \ | |
| 19 "Error: feature pirhack-ffs is applicable only to target pirelli" 1>&2 | |
| 20 exit 1 | |
| 21 fi | |
| 22 | |
| 23 FFS_IN_RAM=0 | |
| 24 CONFIG_PIRHACK_FFS=1 | |
| 25 CONFIG_FLASH_WRITE=1 | |
| 26 export_to_c CONFIG_PIRHACK_FFS | |
| 27 export_to_c CONFIG_FLASH_WRITE |