Home
last modified time | relevance | path

Searched refs:compatible (Results 1 – 22 of 22) sorted by relevance

/system/libvintf/
Dmain.cpp63 bool compatible = vm->checkCompatibility(*fcm, &error); in main() local
65 << compatible; in main()
66 if (!compatible) in main()
71 bool compatible = fm->checkCompatibility(*vcm, &error); in main() local
73 << compatible; in main()
74 if (!compatible) in main()
79 bool compatible = ki->checkCompatibility(*fcm, &error); in main() local
80 std::cout << "Runtime info <==> Framework Compatibility Matrix? " << compatible; in main()
81 if (!compatible) std::cout << ", " << error; in main()
86 auto compatible = VintfObject::CheckCompatibility({}, &error); in main() local
[all …]
/system/libufdt/utils/tests/data/
Dsoc2v1.dts4 compatible = "soc_manufacturer,soc_model";
9 compatible = "deviceA_manufacturer,deviceA_model";
14 compatible = "deviceB_manufacturer,deviceB_model";
Dsoc1v1.dts4 compatible = "soc_manufacturer,soc_model";
9 compatible = "deviceA_manufacturer,deviceA_model";
Dboard1v1.dts5 compatible = "board_manufacturer,board_model";
Dboard2v1.dts5 compatible = "board_manufacturer,board_model";
Dboard1v1_1.dts5 compatible = "board_manufacturer,board_model";
/system/libufdt/tests/src/
Dextract_dtb.c80 const char *compatible = in find_and_write_dtb() local
82 printf(" compatible=%s\n", compatible ? compatible : "(unknown)"); in find_and_write_dtb()
/system/libufdt/utils/src/
Dmkdtimg_dump.c142 const char *compatible = in output_fdt_info() local
144 output_prop_str(out_fp, "(FDT)compatible", compatible ? compatible : "(unknown)"); in output_fdt_info()
/system/tools/hidl/test/vendor/1.0/
Dtypes.hal27 * It should only be used to make a backwards compatible header definition so that
/system/libufdt/utils/
DREADME.md112 compatible = "board_manufacturer,board_model";
209 (FDT)compatible = board_manufacturer,board_model
/system/bt/osi/
DAndroid.bp92 // should be compatible for a Linux host OS. We should figure out what to do for
/system/tools/hidl/
Dmain.cpp330 bool *compatible) { in isPackageJavaCompatible() argument
357 *compatible = false; in isPackageJavaCompatible()
384 *compatible = true; in isPackageJavaCompatible()
/system/chre/
DREADME.md15 CHRE is compatible with Linux as a simulator.
/system/tools/aidl/docs/
Daidl-cpp.md22 compatible (e.g. Java clients are tested to interoperate with native services).
/system/update_engine/
Dupdate_metadata.proto79 // all to be compatible with xz-embedded.
/system/chre/external/flatbuffers/include/flatbuffers/
Dflatbuffers.h75 #error A C++11 compatible compiler with support for the auto typing is \
/system/tpm/trunks/generator/
Draw_structures_fixed.txt1279 the C-compatible code that might be produced from that table by an automated process.
1713 Example 2 shows how the table would be converted into C-compatible code.
1752 // C-compatible version of the union defined in the table above
1806 shows how the table would be converted into C-compatible code and Example 3 shows how the
1830 // C-compatible version of the union structure in the table above
2468 The types are compatible with the C99 standard and should be defined in stdint.h that is provided w…
2559 this is the 1.2 compatible form of the TPM_ALG_ID
4364 The response codes use two different format groups. One group contains the TPM 1.2 compatible
5143 key fields are not compatible with the selected use
5809 TPM is compatible with a previous TPM specification and the TPM cannot determine which family of
[all …]
Draw_structures.txt1279 the C-compatible code that might be produced from that table by an automated process.
1713 Example 2 shows how the table would be converted into C-compatible code.
1752 // C-compatible version of the union defined in the table above
1806 shows how the table would be converted into C-compatible code and Example 3 shows how the
1830 // C-compatible version of the union structure in the table above
2468 The types are compatible with the C99 standard and should be defined in stdint.h that is provided w…
2559 this is the 1.2 compatible form of the TPM_ALG_ID
4370 The response codes use two different format groups. One group contains the TPM 1.2 compatible
5149 key fields are not compatible with the selected use
5815 TPM is compatible with a previous TPM specification and the TPM cannot determine which family of
[all …]
Draw_commands_fixed.txt1753 the TPM 1.2 compatible software will have a recognizable response, the TPM sets tag to
2493 start up type is not compatible with previous shutdown sequence
10902 // if the hashAlg is TPM_ALG_NULL, then the input hashAlg is not compatible
11594 // schemes are not compatible or no hash was provided and both conditions
12763 scheme is compatible with the family of the key (for example, TPM_ALG_RSAPSS cannot be selected for
12992 inScheme is not compatible with signHandle
13325 inScheme is not compatible with signHandle
13697 the scheme is not compatible with sign key type, or input scheme is
13698 not compatible with default scheme, or the chosen scheme is not a
16080 inScheme is not compatible with keyHandle; both inScheme and
[all …]
/system/media/audio_utils/
DDoxyfile1711 # browsing using Word or some other Word compatible readers that support those
DDoxyfile.orig1711 # browsing using Word or some other Word compatible readers that support those
/system/chre/chre_api/doc/
DDoxyfile1780 # browsing using Word or some other Word compatible readers that support those