Searched refs:tell (Results 1 – 25 of 28) sorted by relevance
12
| /Zephyr-Core-3.5.0/cmake/toolchain/llvm/ |
| D | clang_libgcc.cfg | 7 # better tell clang to give us the correct path to libgcc.a.
|
| /Zephyr-Core-3.5.0/include/zephyr/fs/ |
| D | fs_sys.h | 71 off_t (*tell)(struct fs_file_t *filp); member
|
| /Zephyr-Core-3.5.0/boards/posix/native_posix/ |
| D | Kconfig | 22 case the zephyr kernel and application cannot tell the difference unless they
|
| /Zephyr-Core-3.5.0/boards/posix/native_sim/ |
| D | Kconfig | 34 case the zephyr kernel and application cannot tell the difference unless they
|
| /Zephyr-Core-3.5.0/doc/build/dts/ |
| D | intro-scope-purpose.rst | 43 messages. You always can tell a generated- from a non-generated macro:
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/doc/services/storage/fcb/ |
| D | fcb.rst | 55 :c:func:`flash_area_read`. You can tell when all data from within a sector
|
| /Zephyr-Core-3.5.0/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
|
| /Zephyr-Core-3.5.0/subsys/fs/ |
| D | fs.c | 268 CHECKIF(zfp->mp->fs->tell == NULL) { in fs_tell()
272 rc = zfp->mp->fs->tell(zfp); in fs_tell()
|
| D | fat_fs.c | 506 .tell = fatfs_tell,
|
| D | littlefs_fs.c | 1005 .tell = littlefs_tell,
|
| /Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/tools/ |
| D | cavstool.py | 604 pos = hda_str.mem.tell()
621 pos = hda_str.mem.tell()
|
| /Zephyr-Core-3.5.0/doc/hardware/porting/ |
| D | shields.rst | 194 to tell the driver how a particular pin behaves, as with:
|
| /Zephyr-Core-3.5.0/scripts/ci/ |
| D | pylintrc | 50 # These tell you to use logger.warning("foo %d bar", 3) instead of e.g.
|
| /Zephyr-Core-3.5.0/subsys/fs/ext2/ |
| D | ext2_ops.c | 630 .tell = ext2_tell,
|
| /Zephyr-Core-3.5.0/boards/arm/arduino_nano_33_ble/doc/ |
| D | index.rst | 70 The `schematic`_ will tell you everything
|
| /Zephyr-Core-3.5.0/doc/develop/test/ |
| D | ztest_deprecated.rst | 240 won't be able to tell the subcases.
|
| D | ztest.rst | 388 won't be able to tell the subcases.
|
| /Zephyr-Core-3.5.0/subsys/net/lib/sockets/ |
| D | Kconfig | 104 This is mostly useful for TLS client side to tell TLS server what is
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/api/ |
| D | net_pkt.rst | 307 tell if the data will be in a contiguous area, and
|
| /Zephyr-Core-3.5.0/boards/xtensa/intel_adsp_cavs25/doc/ |
| D | intel_adsp_generic.rst | 213 an intermediate host, you may need to tell :file:`cavstool_client.py` to connect
|
| /Zephyr-Core-3.5.0/doc/develop/west/ |
| D | build-flash-debug.rst | 86 The ``build.sysbuild`` configuration option can be enabled to tell
|
| /Zephyr-Core-3.5.0/subsys/net/ip/ |
| D | Kconfig | 818 This value tell what is the size of the memory pool where each
|
| /Zephyr-Core-3.5.0/doc/develop/ |
| D | modules.rst | 1041 You can tell the build system to use this file by adding ``-C
|
12
