| /freebsd/contrib/llvm-project/llvm/include/llvm/CodeGen/ |
| H A D | MIRFormatter.h | 41 /// Implement target specific printing for machine operand immediate value, so 49 /// Implement target specific parsing of immediate mnemonics. The mnemonic is 54 llvm_unreachable("target did not implement parsing MIR immediate mnemonic"); in parseImmMnemonic() 57 /// Implement target specific printing of target custom pseudo source value. 66 /// Implement target specific parsing of target custom pseudo source value. 71 "target did not implement parsing MIR custom pseudo source value"); in parseCustomPseudoSourceValue()
|
| /freebsd/sys/contrib/device-tree/Bindings/net/ |
| H A D | ethernet-controller.yaml | 287 # indicating the MAC or PHY should implement one of the delays 299 # When the PCB does not implement the delays, the MAC or PHY must. As 307 # users of the Device Tree may implement it differently, and still be 312 # to read the 'phy-mode' from Device Tree, not implement any delays, 313 # and pass the value to the PHY. The PHY will then implement delays as 315 # to implement the needed delays, replacing any setting performed by 318 # Experience to date is that all PHYs which implement RGMII also 319 # implement the ability to add or not add the needed delays. Hence 332 # ensure that the PHY does not also implement the same delay. So it
|
| /freebsd/contrib/wpa/src/eap_common/ |
| H A D | eap_eke_common.h | 21 #define EAP_EKE_DHGROUP_EKE_14 3 /* mandatory to implement */ 26 #define EAP_EKE_ENCR_AES128_CBC 1 /* mandatory to implement */ 29 #define EAP_EKE_PRF_HMAC_SHA1 1 /* mandatory to implement */ 33 #define EAP_EKE_MAC_HMAC_SHA1 1 /* mandatory to implement */
|
| /freebsd/sys/riscv/riscv/ |
| H A D | sbi.c | 329 ("SBI doesn't implement sbi_set_timer()")); in sbi_init() 331 ("SBI doesn't implement sbi_console_putchar()")); in sbi_init() 333 ("SBI doesn't implement sbi_console_getchar()")); in sbi_init() 335 ("SBI doesn't implement sbi_send_ipi()")); in sbi_init() 338 ("SBI doesn't implement sbi_remote_fence_i()")); in sbi_init() 341 ("SBI doesn't implement sbi_remote_sfence_vma()")); in sbi_init() 344 ("SBI doesn't implement sbi_remote_sfence_vma_asid()")); in sbi_init() 346 ("SBI doesn't implement a shutdown or reset extension")); in sbi_init()
|
| /freebsd/contrib/llvm-project/lldb/docs/design/ |
| H A D | overview.rst | |
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | SSL_CTX_set_tlsext_ticket_key_cb.3 | 104 The OpenSSL library uses your callback function to help implement a common TLS 215 \& your_type_t *key; /* something that you need to implement */ 221 \& key = currentkey(); /* something that you need to implement */ 225 \& * Something that you need to implement. 251 \& key = findkey(key_name); /* something that you need to implement */ 268 \& if (key\->expire < t \- RENEW_TIME) { /* RENEW_TIME: implement */
|
| H A D | OPENSSL_LH_COMPFUNC.3 | 178 \& * Implement the hash and compare functions; "stuff" can be any word. 190 \& * Implement the wrapper functions. 241 \& /* Implement a prototype\-compatible wrapper for "TYPE_cleanup" */ 257 declare/implement macros to create compatible wrappers that cast 266 \& /* Implement a prototype\-compatible wrapper for "TYPE_print" */ 369 the raw callbacks themselves) or use the macros to declare/implement
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | SSL_CTX_set_tlsext_ticket_key_cb.pod | 40 The OpenSSL library uses your callback function to help implement a common TLS 162 your_type_t *key; /* something that you need to implement */ 168 key = currentkey(); /* something that you need to implement */ 172 * Something that you need to implement. 198 key = findkey(key_name); /* something that you need to implement */ 215 if (key->expire < t - RENEW_TIME) { /* RENEW_TIME: implement */
|
| /freebsd/contrib/llvm-project/libc/src/__support/threads/ |
| H A D | thread.h | 123 // destructor. Can be used to implement public functions like 127 // Delete the |key|. Can be used to implement public functions like 134 // to implement public functions like pthread_setspecific. 140 // nullptr if |key| is invalid. Can be used to implement public functions like 196 // Platform should implement the functions below. 236 // Platforms should implement this function.
|
| /freebsd/contrib/llvm-project/llvm/lib/Target/AArch64/MCTargetDesc/ |
| H A D | AArch64TargetStreamer.h | 34 /// Callback used to implement the ldr= pseudo. 39 /// Callback used to implement the .ltorg directive. 43 /// Callback used to implement the .note.gnu.property section. 52 /// Callback used to implement the .inst directive. 55 /// Callback used to implement the .variant_pcs directive.
|
| /freebsd/contrib/llvm-project/llvm/lib/Target/AMDGPU/ |
| H A D | AMDGPUMIRFormatter.h | 31 /// Implement target specific printing for machine operand immediate value, so 38 /// Implement target specific parsing of immediate mnemonics. The mnemonic is 44 /// Implement target specific parsing of target custom pseudo source value.
|
| /freebsd/crypto/krb5/src/util/support/ |
| H A D | strerror_r.c | 38 /* Implement strerror_r in terms of strerror_s. */ 54 /* Implement strerror_r in terms of strerror (not thread-safe). */ 68 * Implement the POSIX strerror_r API in terms of the GNU strerror_r, which
|
| /freebsd/share/doc/psd/02.implement/ |
| H A D | Makefile | 1 VOLUME= psd/02.implement 2 SRCS= stubs implement
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | provider-signature.7 | 167 The signature (OSSL_OP_SIGNATURE) operation enables providers to implement 236 A signature algorithm implementation may not implement all of these functions. 284 be usable within \fIlibssl\fR for TLS connections, it \fBmust\fR implement the 292 The choice of which function set to implement depends on your use case: 294 For general\-purpose signature operations and TLS support: implement the 297 For operations on pre\-digested data only: implement the basic sign and verify 300 For signature schemes with recovery capability: additionally implement the 320 A signature algorithm must also implement some mechanism for generating, 363 These functions are suitable for providers that implement algorithms that 411 These functions are suitable for providers that implement algorithms that
|
| H A D | provider-kem.7 | 114 implement asymmetric kem algorithms and make them available to applications 158 An asymmetric kem algorithm implementation may not implement all of these 160 In order to be a consistent set of functions a provider must implement 162 It must also implement both of OSSL_FUNC_kem_encapsulate_init and 172 An asymmetric kem algorithm must also implement some mechanism for generating,
|
| H A D | provider-asym_cipher.7 | 111 implement asymmetric cipher algorithms and make them available to applications 154 An asymmetric cipher algorithm implementation may not implement all of these 156 In order to be a consistent set of functions a provider must implement 158 It must also implement both of OSSL_FUNC_asym_cipher_encrypt_init and 166 An asymmetric cipher algorithm must also implement some mechanism for generating,
|
| /freebsd/contrib/wpa/src/crypto/ |
| H A D | crypto.h | 181 * to implement this. 194 * to implement this. 213 * to implement this. 236 * to implement this. 252 * to implement this. 267 * to implement this. 278 * to implement this. 298 * to implement this. 315 * to implement this. 333 * to implement this. [all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | provider-kem.pod | 54 implement asymmetric kem algorithms and make them available to applications 94 An asymmetric kem algorithm implementation may not implement all of these 96 In order to be a consistent set of functions a provider must implement 98 It must also implement both of OSSL_FUNC_kem_encapsulate_init and 108 An asymmetric kem algorithm must also implement some mechanism for generating,
|
| H A D | provider-asym_cipher.pod | 51 implement asymmetric cipher algorithms and make them available to applications 90 An asymmetric cipher algorithm implementation may not implement all of these 92 In order to be a consistent set of functions a provider must implement 94 It must also implement both of OSSL_FUNC_asym_cipher_encrypt_init and 102 An asymmetric cipher algorithm must also implement some mechanism for generating,
|
| /freebsd/sys/cddl/dev/dtrace/arm/ |
| H A D | dtrace_isa.c | 106 printf("IMPLEMENT ME: %s\n", __func__); in dtrace_getupcstack() 112 printf("IMPLEMENT ME: %s\n", __func__); in dtrace_getustackdepth() 119 printf("IMPLEMENT ME: %s\n", __func__); in dtrace_getufpstack() 161 printf("IMPLEMENT ME: %s\n", __func__); in dtrace_getreg()
|
| /freebsd/contrib/llvm-project/clang/lib/Basic/Targets/ |
| H A D | MSP430.h | 54 // FIXME: Implement. in getTargetBuiltins() 79 // FIXME: implement in validateAsmConstraint() 96 // FIXME: implement in getBuiltinVaListKind()
|
| /freebsd/sys/dev/ow/ |
| H A D | README.txt | 9 the 1-wire bus. This means that the 1-wire bridge will implement the 14 responsibility of the client device drivers to implement.
|
| /freebsd/crypto/heimdal/ |
| H A D | ChangeLog.1998 | 116 * lib/krb5/auth_context.c (re-)implement `krb5_auth_setenctype' 207 (RSA_MD5_DES3_{verify,checksum}): implement 280 * lib/krb5/x-key.c: implement DES3_string_to_key_derived; fix a 426 * kuser/kinit.c: Implement lots a new options. 480 * lib/kadm5/init_c.c: Implement init_with_{skey,creds}*. Make use 483 * lib/kadm5/init_s.c: implement init_with_{skey,creds}* 569 * lib/gssapi/unwrap.c: Implement and use `gss_krb5_getsomekey'. 578 * lib/gssapi/8003.c: Implement `gssapi_krb5_verify_8003_checksum'. 669 * admin/ktutil.c: Implement `add' and `remove' functions. Make 672 * lib/krb5/keytab.c: Implement remove with files. Add memory [all …]
|
| /freebsd/crypto/openssh/ |
| H A D | sftp.1 | 417 Note that this is only supported by servers that implement 436 Note that this is only supported by servers that implement 457 Note that this is only supported by servers that implement 465 Note that this is only supported by servers that implement the "copy-data" 486 This command is only supported on servers that implement the 671 Note that this is only supported by servers that implement
|
| /freebsd/sys/netgraph/bluetooth/l2cap/ |
| H A D | TODO | 13 2) Understand and implement L2CAP QoS 23 4) Implement group channels (multicast)
|