Searched full:against (Results 1 – 25 of 255) sorted by relevance
1234567891011
11 substring matched against both BT device name and broadcast name.20 substring matched against the BT device name.
111 * @brief Validate a channel against a band.113 * @param band Band to validate the channel against.123 * @brief Validate a channel against the 2.4 GHz band.133 * @brief Validate a channel against the 5 GHz band.143 * @brief Validate a channel against the 6 GHz band.
356 *against376 *against421 * @param _addr_array Array of <tt>struct net_eth_addr</tt> items to test against438 * @param _addr_array Array of <tt>struct net_eth_addr</tt> items to test against455 * @param _addr_array Array of <tt>struct net_eth_addr</tt> items to test against472 * @param _addr_array Array of <tt>struct net_eth_addr</tt> items to test against489 * @param _addr_array Array of <tt>struct net_eth_addr</tt> items to test against507 * @param _addr_array Array of <tt>struct net_eth_addr</tt> items to test against
1 # Overlay for experimental TCP as qemu_x86 target against the sanity check
31 /* pthread_mutexattr_init() is not hardened against this */ in ZTEST()48 /* pthread_mutex_destroy() is not hardened against these */ in ZTEST()60 /* pthread_mutex_lock() is not hardened against this */ in ZTEST()73 /* pthread_mutex_lock() is not hardened against this */ in ZTEST()
7 """Check minimal libc error numbers against newlib.10 contents against the SDK's newlib errno.h. This is done to ensure that both C
13 periodically recalibrated against the HFXO.
4 Tests the i2c transfer and transfer async APIs against the fxos8700 sensor
11 # Link against zephyr
11 Expected flash device size the test will validate against. If the flash driver does not
53 (``ab``) against the server::57 ``-n`` parameter specifies the number of HTTP requests to issue against
17 - The kernel can protect against many unintentional programming errors which32 'user mode') we aim to protect against the following:96 We are specifically not protecting against the following attacks:109 - We can't protect against mistakes made in memory domain configuration done in118 - We do not protect against denial of service attacks through thread CPU
38 The controller driver may check this setting against its45 The controller driver may check this setting against its
4 Tests an i2c controller driver against a (s/f/nv)ram module doing a simple write and readback.
25 * from executing speculative prefetches against this region when
13 # configuration can only be verified against compilation errors on a single core.
73 that no locking mechanism can protect code against an NMI happening. Zephyr's78 against an NMI is the atomic layer. This also applies to callback function
49 * The data stored in the ITS is by default encrypted and authenticated (Against ``1.`` in65 In addition, the data stored in the ITS is not protected against replay attacks,69 read/write by software or debugging. (Against ``2.`` and ``10.`` in
12 # This is just a basic sanity check against errors introduced by
22 # version file so that it can be compared against in the test
34 API to store credentials with integrity check against physical
16 # DT values against the MDK, without having to conditionally include different
7 * This file validates definitions found in dt-bindings headers against their
14 * that will be linked against.
