Searched refs:works (Results 26 – 50 of 187) sorted by relevance
12345678
/Zephyr-latest/boards/sifive/hifive1/support/ |
D | openocd.cfg | 28 # `reset halt` not correctly works.
|
/Zephyr-latest/tests/benchmarks/sched/ |
D | README.rst | 7 abstractions. It works very simply: a main thread creates a "partner"
|
/Zephyr-latest/tests/arch/arm/arm_sw_vector_relay/ |
D | README.txt | 6 (CONFIG_SW_VECTOR_RELAY=y) works as expected. Only for
|
/Zephyr-latest/lib/hash/ |
D | Kconfig.hash_func | 37 This is the naive identity hash function. It only works for strings
|
/Zephyr-latest/cmake/compiler/xt-clang/ |
D | compiler_flags.cmake | 35 # Remove after testing that -Wshadow works
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | socks5.rst | 18 for a detailed overview of how SOCKS5 works.
|
D | websocket.rst | 20 for a detailed overview of how Websocket works.
|
/Zephyr-latest/samples/subsys/input/draw_touch_events/ |
D | README.rst | 10 if the touch screen works for a board, examine its parameters such as inverted/swapped axes.
|
/Zephyr-latest/samples/boards/bbc/microbit/pong/ |
D | README.rst | 12 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/ |
D | l4_i2c1_hsi_lptim1_lse.overlay | 74 /* an extra clock at index 2 to check if switching clocks works */
|
D | l4_i2c1_sysclk_lptim1_lsi.overlay | 74 /* an extra clock at index 2 to check if switching clocks works */
|
/Zephyr-latest/arch/posix/ |
D | Kconfig | 29 support from the toolchain (currently only clang works, and
|
/Zephyr-latest/drivers/ethernet/ |
D | Kconfig.sam_gmac | 45 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/ |
D | index.rst | 52 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/ |
D | README.txt | 6 support (CONFIG_MULTITHREADING=n) works as expected. Only for
|
/Zephyr-latest/tests/drivers/disk/disk_access/ |
D | README.txt | 8 * Setup test: Verifies that disk initialization works, as well as testing
|
/Zephyr-latest/doc/hardware/peripherals/sensor/ |
D | read_and_decode.rst | 75 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/ |
D | qemu_802154_setup.rst | 12 between them. Note that this only works in Linux host.
|
/Zephyr-latest/doc/develop/toolchains/ |
D | arm_compiler.rst | 44 with Zephyr's linker script template, which works with GNU ld. Zephyr's
|
/Zephyr-latest/doc/kernel/data_structures/ |
D | rbtree.rst | 57 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/ |
D | index.rst | 14 This board configuration works on the variant of `EHL`_
|
/Zephyr-latest/arch/x86/zefi/ |
D | README.txt | 14 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/ |
D | index.rst | 10 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/ |
D | README.rst | 59 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/ |
D | README.rst | 17 Right now, the only toolchain that works with libfuzzer is a recent 64
|
12345678