Home
last modified time | relevance | path

Searched refs:numbers (Results 1 – 24 of 24) sorted by relevance

/system/bt/
DEventLogTags.logtags1 # The entries in this file map a sparse set of log tag numbers to tag names.
4 # Tag numbers are decimal integers, from 0 to 2^31. (Let's leave the
7 # Tag names are one or more ASCII letters and numbers or underscores, i.e.
11 # Tag numbers and names are separated by whitespace. Blank lines and lines
/system/core/logd/
Devent.logtags1 # The entries in this file map a sparse set of log tag numbers to tag names.
4 # Tag numbers are decimal integers, from 0 to 2^31. (Let's leave the
7 # Tag names are one or more ASCII letters and numbers or underscores, i.e.
11 # Tag numbers and names are separated by whitespace. Blank lines and lines
/system/core/storaged/
DEventLogTags.logtags1 # The entries in this file map a sparse set of log tag numbers to tag names.
4 # Tag numbers are decimal integers, from 0 to 2^31. (Let's leave the
7 # Tag names are one or more ASCII letters and numbers or underscores, i.e.
11 # Tag numbers and names are separated by whitespace. Blank lines and lines
/system/core/liblog/
Devent.logtags1 # The entries in this file map a sparse set of log tag numbers to tag names.
4 # Tag numbers are decimal integers, from 0 to 2^31. (Let's leave the
7 # Tag names are one or more ASCII letters and numbers or underscores, i.e.
11 # Tag numbers and names are separated by whitespace. Blank lines and lines
Dpmsg_reader.c416 static const char numbers[] = "0123456789"; in __android_log_pmsg_file_read() local
449 cp = strpbrk(names->name, numbers); in __android_log_pmsg_file_read()
459 cp = strpbrk(r, numbers); in __android_log_pmsg_file_read()
/system/extras/brillo_config/
DAndroid.mk55 four numbers separated by dots. Example: "1.2.0.0")
76 three numbers separated by dots. Example: "1.2.0")
/system/core/logcat/
Devent.logtags1 # The entries in this file map a sparse set of log tag numbers to tag names.
4 # Tag numbers are decimal integers, from 0 to 2^31. (Let's leave the
7 # Tag names are one or more ASCII letters and numbers or underscores, i.e.
11 # Tag numbers and names are separated by whitespace. Blank lines and lines
/system/sepolicy/public/
Dfsck_untrusted.te21 # device, comparing the major and minor numbers to the filesystem
Dfsck.te26 # device, comparing the major and minor numbers to the filesystem
/system/sepolicy/prebuilts/api/27.0/public/
Dfsck_untrusted.te21 # device, comparing the major and minor numbers to the filesystem
Dfsck.te26 # device, comparing the major and minor numbers to the filesystem
/system/sepolicy/prebuilts/api/28.0/public/
Dfsck_untrusted.te21 # device, comparing the major and minor numbers to the filesystem
Dfsck.te26 # device, comparing the major and minor numbers to the filesystem
/system/sepolicy/prebuilts/api/26.0/public/
Dfsck_untrusted.te21 # device, comparing the major and minor numbers to the filesystem
Dfsck.te26 # device, comparing the major and minor numbers to the filesystem
/system/timezone/
DREADME.android90 - Major format version numbers are mutually incompatible. e.g. v2 is not
92 - Minor format version numbers are backwards compatible. e.g. a v2.2 distro
/system/netd/server/dns/
DREADME.md68 `DnsTlsDispatcher` accepts queries that have colliding ID numbers and still sends them on
74 ID number of an outstanding query. This means that ID numbers are initially sequential
/system/core/adb/
DSERVICES.TXT91 Note that emulator serial numbers are of the form "emulator-5554"
Dprotocol.txt239 ID numbers such that only one stream may be connected to a bootloader
/system/tools/hidl/test/hidl_test/
Dhidl_test_client.cpp1675 .numbers = std::array<double, 10>{ {1, 2, 3, 4, 5, 6, 7, 8, 9, 10} }, in TEST_F()
1683 .numbers = std::array<double, 10>{ {1, 2, 3, 4, 5, 6, 7, 8, 9, 10} }, in TEST_F()
1691 .numbers = std::array<double, 10>{ {1, 2, 3, 4, 5, 6, 7, 8, 9, 10} }, in TEST_F()
/system/tpm/trunks/generator/
Draw_structures_fixed.txt1964 When a field has more than one bit, the range is indicated by a pair of numbers separated by a colo…
1965 The numbers will be in high:low order.
2020 expressions. A range of numbers may be indicated by separating two expressions with a colon (“:”). …
7323 PCR – consecutive numbers, starting at 0, that reference the PCR
7868 The bit numbers for an attribute structure are assigned with the number 0 assigned to the least-sig…
17365 The values listed in Table 221 are defined for a specific TPM implementation. The numbers in the Va…
Draw_structures.txt1964 When a field has more than one bit, the range is indicated by a pair of numbers separated by a colo…
1965 The numbers will be in high:low order.
2020 expressions. A range of numbers may be indicated by separating two expressions with a colon (“:”). …
7296 PCR – consecutive numbers, starting at 0, that reference the PCR
7840 The bit numbers for an attribute structure are assigned with the number 0 assigned to the least-sig…
17383 The values listed in Table 221 are defined for a specific TPM implementation. The numbers in the Va…
Draw_commands.txt12772 firmwareVersion numbers are obfuscated when the signing key is not in the Endorsement or Platform
18276 // slot numbers and handle numbers. To handle the general case, scan for
Draw_commands_fixed.txt12783 firmwareVersion numbers are obfuscated when the signing key is not in the Endorsement or Platform
18287 // slot numbers and handle numbers. To handle the general case, scan for