view gsm-fw/cfgmagic/feature.pirhack-ffs @ 254:4eeab025b502

doc/TIFFS-old-description: the original description from SE 52 Mes 16
author Michael Spacefalcon <msokolov@ivan.Harhan.ORG>
date Sun, 02 Feb 2014 00:02:26 +0000
parents 4d706a4134b0
children 6e7410f7975c
line wrap: on
line source

# Concerning the FFS, there is one fundamental difference between the gtamodem
# and pirelli targets: whereas the content of Openmoko's modem FFS is directly
# fit for reuse by our fw (resulting from the phylogenetic proximity of the two
# firmwares), Pirelli's original FFS has the same format, but its content is so
# different that trying to reuse it would be more trouble than it is worth.
# (And Pirelli's FFS contains no IMEI or RF calibration data to boot!)
#
# Therefore, I (FC developer Michael Spacefalcon) have decided that when
# targeting the Pirelli, it would be better for us to start from our own blank
# FFS than to deal with the original.  This feature pirhack-ffs configures our
# GSM fw to put its FFS in the last 7 256 KiB sectors of the 2nd flash chip
# select: these sectors form an independent read/write bank, and are not used
# for FFS by Pirelli's fw, eliminating the possibility of accidental FFS
# cross-contamination between the two very different firmwares on the same hw.
#
# If you want to use some other sectors for FC FFS on the Pirelli, invoke
# feature pirhack-ffs first, then change CONFIG_PIRHACK_FFS_START and
# CONFIG_PIRHACK_FFS_NBLOCKS to taste.

if [ $TARGET != pirelli ]
then
	echo \
	"Error: feature pirhack-ffs is applicable only to target pirelli" 1>&2
	exit 1
fi

FFS_IN_RAM=0
CONFIG_PIRHACK_FFS=1
CONFIG_PIRHACK_FFS_START=24
CONFIG_PIRHACK_FFS_NBLOCKS=7
CONFIG_FLASH_WRITE=1
export_to_c	CONFIG_PIRHACK_FFS
export_to_c	CONFIG_PIRHACK_FFS_START
export_to_c	CONFIG_PIRHACK_FFS_NBLOCKS
export_to_c	CONFIG_FLASH_WRITE