Searched refs:older (Results 1 – 18 of 18) sorted by relevance
| /system/tools/aidl/ |
| D | aidl_checkapi.cpp | 54 static bool CheckEquality(const AidlDefinedType& older, const AidlDefinedType& newer) { in CheckEquality() argument
56 auto older_file = older.GetLocation().GetFile(); in CheckEquality()
58 auto result = EqHelper::Compare(older_file.data(), newer_file.data(), Dump(older), Dump(newer)); in CheckEquality()
111 static bool have_compatible_annotations(const AidlAnnotatable& older, in have_compatible_annotations() argument
113 vector<string> olderAnnotations = get_strict_annotations(older); in have_compatible_annotations()
118 const string from = older.ToString().empty() ? "(empty)" : older.ToString(); in have_compatible_annotations()
126 static bool are_compatible_types(const AidlTypeSpecifier& older, const AidlTypeSpecifier& newer) { in are_compatible_types() argument
128 if (older.Signature() != newer.Signature()) { in are_compatible_types()
129 AIDL_ERROR(newer) << "Type changed: " << older.Signature() << " to " << newer.Signature() in are_compatible_types()
133 compatible &= have_compatible_annotations(older, newer); in are_compatible_types()
[all …]
|
| /system/core/debuggerd/seccomp_policy/ |
| D | crash_dump.policy.def | 55 libminijail on vendor partitions older than P does not have constants from <sys/mman.h>.
|
| /system/chre/doc/ |
| D | compatibility.md | 76 or older implementation. This is done through a combination of runtime feature
111 on an older CHRE version. This may be the case for a nanoapp developed for a
141 API minor version that is 2 or more generations older. For example, a CHRE v1.4
194 CHRE `N-1` or older, or a suitable alternative must be devised. Likewise,
206 to return false on version `N` or older.
211 `N+1` or older at load time. Likewise, the NSL can remove compatibility code for
|
| D | nanoapp_overview.md | 24 or older version of the CHRE API. These properties help provide for the maximum
|
| D | porting_guide.md | 176 PAL API, full backwards compatibility (newer CHRE framework to older PAL) is not
|
| /system/sepolicy/private/compat/30.0/ |
| D | 30.0.compat.cil | 16 ;; permission for devices (older than S) where debugfs restriction doesn't apply.
|
| /system/sepolicy/private/compat/29.0/ |
| D | 29.0.compat.cil | 15 ;; permission for devices (older than S) where debugfs restriction doesn't apply.
|
| /system/update_engine/ |
| D | README.md | 223 (especially if it's a much older version) and is securely verifiable. This
329 major version should be done with utmost care because older clients do not know
425 can correctly be applied to older devices that run older versions of the update
427 proto file might break older clients. Or passing operations that are not
428 understood in older clients will break them. Whenever changing anything in the
429 payload generation process, ask yourself this question: Would it work on older
433 to accept an older update payload. Normally this happens using a full payload,
440 * How can the change be implemented that five years from now older clients
443 * How can it make it easier for future changes without breaking older clients
|
| D | update_metadata.proto | 181 // |data_length|, older client will read them as uint32.
|
| /system/unwinding/libunwindstack/ |
| D | AndroidVersions.md | 23 and one read/executable. The libunwindstack on P and the unwinder on older
25 target API level 28 or older, make sure that `-Wl,--no-rosegment` is
|
| /system/timezone/ |
| D | README.android | 95 interpreted by older tzcode and vice versa.
142 upgrade any more as from V tzdata now ships .res files which are compatible with older ICU releases.
|
| /system/sepolicy/private/ |
| D | update_engine_common.te | 36 # the update to an older version (channel change) or incompatible version
|
| D | kernel.te | 141 # kernel older than 4.8.
|
| D | domain.te | 2071 # mlsvendorcompat is only for compatibility support for older vendor
|
| /system/update_engine/update_engine/ |
| D | update_metadata.proto | 181 // |data_length|, older client will read them as uint32.
|
| /system/core/fastboot/ |
| D | README.md | 129 variables, so older devices might exhibit this behavior,
|
| /system/timezone/input_data/android/ |
| D | countryzones.txt | 121 # In rare cases, Android may choose to continue using an older ID for the "id",
|
| /system/core/rootdir/ |
| D | init.rc | 1255 # controlling access. On older kernels, the paranoid value is the only means of
|