Fork from pix106's tree

Kevin Tang d1cc6bfee7 GPS LOCK did not work when NMEA_PROVIDER follows it ... there is an implicit requirement on the loc_gps_cfg_s_type field data type, that is they must be 32 bit fields. Otherwise it would only work with the assistance of padding. When two adjacent 8 bit fields are defined, the later filled field would overwrite the previously written neighbor. This is why GPS_LOCK was tested as broken in the latest build. This also fixes a theoretic bug that when there are two of the same fields defined in the config table to be filled, the accounting of the filled entries was incorrect earlier. This is not a realistic bug, as there are no idential entries in the config table HAL fills. Bug: 16131208 CRs-fixed: 736966 Change-Id: I2e262fb30272f6f334508df17bb640022d7b1ef5		2014-10-20 15:00:39 -07:00
core	GPS_LOCK configuration support	2014-10-20 15:00:31 -07:00
etc	GPS_LOCK configuration support	2014-10-20 15:00:31 -07:00
loc_api	GPS LOCK did not work when NMEA_PROVIDER follows it	2014-10-20 15:00:39 -07:00
platform_lib_abstractions	hardware/qcom/gps: Enabled Timestamps for on-target logging	2013-07-03 17:09:21 -07:00
utils	GPS LOCK did not work when NMEA_PROVIDER follows it	2014-10-20 15:00:39 -07:00
CleanSpec.mk	removed exe bit of the file access mod	2013-04-05 11:12:28 -07:00
configure.ac	hardware/qcom/gps: Porting HAL and Loc API 2.0	2013-07-03 17:08:14 -07:00
loc-api.pc.in	hardware/qcom/gps: fixing build failure	2013-07-03 17:10:14 -07:00
Makefile.am	hardware/qcom/gps: Porting HAL and Loc API 2.0	2013-07-03 17:08:14 -07:00