/freebsd/contrib/bearssl/inc/ |
H A D | bearssl_block.h | 413 * \brief Initialisation function. 469 * \brief Initialisation function. 526 * \brief Initialisation function. 593 * \brief Initialisation function. 706 * First field is a pointer to the vtable; it is set by the initialisation 721 * First field is a pointer to the vtable; it is set by the initialisation 737 * First field is a pointer to the vtable; it is set by the initialisation 753 * First field is a pointer to the vtable; it is set by the initialisation 788 * \brief Context initialisation (key schedule) for AES CBC encryption 799 * \brief Context initialisation (key schedule) for AES CBC decryption [all …]
|
H A D | bearssl_hash.h | 260 * \brief Initialisation method. 386 * First field is a pointer to the vtable; it is set by the initialisation 402 * \brief MD5 context initialisation. 428 * provided context since the last initialisation or reset call, is 443 * number of bytes injected since the last initialisation or reset 481 * First field is a pointer to the vtable; it is set by the initialisation 497 * \brief SHA-1 context initialisation. 523 * provided context since the last initialisation or reset call, is 538 * number of bytes injected since the last initialisation or reset 576 * First field is a pointer to the vtable; it is set by the initialisation [all …]
|
H A D | bearssl_rand.h | 66 * The initialisation function sets the first context field (`vtable`) 71 * Note that the context initialisation method may accept additional 82 * The "extra parameters" pointer for context initialisation should be 143 * \brief Initialisation method. 200 * This field is set with the initialisation method/function. 216 * \brief HMAC_DRBG initialisation. 330 * This field is set with the initialisation method/function. 345 * \brief AESCTR_DRBG initialisation.
|
H A D | bearssl_hmac.h | 63 * appropriate. Context initialisation and usage incurs no dynamic 74 * \brief HMAC key context initialisation. 119 * \brief HMAC computation initialisation. 148 * initialisation `out_len` parameter was 0, then this function will
|
/freebsd/contrib/libcxxrt/ |
H A D | guard.cc | 29 * guard.cc: Functions for thread-safe static initialisation. 37 * Statics that require initialisation are protected by a 64-bit value. Any 68 * another bit to indicate that it's currently locked (initialisation in 87 * The lock is not held but is not needed because initialisation is 93 * Initialisation is not done but the lock is held by the caller. 161 // initialised, return that initialisation is done and skip further in try_lock() 225 // If we succeeded, check if initialisation has happened. In in try_lock() 233 // the lock and notify the caller that initialisation is in try_lock() 335 // indicating that initialisation is not required. in __cxa_guard_acquire() 339 // initialisation. in __cxa_guard_acquire() [all …]
|
/freebsd/share/man/man4/ |
H A D | mlx.4 | 90 .Ss Controller initialisation phase 92 .It mlx%d: controller initialisation in progress... 93 .It mlx%d: initialisation complete 95 The controller firmware is performing/has completed initialisation. 127 .It mlx%d: unknown firmware initialisation error %x:%x:%x 129 An unknown error occurred during initialisation; it will be ignored. 131 .Ss Driver initialisation/shutdown phase: 142 initialisation has failed and the driver will not attach to this
|
/freebsd/crypto/openssl/doc/man3/ |
H A D | OPENSSL_init_ssl.pod | 5 OPENSSL_init_ssl - OpenSSL (libssl and libcrypto) initialisation 22 needs so no explicit initialisation is required. Similarly it will also 25 However, there may be situations when explicit initialisation is desirable or 26 needed, for example when some nondefault initialisation is required. The 33 Therefore, in order to perform nondefault initialisation,
|
H A D | BIO_get_data.pod | 28 whether initialisation has been completed for this BIO or not. A nonzero value 29 indicates that initialisation is complete, whilst zero indicates that it is not. 30 Often initialisation will complete during initial construction of the BIO. For 31 some BIOs however, initialisation may not complete until after additional steps
|
H A D | OPENSSL_init_crypto.pod | 8 OPENSSL_thread_stop_ex, OPENSSL_thread_stop - OpenSSL initialisation 39 needs so no explicit initialisation is required. Similarly it will also 42 However, there may be situations when explicit initialisation is desirable or 43 needed, for example when some nondefault initialisation is required. The 49 Therefore, in order to perform nondefault initialisation, 107 initialisation). 205 will be added to the error stack. Note that because initialisation has failed
|
H A D | SSL_CTX_set_tlsext_ticket_key_cb.pod | 67 I<ctx> should use the initialisation vector I<iv>. The cipher context can be 184 return -1; /* error in cipher initialisation */ 192 return -1; /* error in mac initialisation */ 209 return -1; /* error in mac initialisation */ 213 return -1; /* error in cipher initialisation */
|
H A D | RAND_cleanup.pod | 21 since no explicit initialisation or de-initialisation is necessary. See
|
/freebsd/secure/lib/libcrypto/man/man3/ |
H A D | OPENSSL_init_ssl.3 | 140 OPENSSL_init_ssl \- OpenSSL (libssl and libcrypto) initialisation 157 needs so no explicit initialisation is required. Similarly it will also 160 However, there may be situations when explicit initialisation is desirable or 161 needed, for example when some nondefault initialisation is required. The 168 Therefore, in order to perform nondefault initialisation,
|
H A D | OPENSSL_init_crypto.3 | 143 OPENSSL_thread_stop_ex, OPENSSL_thread_stop \- OpenSSL initialisation 174 needs so no explicit initialisation is required. Similarly it will also 177 However, there may be situations when explicit initialisation is desirable or 178 needed, for example when some nondefault initialisation is required. The 184 Therefore, in order to perform nondefault initialisation, 233 initialisation). 319 will be added to the error stack. Note that because initialisation has failed
|
H A D | BIO_get_data.3 | 163 whether initialisation has been completed for this \s-1BIO\s0 or not. A nonzero value 164 indicates that initialisation is complete, whilst zero indicates that it is not. 165 Often initialisation will complete during initial construction of the \s-1BIO.\s0 For 166 some BIOs however, initialisation may not complete until after additional steps
|
H A D | SSL_CTX_set_tlsext_ticket_key_cb.3 | 204 \&\fIctx\fR should use the initialisation vector \fIiv\fR. The cipher context can be 310 \& return \-1; /* error in cipher initialisation */ 318 \& return \-1; /* error in mac initialisation */ 335 \& return \-1; /* error in mac initialisation */ 339 \& return \-1; /* error in cipher initialisation */
|
H A D | RAND_cleanup.3 | 158 since no explicit initialisation or de-initialisation is necessary. See
|
/freebsd/crypto/openssl/doc/internal/man3/ |
H A D | ossl_lib_ctx_get_data.pod | 51 ossl_lib_ctx_run_once is used to run some initialisation routine I<run_once_fn> 52 exactly once per library context I<ctx> object. Each initialisation routine 55 Any resources allocated via a run once initialisation routine can be cleaned up
|
/freebsd/sys/contrib/device-tree/Bindings/mfd/ |
H A D | cirrus,lochnagar.yaml | 143 Initialisation data for the VDDCORE regulator, which supplies the 161 Initialisation data for the MICVDD regulator, which supplies the 179 Initialisation data for the MIC1VDD supplies. 205 Initialisation data for the MIC2VDD supplies.
|
/freebsd/sys/contrib/xen/io/ |
H A D | xenbus.h | 32 * status of initialisation across the bus. States here imply nothing about 42 * InitWait: Finished early initialisation but waiting for information
|
/freebsd/share/examples/kld/random_adaptor/ |
H A D | random_adaptor_example.c | 67 /* Do initialisation stuff here */ in live_random_example_init() 74 /* Do de-initialisation stuff here */ in live_random_example_deinit()
|
/freebsd/contrib/ntp/html/ |
H A D | parsenew.html | 114 <li>TTY setup and initialisation/configuration will be done in ntpd/refclock_parse.c. 137 The routine to call to undo any special initialisation (free memory/timers) 192 …<p>Please include an exact description on how your clock works. (initialisation, TTY modes, string…
|
/freebsd/crypto/openssl/include/internal/ |
H A D | thread_once.h | 17 * Initialisation of global data should never happen via "RUN_ONCE" inside the 134 * function and check if that initialisation succeeded
|
/freebsd/crypto/openssl/demos/mac/ |
H A D | gmac.c | 32 * The initialisation vector (IV) is better not being hard coded too. 100 /* Set the initialisation vector (IV) */ in main()
|
/freebsd/contrib/llvm-project/compiler-rt/lib/xray/ |
H A D | xray_init.cpp | 11 // XRay initialisation logic. 126 // initialisation.
|
/freebsd/crypto/openssl/crypto/engine/ |
H A D | eng_local.h | 98 /* Once initialisation function */ 140 * loading and initialisation of any functionality required by this
|