/system/libvintf/ |
D | main.cpp | 63 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/ |
D | soc2v1.dts | 4 compatible = "soc_manufacturer,soc_model"; 9 compatible = "deviceA_manufacturer,deviceA_model"; 14 compatible = "deviceB_manufacturer,deviceB_model";
|
D | soc1v1.dts | 4 compatible = "soc_manufacturer,soc_model"; 9 compatible = "deviceA_manufacturer,deviceA_model";
|
D | board1v1.dts | 5 compatible = "board_manufacturer,board_model";
|
D | board2v1.dts | 5 compatible = "board_manufacturer,board_model";
|
D | board1v1_1.dts | 5 compatible = "board_manufacturer,board_model";
|
/system/libufdt/tests/src/ |
D | extract_dtb.c | 80 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/ |
D | mkdtimg_dump.c | 142 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/ |
D | types.hal | 27 * It should only be used to make a backwards compatible header definition so that
|
/system/libufdt/utils/ |
D | README.md | 112 compatible = "board_manufacturer,board_model"; 209 (FDT)compatible = board_manufacturer,board_model
|
/system/bt/osi/ |
D | Android.bp | 92 // should be compatible for a Linux host OS. We should figure out what to do for
|
/system/tools/hidl/ |
D | main.cpp | 330 bool *compatible) { in isPackageJavaCompatible() argument 357 *compatible = false; in isPackageJavaCompatible() 384 *compatible = true; in isPackageJavaCompatible()
|
/system/chre/ |
D | README.md | 15 CHRE is compatible with Linux as a simulator.
|
/system/tools/aidl/docs/ |
D | aidl-cpp.md | 22 compatible (e.g. Java clients are tested to interoperate with native services).
|
/system/update_engine/ |
D | update_metadata.proto | 79 // all to be compatible with xz-embedded.
|
/system/chre/external/flatbuffers/include/flatbuffers/ |
D | flatbuffers.h | 75 #error A C++11 compatible compiler with support for the auto typing is \
|
/system/tpm/trunks/generator/ |
D | raw_structures_fixed.txt | 1279 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 …]
|
D | raw_structures.txt | 1279 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 …]
|
D | raw_commands_fixed.txt | 1753 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/ |
D | Doxyfile | 1711 # browsing using Word or some other Word compatible readers that support those
|
D | Doxyfile.orig | 1711 # browsing using Word or some other Word compatible readers that support those
|
/system/chre/chre_api/doc/ |
D | Doxyfile | 1780 # browsing using Word or some other Word compatible readers that support those
|