Searched refs:tell (Results 1 – 25 of 32) sorted by relevance
12
| /Zephyr-latest/cmake/toolchain/llvm/ |
| D | clang_libgcc.cfg | 7 # better tell clang to give us the correct path to libgcc.a.
|
| /Zephyr-latest/include/zephyr/fs/ |
| D | fs_sys.h | 71 off_t (*tell)(struct fs_file_t *filp); member
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro-scope-purpose.rst | 43 messages. You always can tell a generated- from a non-generated macro:
|
| /Zephyr-latest/boards/native/native_sim/ |
| D | Kconfig | 38 case the zephyr kernel and application cannot tell the difference unless they
|
| /Zephyr-latest/cmake/sca/polyspace/ |
| D | sca.cmake | 69 # tell Polyspace about Zephyr specials
|
| /Zephyr-latest/tests/subsys/fs/fs_api/src/ |
| D | test_fs.c | 341 .tell = temp_tell,
|
| D | test_fs_dir_file.c | 720 temp_fs.tell = NULL; in test_file_seek()
|
| /Zephyr-latest/doc/services/storage/fcb/ |
| D | fcb.rst | 55 :c:func:`flash_area_read`. You can tell when all data from within a sector
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_WINDOWS.rst | 57 followed by 0, 1 or 2 zero bits that tell you how "big" (how many
65 Likewise, the processor can tell if a high register is "owned" by
|
| D | README_MMU.txt | 107 needs to tell the hardware how to find a physical address using the
|
| /Zephyr-latest/samples/subsys/usb/uac2_explicit_feedback/ |
| D | README.rst | 32 host, the device can tell host how many samples on average it needs every frame.
|
| /Zephyr-latest/subsys/fs/ |
| D | fs.c | 292 CHECKIF(zfp->mp->fs->tell == NULL) { in fs_tell()
296 rc = zfp->mp->fs->tell(zfp); in fs_tell()
|
| D | fat_fs.c | 542 .tell = fatfs_tell,
|
| D | littlefs_fs.c | 1043 .tell = littlefs_tell,
|
| /Zephyr-latest/scripts/ci/ |
| D | pylintrc | 50 # These tell you to use logger.warning("foo %d bar", 3) instead of e.g.
|
| /Zephyr-latest/modules/mbedtls/ |
| D | CMakeLists.txt | 181 # Custom macro to tell that an mbedTLSCrypto source file is being compiled.
|
| /Zephyr-latest/boards/arduino/nano_33_ble/doc/ |
| D | index.rst | 22 The `schematic`_ will tell you everything
|
| /Zephyr-latest/subsys/fs/ext2/ |
| D | ext2_ops.c | 632 .tell = ext2_tell,
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | shields.rst | 211 to tell the driver how a particular pin behaves, as with:
|
| /Zephyr-latest/soc/intel/intel_adsp/tools/ |
| D | cavstool.py | 880 pos = hda_str.mem.tell()
897 pos = hda_str.mem.tell()
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_pkt.rst | 307 tell if the data will be in a contiguous area, and
|
| /Zephyr-latest/subsys/net/lib/sockets/ |
| D | Kconfig | 148 This is mostly useful for TLS client side to tell TLS server what is
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 198 an intermediate host, you may need to tell :file:`cavstool_client.py` to connect
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 161 change should be grouped into commits that tell a clear, coherent story of the work done.
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig | 880 This value tell what is the size of the RX memory pool where each
889 This value tell what is the size of the TX memory pool where each
|
12
