Home
last modified time | relevance | path

Searched refs:works (Results 26 – 50 of 187) sorted by relevance

12345678

/Zephyr-latest/boards/sifive/hifive1/support/
Dopenocd.cfg28 # `reset halt` not correctly works.
/Zephyr-latest/tests/benchmarks/sched/
DREADME.rst7 abstractions. It works very simply: a main thread creates a "partner"
/Zephyr-latest/tests/arch/arm/arm_sw_vector_relay/
DREADME.txt6 (CONFIG_SW_VECTOR_RELAY=y) works as expected. Only for
/Zephyr-latest/lib/hash/
DKconfig.hash_func37 This is the naive identity hash function. It only works for strings
/Zephyr-latest/cmake/compiler/xt-clang/
Dcompiler_flags.cmake35 # Remove after testing that -Wshadow works
/Zephyr-latest/doc/connectivity/networking/api/
Dsocks5.rst18 for a detailed overview of how SOCKS5 works.
Dwebsocket.rst20 for a detailed overview of how Websocket works.
/Zephyr-latest/samples/subsys/input/draw_touch_events/
DREADME.rst10 if the touch screen works for a board, examine its parameters such as inverted/swapped axes.
/Zephyr-latest/samples/boards/bbc/microbit/pong/
DREADME.rst12 The game works by controlling a paddle with the two buttons of the
/Zephyr-latest/tests/drivers/clock_control/stm32_clock_configuration/stm32_common_devices/boards/
Dl4_i2c1_hsi_lptim1_lse.overlay74 /* an extra clock at index 2 to check if switching clocks works */
Dl4_i2c1_sysclk_lptim1_lsi.overlay74 /* an extra clock at index 2 to check if switching clocks works */
/Zephyr-latest/arch/posix/
DKconfig29 support from the toolchain (currently only clang works, and
/Zephyr-latest/drivers/ethernet/
DKconfig.sam_gmac45 it is easier to verify whether the chosen hardware queue actually works.
46 This works only if there are four or fewer RX traffic classes enabled, as
/Zephyr-latest/boards/mediatek/
Dindex.rst52 environment. This process works under the control of a
57 installed works great. See the ChromiumOS developer library for more
156 document, but it works similarly, by specifying your toolchain and
/Zephyr-latest/tests/arch/arm/arm_no_multithreading/
DREADME.txt6 support (CONFIG_MULTITHREADING=n) works as expected. Only for
/Zephyr-latest/tests/drivers/disk/disk_access/
DREADME.txt8 * Setup test: Verifies that disk initialization works, as well as testing
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dread_and_decode.rst75 sample to show how this all works.
96 Handling triggers with `Read and Decode`_ works by setting up a stream I/O device
/Zephyr-latest/doc/connectivity/networking/
Dqemu_802154_setup.rst12 between them. Note that this only works in Linux host.
/Zephyr-latest/doc/develop/toolchains/
Darm_compiler.rst44 with Zephyr's linker script template, which works with GNU ld. Zephyr's
/Zephyr-latest/doc/kernel/data_structures/
Drbtree.rst57 similar APIs for the lists, works to iterate over a list in a more
113 These properties, of a balanced tree data structure that works with
114 only two pointers of data per node and that works without any need for
/Zephyr-latest/boards/intel/ehl/doc/
Dindex.rst14 This board configuration works on the variant of `EHL`_
/Zephyr-latest/arch/x86/zefi/
DREADME.txt14 This works by creating a "zephyr.efi" EFI binary containing a zephyr
58 support from the environment. But that only works for symbols that
/Zephyr-latest/boards/wiznet/w5500_evb_pico/doc/
Dindex.rst10 Pi RP2040 and fully hardwired TCP/IP controller W5500 - and basically works
104 Pi Pico, the blinky example works as intended. The W5500 is routed to the SPI0
195 configuration also works with an environment that is set up by the
/Zephyr-latest/samples/sensor/bme280/
DREADME.rst59 works on any board with a properly configured Arduino pin-compatible SPI
74 works on any board with a properly configured Arduino pin-compatible I2C
/Zephyr-latest/samples/subsys/debug/fuzz/
DREADME.rst17 Right now, the only toolchain that works with libfuzzer is a recent 64

12345678