Android-x86
Fork
Faire un don

  • R/O
  • HTTP
  • SSH
  • HTTPS

hardware-libhardware_legacy: Listed des commits

hardware/libhardware_legacy


RSS
Révision l'heure Auteur
7a7d6e6 oreo-x86 2017-04-18 16:08:50 gitbuildkicker

merge in oc-release history after reset to oc-dev

477e597 2017-04-18 05:38:11 Steven Moreland

libhardware_legacy: vendor_available

Test: build with BOARD_VNDK_VERSION := current
Change-Id: Iccc3a0301a28de52fc17102d251ce728d372ba5c

a8d0543 2017-04-18 03:10:25 TreeHugger Robot

Merge "Mark as vendor_available" into oc-dev

703e783 2017-04-15 01:42:32 Dan Willemsen

Mark as vendor_available

By setting vendor_available, the following may become true:

* a prebuilt library from this release may be used at runtime by
in a later releasse (by vendor code compiled against this release).
so this library shouldn't depend on runtime state that may change
in the future.
* this library may be loaded twice into a single process (potentially
an old version and a newer version). The symbols will be isolated
using linker namespaces, but this may break assumptions about 1
library in 1 process (your singletons will run twice).

Background:

This means that these modules may be built and installed twice --
once for the system partition and once for the vendor partition. The
system version will build just like today, and will be used by the
framework components on /system. The vendor version will build
against a reduced set of exports and libraries -- similar to, but
separate from, the NDK. This means that all your dependencies must
also mark vendor_available.

At runtime, /system binaries will load libraries from /system/lib*,
while /vendor binaries will load libraries from /vendor/lib*. There
are some exceptions in both directions -- bionic(libc,etc) and liblog
are always loaded from /system. And SP-HALs (OpenGL, etc) may load
/vendor code into /system processes, but the dependencies of those
libraries will load from /vendor until it reaches a library that's
always on /system. In the SP-HAL case, if both framework and vendor
libraries depend on a library of the same name, both versions will be
loaded, but they will be isolated from each other.

It's possible to compile differently -- reducing your source files,
exporting different include directories, etc. For details see:

https://android-review.googlesource.com/368372

None of this is enabled unless the device opts into the system/vendor
split with BOARD_VNDK_VERSION := current.

Bug: 36426473
Bug: 36079834
Bug: 37343006
Test: Android-aosp_arm.mk is the same before/after
Test: build.ninja is the same before/after
Test: build-aosp_arm.ninja is the same before/after
Test: attempt to compile with BOARD_VNDK_VERSION := current
Merged-In: I3f1e4986c5920b4a64768636cb0bc37fa602c7a7
Change-Id: I3f1e4986c5920b4a64768636cb0bc37fa602c7a7

4d4047b 2017-04-15 01:05:25 Steven Moreland

libhardware_legacy: Android.mk -> Android.bp

Test: builds with BOARD_VNDK_VERSION := current
Test: (sanity) Boots and works on internal marlin.
Bug: 33241851
Bug: 29915755
Change-Id: Ic355174a67860afa13377bc9d8f0a140f59ec34e

5c98538 2017-04-13 16:09:10 gitbuildkicker

merge in oc-release history after reset to oc-dev

24230cd 2017-04-12 03:22:37 Dan Willemsen

Include what you use

This doesn't need utils/Log.h, only log/log.h (and liblog)

Bug: 33241851
Test: m -j libpower
Merged-In: I21b08203fad51902d4a0f6172b4321b8b701ec47
Change-Id: I21b08203fad51902d4a0f6172b4321b8b701ec47

6a14d31 2017-04-06 16:08:32 gitbuildkicker

merge in oc-release history after reset to oc-dev

c99381f 2017-04-06 02:07:56 Vijay Venkatraman

Exporting headers as libhardware_legacy_headers

Bug: 33241851
Test: Build sailfish
Change-Id: I05dac45051713ac56b53b2d8fd8b01281dbe0db1
(cherry picked from commit a150372fcced9669304dc0c7e269b7fbb79cdda4)

eb92138 2017-03-23 16:08:56 gitbuildkicker

merge in oc-release history after reset to master

d29d03f 2017-03-23 13:23:24 gitbuildkicker

merge in oc-release history after reset to master

