Searched refs:like (Results 176 – 200 of 517) sorted by relevance
12345678910>>...21
/Zephyr-latest/dts/arc/synopsys/ |
D | emsdp.dtsi | 48 /* this is (Pseudo SRAM), so treat it like mmio-sram */
|
/Zephyr-latest/soc/mediatek/mt8xxx/ |
D | Kconfig.defconfig | 27 # level 2, underneath other hardware interrupts like timer, so it
|
/Zephyr-latest/soc/andestech/ae350/ |
D | Kconfig | 100 matching of Andes V5 PMA is like RISC-V PMP NAPOT mode
|
/Zephyr-latest/boards/panasonic/pan1783/doc/ |
D | index.rst | 22 The PAN1783A EVB essentially looks like a PAN1783 EVB, except that it is
|
/Zephyr-latest/cmake/ |
D | target_toolchain_flags.cmake | 4 # like this:
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | 8021Qav.rst | 41 The application can configure the credit-based shaper like this:
|
/Zephyr-latest/doc/services/file_system/ |
D | index.rst | 41 - ``FS_FATFS`` is the file system type like FATFS or LittleFS.
|
/Zephyr-latest/doc/develop/west/ |
D | install.rst | 40 like ``west init``, ``west update``, along with any extensions discovered
|
D | release-notes.rst | 152 using an abbreviation like ``west update --keep-d``. This is part of a change 214 itself usually appeared when running an extension command like ``west build`` 248 itself in the ``manifest: self: userdata:`` value, like so: 373 branch or a tag. In particular, "pseudo-branches" like GitHub's 442 allowed invalid schema versions, like ``0.8.2``. 468 - Commands like ``west manifest --resolve`` now correctly include group and 626 such in commands like ``west list manifest``, instead of ``west list 756 URLs directly, like so: 769 have URLs with the same final pathname component, like so: 788 instead of ``remote``, like so:
|
/Zephyr-latest/kernel/ |
D | Kconfig.mem_domain | 52 policy is managed in separate software constructions like page
|
/Zephyr-latest/samples/net/sockets/socketpair/ |
D | README.rst | 29 Build the Zephyr version of the sockets/echo application like this:
|
/Zephyr-latest/samples/net/sockets/echo/ |
D | README.rst | 28 Build the Zephyr version of the sockets/echo application like this:
|
/Zephyr-latest/samples/net/sockets/echo_async_select/ |
D | README.rst | 27 Build the Zephyr version of the sockets/echo_async application like this:
|
/Zephyr-latest/samples/sensor/sensor_shell/ |
D | README.rst | 66 undefined behavior like hardware exception. This happens because the shell
|
/Zephyr-latest/doc/kernel/services/timing/ |
D | clocks.rst | 91 * Kernel blocking operations like :c:func:`k_sem_take` or 271 In general, code like this will port just like applications code will. 278 features, like the higher precision timeout constructors or absolute 327 longer possible. For situations like this, the new API provides the 330 an uptime tick at which it will expire. So such a loop might look like:
|
/Zephyr-latest/cmake/modules/ |
D | yaml.cmake | 9 # It supports basic key-value pairs, like 12 # basic key-object pairs, like 16 # Simple value lists, like: 22 # Support for list of maps, like: 29 # All of above can be combined, for example like: 360 # single quotes and commas must be double escaped, like this: 'A \\,string'
|
/Zephyr-latest/boards/beagle/beaglev_fire/doc/ |
D | index.rst | 45 are connected properly you can press the Reset button which will show you a progress bar like: 126 …rage device. You can then then flash the image with ``dd`` or other tools like `BalenaEtcher <http…
|
/Zephyr-latest/doc/connectivity/networking/ |
D | eth_bridge_native_sim_setup.rst | 71 bridging API directly from the application. We setup the bridging using the bridge shell like 82 The network interfaces look like this in Zephyr's side:
|
/Zephyr-latest/boards/xen/xenvm/doc/ |
D | index.rst | 166 will not change some values (like RAM base address) in the future. 172 environment variable, like so:
|
/Zephyr-latest/doc/develop/languages/c/ |
D | picolibc.rst | 135 which is supposed to remain local to each thread, like 143 Picolibc uses a few internal variables for things like heap
|
/Zephyr-latest/samples/boards/nxp/adsp/number_crunching/ |
D | README.rst | 26 This sample executes some mathematical functions that can be used for audio processing like 102 For NatureDSP, the output looks like this:
|
/Zephyr-latest/doc/services/sensing/ |
D | index.rst | 127 This method is suitable for supporting some up-layer frameworks like ``CHRE``, ``HID`` which need 186 Each sensor sample value defines as a common ``header`` + ``readings[]`` data structure, like 224 For example :c:struct:`sensing_sensor_value_3d_q31` can be used by 3D IMU sensors like
|
/Zephyr-latest/boards/native/nrf_bsim/doc/ |
D | nrf52_bsim.rst | 123 For example, if you would like to run a simple case with a BLE :zephyr:code-sample:`ble_central_hr` 213 Just like with :ref:`native_sim<native_sim_debug>`, the resulting 216 native application, like for example ``gdb`` or ``valgrind``.
|
/Zephyr-latest/doc/develop/flash_debug/ |
D | nordic_segger.rst | 101 Recent versions of `ModemManager send AT commands to TTY-like devices`_; this 224 Once downloaded you can install it and configure it like so: 247 .. _ModemManager send AT commands to TTY-like devices: https://bugs.freedesktop.org/show_bug.cgi?id…
|
/Zephyr-latest/boards/shields/lcd_par_s035/boards/ |
D | rd_rw612_bga.overlay | 83 * like LVGL, which would otherwise have to swap RGB565 data in
|
12345678910>>...21