Searched refs:behind (Results 1 – 25 of 34) sorted by relevance
12
| /Zephyr-latest/lib/utils/ |
| D | winstream.c | 88 uint32_t seq0 = *seq, start, end, wseq, len, behind, copy, suffix; in sys_winstream_read() local
104 behind = wseq - *seq; in sys_winstream_read()
105 if (behind > idx_sub(ws, ws->end, ws->start)) { in sys_winstream_read()
111 copy = idx_sub(ws, ws->end, behind); in sys_winstream_read()
112 len = MIN(buflen, behind); in sys_winstream_read()
|
| /Zephyr-latest/samples/net/cloud/mqtt_azure/ |
| D | Kconfig | 44 behind proxy.
51 behind proxy.
|
| D | README.rst | 54 the sample behind a proxy:
|
| /Zephyr-latest/doc/services/crypto/ |
| D | index.rst | 8 behind the operation of the different algorithms and how they were implemented.
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | index.rst | 7 Zephyr kernel. Use the information to understand the principles behind the
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | index.rst | 7 Zephyr OS. You can use this information to understand the principles behind the
|
| /Zephyr-latest/doc/project/ |
| D | issues.rst | 14 reason behind it by following the references in the code.
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | index.rst | 19 behind this design is to allow the collections to be used in contexts
|
| /Zephyr-latest/soc/intel/intel_adsp/tools/ |
| D | cavstool.py | 685 behind = seq - last_seq
686 if behind > ((end - start) % wlen):
688 copy = (end - behind) % wlen
689 suffix = min(behind, wlen - copy)
691 if suffix < behind:
692 result += win_read(base, 16, behind - suffix)
|
| /Zephyr-latest/doc/services/portability/posix/implementation/ |
| D | index.rst | 77 implementation of that system call should be hidden behind the POSIX API.
|
| /Zephyr-latest/samples/boards/nordic/nrf53_sync_rtc/ |
| D | README.rst | 20 may be slightly behind (usually 1 tick) due to latency introduced by the
|
| /Zephyr-latest/doc/develop/west/ |
| D | built-in.rst | 138 leaving behind any branches which were already checked out. This is
143 behind some commits which are no longer referred to by any branch. These
171 does not even try to rebase and leaves your branches behind just like a
|
| D | why.rst | 18 Although the motivation behind splitting the Zephyr codebase into multiple
|
| D | troubleshooting.rst | 36 If you're behind a corporate firewall and may have proxy or other issues,
|
| /Zephyr-latest/doc/develop/test/ |
| D | bsim.rst | 188 That is, they should not leave stray files behind.
|
| /Zephyr-latest/doc/services/settings/ |
| D | index.rst | 8 provided behind a common API using FCB, NVS, or a file system. These different
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_linux.rst | 18 .. note:: If you're working behind a corporate firewall, you'll likely
|
| /Zephyr-latest/doc/build/dts/ |
| D | api-usage.rst | 18 abstracted behind a macro API, the Linux kernel would instead read the
|
| /Zephyr-latest/doc/kernel/services/ |
| D | interrupts.rst | 240 they normally would. The interrupt sharing is taken care of behind the scenes.
261 behind the scenes. All its arguments must be known at build time.
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 197 The idea behind this architecture is to organize modules or components with similar functionality
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.9.rst | 182 * Fixed link targets hidden behind header
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | chromebooks_adsp.rst | 200 hardware is all quite recent (5-6 weeks behind mainline or so). We
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 242 …* It is acceptable to gate this behind a small timeout (separate from the connection timeout) for …
|
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 81 The underlying assumptions behind this port set some limitations on what
|
| /Zephyr-latest/doc/connectivity/usb/device/ |
| D | usb_device.rst | 115 devicetree to describe CDC ACM UART. The motivation behind using devicetree
|
12
