Searched refs:what (Results 1 – 25 of 245) sorted by relevance
12345678910
19 Why do we want this change and what problem are we trying to address?24 A brief summary of the proposed change - the 10,000 ft view on what it will31 reading this section each engineer should have a rather clear picture of what41 By reading this section, each team member should be able to know what exactly
12 A clear and concise description of what the problem is.17 A clear and concise description of what you want to happen.
23 A clear and concise description of what the bug is.45 A clear and concise description of what you expected to happen.
22 Do not touch this unless you know what you are doing.30 Do not touch this unless you know what you are doing.38 Do not touch this unless you know what you are doing.45 Do not touch this unless you know what you are doing.53 Do not touch this unless you know what you are doing.
25 you know what you are doing. Beware cc1200 requires gpio and spi to72 This value should follow what has been set in the RF settings via73 SmartRF tool. Do not touch this unless you know what you are doing.111 more information. Do not touch this unless you know what you are doing.118 more information. Do not touch this unless you know what you are doing.120 # Do no touch below settings unless you know what you are doing
19 you know what you are doing. It has to start before the net stack.
16 be bigger depending on what features are enabled.25 be bigger depending on what features are enabled.
32 WINC1500 HAL callbacks. Do not touch it unless you know what you are40 callbacks. Do not touch it unless you know what you are doing.55 Do not modify it unless you know what you are doing.
22 API support are enabled. The system will start to collect what BSD socket23 API calls are made and what parameters the API calls are using and returning.
8 * Warning: This overlay clears the msi clock back to a state equivalent to what could
8 * Warning: This overlay clears clocks back to a state equivalent to what could
16 Tells what Qemu network model to use. This value is given as
18 Tells what Qemu network model to use. This value is given as
14 # and user-configurable Kconfigs, since that's what visible to users.17 # the engineering version, because that's what the MDK/nrfx expects
23 # Don't start M4 during the M7 boot (this is what the original Opta does)
12 Choose N if you have no idea what is this.
24 toolchain and might conflict with what Zephyr uses.
15 These pages introduce bindings, describe what they do, note where they are
7 the remote device's TMAS to see what TMAP roles they support.
44 # what the ztest_thread_stack defaults to.
