niq32.c DTR handling restored for targets that have it TI's original TCS211 fw treated GPIO 3 as the DTR input (wired so on C-Sample and D-Sample boards, also compatible with Leonardo and FCDEV3B which have a fixed pull-down resistor on this GPIO line), and the code in niq32.c called UAF_DTRInterruptHandler() (implemented in uartfax.c) from the IQ_KeypadGPIOHandler() function. But on Openmoko's GTA02 with their official fw this GPIO is a floating input, all of the DTR handling code in uartfax.c including the interrupt logic is still there, but the hobbled TCS211-20070608 semi-src delivery which OM got from TI contained a change in niq32.c (which had been kept in FC until now) that removed the call to UAF_DTRInterruptHandler() as part of those not-quite-understood "CC test" hacks. The present change fixes this bug at a long last: if we are building fw for a target that has TI's "classic" DTR & DCD GPIO arrangement (dsample, fcmodem and gtm900), we bring back all of TI's original code in both uartfax.c and niq32.c, whereas if we are building fw for a target that does not use this classic GPIO arrangement, the code in niq32.c goes back to what we got from OM and all DTR & DCD code in uartfax.c is conditioned out. This change also removes the very last remaining bit of "CC test" bogosity from our FreeCalypso code base.

build_date.c:	${LIBS}
	../helpers/build-date ${CONFIG_NAME} ${TARGET} \
		`../scripts/src-version.sh` > $@

build_date.obj:	build_date.c
	../toolwrap/cl470 -q -c -me -mt -o -pw2 -x -mw build_date.c

str2ind.obj:	str2ind.c
	../toolwrap/cl470 -q -c -me -mt -o -pw2 -x -mw str2ind.c

link.cmd:	${LINK_SCRIPT_SRC} Makefile lcfgen
	perl ../scripts/ti/make_cmd.pl lcfgen $@ 0 ${LINK_SCRIPT_SRC} \
		${SPECIAL_LINK_LIBS}

fwimage.out:	${LIBS} build_date.obj str2ind.obj link.cmd
	../toolwrap/vlnk470 -farcall -x -o $@ -m fwimage.map $^

fwimage.m0:	fwimage.out
	../toolwrap/hex470 -m -memwidth 16 -romwidth 16 $<