e042922 2017-03-23 09:31:07 Etan Cohen

Merge "[AWARE]: Add support to accept either passphrase or pmk" am: ad6f1d5512 am: adedd72dd1
am: 9a46e19052

Change-Id: I136dd9be16b2c187d86ab4a6b16db486f7084123

9a46e19 2017-03-23 09:29:04 Etan Cohen

Merge "[AWARE]: Add support to accept either passphrase or pmk" am: ad6f1d5512
am: adedd72dd1

Change-Id: I8e7a62ca48e6925bf39157d5459ac0d46038a100

adedd72 2017-03-23 09:26:27 Etan Cohen

Merge "[AWARE]: Add support to accept either passphrase or pmk"
am: ad6f1d5512

Change-Id: I5b4df7e827e74747dde72b658b563ab62d356e10

0a41248 2017-03-23 09:14:44 gitbuildkicker

merge in oc-release history after reset to 568e414ac5a62911664ae7498ebcc07204cc5f75

ad6f1d5 2017-03-23 09:10:34 Etan Cohen

Merge "[AWARE]: Add support to accept either passphrase or pmk"

7612aaf 2017-03-22 16:09:19 gitbuildkicker

merge in oc-release history after reset to master

e58fbf0 2017-03-22 03:08:32 Etan Cohen

Merge "[AWARE]: Fix Nan capabilities mismatch" am: 980baf1bd7 am: 41fc794eff
am: 79e9afe244

Change-Id: I1a5a77de97f8abecd182acdd64c3951d44572576

79e9afe 2017-03-22 03:04:33 Etan Cohen

Merge "[AWARE]: Fix Nan capabilities mismatch" am: 980baf1bd7
am: 41fc794eff

Change-Id: I6320d1e6a82f26d3cc60a5c80c71e2ec17aa9ce7

41fc794 2017-03-22 03:01:03 Etan Cohen

Merge "[AWARE]: Fix Nan capabilities mismatch"
am: 980baf1bd7

Change-Id: I01b2d62e40d25be61463ca93ea2153ce086a2be3

980baf1 2017-03-22 02:55:40 Etan Cohen

Merge "[AWARE]: Fix Nan capabilities mismatch"

890af55 2017-03-17 03:06:08 Subhani Shaik

[AWARE]: Fix Nan capabilities mismatch

Bug: 36357282

3686f0e 2017-03-15 06:56:09 Subhani Shaik

[AWARE]: Add support to accept either passphrase or pmk

Modify publish/subscribe/Data Initiator/Data Indication messages
to accept either PMK or Passphrase key information. Also, provide
a new parameter service name in Data Initiator request and
Data Indication response to generate PMK from passphrase and
service name for out of band requests.

Bug: 35866810
Test: TBD
Change-Id: Ibe572928e892bbd10be79dc2e09911ada348e89d

568e414 2017-03-14 10:36:19 gitbuildkicker

merge in oc-release history after reset to master

bf459ed 2017-03-14 09:18:40 gitbuildkicker

merge in oc-release history after reset to b1ac19f3800c8edb91ab2d46ee189799fd5f82db

a355559 2017-03-10 08:39:24 Etan Cohen

Merge "[AWARE]: Add range report in SDEA params" am: 1da29541bc am: eaed213c02
am: 93dea20a32

Change-Id: Ic6c22e9969c8522d40cd6fa5556e940dd6cfd34a

93dea20 2017-03-10 08:21:31 Etan Cohen

Merge "[AWARE]: Add range report in SDEA params" am: 1da29541bc
am: eaed213c02

Change-Id: Iee364e94f6a004a46d4d13e18be64bce4d39239c

eaed213 2017-03-10 08:18:30 Etan Cohen

Merge "[AWARE]: Add range report in SDEA params"
am: 1da29541bc

Change-Id: I1b882862aa737f804098e99eebd6bd58c48fe895

1da2954 2017-03-10 08:13:29 Etan Cohen

Merge "[AWARE]: Add range report in SDEA params"

8747f47 2017-03-09 04:45:29 Subhani Shaik

[AWARE]: Add range report in SDEA params

Bug: 36065933
Test: integration (sl4a) tests.
Change-Id: Ice8e87e2a6e4ed4475c7e6dcc691103071e0a03b

Afficher sur ancien navigateur de dépôt.