| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
* These (qcom specifically) are now needed sooner than we had
previously been importing them. Include them within their
<platform>_target.mk makefiles. This ensures they'll be
imported before their macros are needed.
Change-Id: I06c6ab66446e2f0b54c245cf6c2cf665b649e0c9
|
|
|
|
|
|
|
|
|
|
| |
Currently, in the media HAL, we're replacing the usage
of this variable with a check for TARGET_BOARD_PLATFORM.
Instead of having to do that every time a new branch is made,
define the variable in qcom_target.
Change-Id: Idd85b6f0b167bbc64833eb03335abcaa7b9de4a9
|
|
|
|
| |
Change-Id: I97f812412f94a0638e78eaf7e45112b6924120a9
|
|
|
|
|
|
|
|
|
| |
* This code was introduced to support building from Qualcomm hardware
manifests, placing the appropriate Qualcomm HALs at the AOSP
hardware/qcom/$(HAL_TYPE) location. This isn't a supported use case
anymore, so remove the dead code.
Change-Id: Id7d53b33f53289bc1ead8eb983d7e252940b0387
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. The Sony kernel is no longer BF64-based.
2. There is no reason for Sony devices to set
the BOARD_USES_QCOM_HARDWARE flag, since they
are meant to be using AOSP code + select patches.
Revert for now until a better solution is decided upon.
This reverts commit be202afa17314f84ce69ee33a6936ca9abbf499b.
Change-Id: I94749d116340e9eb4a2fcc88a2b4514719e2279d
|
|
|
|
|
|
|
| |
Newer QCOM HALs use this flag for libc2dcolorconvert,
examples being msm8937 and msm8996 media HALs.
Change-Id: I28e8a42b58b4f5f71126df7ad97c377724da5bab
|
|
|
|
|
| |
Change-Id: I87db6ee43059c256d338babbdfe414030a06b53e
Signed-off-by: Caio Oliveira <caiooliveirafarias0@gmail.com>
|
|
|
|
| |
Change-Id: I84b1807e88d5be1230eab64bd1275a0677ce510f
|
|
|
|
| |
Change-Id: I81971e65a7f75ad5755bfdbed229c30d447c7d55
|
|
|
|
| |
Change-Id: Icbeaa995047289b5e10cdebf805f8bd8cb7978b1
|
|
|
|
| |
Change-Id: Ib0efba23e20ff156c032fe0ad428c5fa08b15f8d
|
|
|
|
|
|
|
|
|
|
| |
* There are many supported devices with common trees,
and they may wish to put their hals there.
* Allow setting the path to the hal by using
DEVICE_SPECIFIC_<component>_PATH when
USE_DEVICE_SPECIFIC_<component> is true.
Change-Id: I1335d322cd43440b028b51cff6023dd05e1d1024
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Set vendor/qcom/opensource/dataservices as the default dataservices
provider.
* Devices can override this choice by setting
USE_DEVICE_SPECIFIC_DATASERVICES and providing dataservices in the
$(TARGET_DEVICE_DIR)/dataservices directory.
* Set $(TARGET_DEVICE_DIR)/dataservices as the default dataservices
provider for non-QC hardware (Nexus devices).
Change-Id: Ie003110d7b745367947b4b728bc83800c0351068
|
|
|
|
|
|
| |
* The actual key for camera, gps, loc-api is qcom-$(name), not $(NAME).
Change-Id: Id0f2ed760cae3b5627983ef5a2206775bc880637
|
|
|
|
|
|
|
| |
Sony's msm8226 and msm8974 devices use HALs that match the 3.10 kernel
they use. Select a custom variant here.
Change-Id: Iecfb6bdf0e989ba5231bce6e650b6926417f7f90
|
|
|
|
|
|
|
|
|
| |
* Disable QC AV enhancements across the board. It brings no value
for CyanogenMod now. We are unable and unwilling to make this
shit work for commercial products- for aftermarket it would
be a complete waste of time to even try.
Change-Id: Id6f0086c107c24178410e726738e666341fdbfe1
|
|
|
|
| |
Change-Id: I83cf184f56e1293f6abaaac7849505260499c9af
|
|
|
|
|
|
|
| |
* QCOM variant HALs are pretty much deprecated, long live
device-specific HALs!
Change-Id: I636d1e851519aba31ea3744b369aea06d6db6f68
|
|
|
|
| |
Change-Id: Ie3c433420504f0f14783f99e2d5fcdd46f1a3f37
|
|
|
|
| |
Change-Id: I59616fa641c4ccddea7eb5fb77e9aeb0423ef234
|
|
|
|
|
|
|
| |
* DirectTrack/LPA/tunnel for 8960 only works with AwesomePlayer, which
has been deprecated. Don't bother allowing this to compile.
Change-Id: I4d3e6dd9f1e3047a379fd76af4f6b45d791210de
|
|
|
|
| |
Change-Id: Id99fb17044e453af050e6e3ff59cd3f5a47da268
|
|
|
|
|
|
|
|
|
| |
In the 6.0 HALs, CAF added the TARGET_COMPILE_WITH_MSM_KERNEL
which is enabled when building AOSP with an in-line kernel.
Since we only use in-line kernel builds, go ahead and enable
it across the board for all Qualcomm devices
Change-Id: I36bba34b7f1009b0776256cf0e0ce57e6c7377f4
|
|
|
|
| |
Change-Id: Ie44b9844c6d82dd73d1ea1f16b565f8bb06652c1
|
|
|
|
|
|
|
|
|
|
| |
* Allow devices to override HAL variant using QCOM_HARDWARE_VARIANT
* 8909 and 8916 share HALs by default
* 8610, 8226, 8974 share HALs by default
* 8992, 8994 share HALs by default
Change-Id: Idfbdc405a35c5ba518fc71c8b691fc177ddf9068
(cherry picked from commit 338b399a2976993f0758c2f4e61620e987f4cb19)
|
|
|
|
| |
Change-Id: I37696dae2c05c4e9f4fc824fbba63af47483ea17
|
|
|
|
| |
Change-Id: Ia5d35d916be358fb7be7ead6bd05cc3628b35a37
|
|
|
|
| |
Change-Id: Ieedce8754b145e53d72a5d6a4b41fbe5cdf6473f
|
|
|
|
| |
Change-Id: I637d94f9b0ddee2c8d6057de44355e482163dd36
|
|
|
|
| |
Change-Id: I6ead3e57899bcb007d4d284901f918a65a9e6926
|
|
|
|
| |
Change-Id: I56f0d4106f5d3d27c1ace744d30c1c81f0052bbd
|
|
|
|
| |
Change-Id: I66bca2db83260ccd65b82e540ee9f7961f00b030
|
|
|
|
|
|
|
| |
Checks in the Android.mk files do not enable the cflags for .h
files, causing a build that crashes constantly.
Change-Id: I315c760488445629fda860ba70066417c7d68b8b
|
|
|
|
| |
Change-Id: I880f32892d9e082e3ba92878414f3cb3c6f08066
|
|
|
|
| |
Change-Id: I895f1b1cbad0d260e1bca87ccb61e6194de023fd
|
|
|
|
|
|
|
|
| |
Directly map to the actual HAL directory, including the
board platform. This lets project-path-for point directly
to the respective HALs.
Change-Id: Ic4ed61bbdea9d0b5683502bf84a8410e76858527
|
|
|
|
| |
Change-Id: Ibf9dd35272521109fea52e46bacf6e1e3074ed6a
|
|
|
|
|
|
|
|
| |
* Device platform should determing the HAL that ought to be used. This
commit forces QCOM_HARDWARE to select the -caf HAL variants, which
are then broken down by platform within the variant path.
Change-Id: I6fc7a3def7b93112f034a3b89552f302727cdbf8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This consolidates a bunch of one-off logic scattered throughout the
code base. Usage in Android.mk files is trivial:
At top level, use e.g. "ifeq ($(call my-dir),$(QCOM_AUDIO_PATH))".
This works for all variants, including non-variants (i.e. AOSP).
Within subdirs, use e.g. hardware/qcom/audio => $(QCOM_AUDIO_PATH)
Change-Id: Iee2497ea9a7efeb4ae9e861b84c532b19da7b69d
build: Introduce project pathmap and use it for qcom variants
The project pathmap tracks the path to the top level of a project. The
following functions are provided:
* project-set-path adds an entry.
* project-set-path-variant adds a "variant" entry.
* project-path-for retrieves an entry.
To use as a guard in Android.mk:
ifeq ($(call my-dir),$(call project-path-for,projectname))
To use for include paths in Android.mk:
LOCAL_C_INCLUDES += $(call project-path-for,projectname)/...
Set project pathmap for qcom project variants.
Change-Id: I8dceca72a1ba80fc7b1830c5ab285d444f530457
build: Set QCOM variants for non-QCOM_HARDWARE defined targets
* Nexus devices and others typically do not define the QCOM_HARDWARE
flag, so the variant path should always default to the AOSP variant.
* Unconditionally set the variant to the AOSP HAL by default.
Change-Id: I714170897128f92718af266366cfcbf3136e8981
|
|
|
|
| |
Change-Id: I2281bec3afb4d80e80845718d880dc24ef7baf32
|
|
* Needed to support global DirectTract config on legacy targets
* Let's also eliminate some boilerplate
Change-Id: I736c10a5e7e1f3d1e0de9e60f29b60add276f151
|