Home
last modified time | relevance | path

Searched full:our (Results 1 – 25 of 338) sorted by relevance

12345678910>>...14

/Zephyr-latest/.github/workflows/
Dgreet_first_time_contributor.yml22 for our open-source project. ��
32 Our Continuous Integration pipeline will execute a series of checks on your Pull Request
34 …Please take a look at [our commit message guidelines](https://docs.zephyrproject.org/latest/contri…
35 …to find out how to format your commit messages, and at [our contribution workflow](https://docs.ze…
49 fantastic achievement, and we're thrilled to have you as part of our community!
/Zephyr-latest/
DCODE_OF_CONDUCT.md3 ## Our Pledge
5 We as members, contributors, and leaders pledge to make participation in our
15 ## Our Standards
17 Examples of behavior that contributes to a positive environment for our
23 * Accepting responsibility and apologizing to those affected by our mistakes,
41 Community leaders are responsible for clarifying and enforcing our standards of
55 Examples of representing our community include using an official e-mail address,
/Zephyr-latest/tests/bsim/bluetooth/host/misc/sample_test/src/
Ddut.c55 * In our case, the `testid` is set to "dut" and `entrypoint_dut()` is mapped to
58 * In our case we only have two entrypoints, as we only have a single test
113 /* Find the address of the peer. In our case, both devices are actually in entrypoint_dut()
116 * contains our device name in string form. in entrypoint_dut()
132 * attrs[0] is our service declaration in entrypoint_dut()
133 * attrs[1] is our characteristic declaration in entrypoint_dut()
134 * attrs[2] is our characteristic value in entrypoint_dut()
/Zephyr-latest/tests/bsim/bluetooth/host/misc/acl_tx_frag/src/
Ddut.c173 * attrs[0] is our service declaration in test_iteration()
174 * attrs[1] is our characteristic declaration in test_iteration()
175 * attrs[2] is our characteristic value in test_iteration()
193 LOG_DBG("Wait until peer confirms our first indication"); in test_iteration()
205 /* We will not access conn after this: give back our initial ref. */ in test_iteration()
258 /* Find the address of the peer. In our case, both devices are actually in entrypoint_dut()
261 * contains our device name in string form. in entrypoint_dut()
/Zephyr-latest/arch/xtensa/include/
Dkernel_arch_func.h81 * modified there, and our cache may be stale. in arch_cohere_stacks()
87 * uninitialized data error) so our stale cache will be in arch_cohere_stacks()
106 * our own cache, and we cannot be allowed to write them back in arch_cohere_stacks()
122 /* When in a switch, our current stack is the outbound in arch_cohere_stacks()
126 * below our SP are the calling function's spill area in arch_cohere_stacks()
/Zephyr-latest/tests/modules/thrift/ThriftTest/
Dprj.conf45 # TFDServer.cpp for our server and socketpair() for our channel. We do not
/Zephyr-latest/samples/net/sockets/http_server/
DREADME.rst146 We can use ``perf`` to collect statistics about the CPU usage of our server
153 ``perf stat`` will then start monitoring our server. We can let it run while
154 sending requests to our server. Once we've collected enough data, we can
161 functions in our code that consume the most CPU time:
167 After running our server under load (For example, using ApacheBench tool),
176 identifying the most expensive code-paths and inspect where our application is
/Zephyr-latest/samples/modules/nanopb/src/
Dmain.c28 /* Create a stream that will write to our buffer. */ in encode_message()
85 /* This is the buffer where we will store our message. */ in main()
89 /* Encode our message */ in main()
/Zephyr-latest/doc/project/
Dindex.rst37 project's goals and guidelines for our active developer community.
48 - subsystem/feature branch: is a branch within the same repository. In our case,
/Zephyr-latest/samples/subsys/fs/fs_sample/boards/
Dnrf52840dk_nrf52840_ram_disk_region.overlay21 * dts files, and replace it with our own.
50 /* Here is the reference to the memory reserved for our
/Zephyr-latest/tests/modules/nanopb/lib/
DCMakeLists.txt5 # Demonstrate that our library includes a generated header so we need the following dependency
/Zephyr-latest/samples/kernel/metairq_dispatch/src/
Dmsgdev.h30 /* "Hardware interrupts" for our fake device will arrive after a
43 /* The "messages" dispatched by our MetaIRQ thread */
/Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/boards/
Dqemu_cortex_a53.conf15 # Additionally, our test also uses malloc
/Zephyr-latest/samples/drivers/virtualization/ivshmem/doorbell/boards/
Dqemu_cortex_a53.conf15 # Additionally, our test also uses malloc
Dqemu_kvm_arm64.conf15 # Additionally, our test also uses malloc
/Zephyr-latest/modules/mbedtls/configs/
Dconfig-threadnet.h98 /* Save RAM by adjusting to our exact needs */
103 /* Save ROM and a few bytes of RAM by specifying our own ciphersuite list */
/Zephyr-latest/arch/x86/zefi/
DREADME.txt46 basically Windows DLLs. But our compiler only generates code for ELF
76 relocation of our own). Will probably never happen unless we move to
80 that the EFI environment will load our image at an address that
Dzefi.py29 # Open the ELF file up and find our entry point
113 # + UEFI can take interrupts on our stack, so no red zone
124 # Extract the .data segment and append our extra blob
134 …# FIXME: this generates warnings about our unused trash section having to be moved to make room. …
/Zephyr-latest/arch/xtensa/core/
Dgen_zsr.py63 # Next come EXCSAVE. Also record our highest non-debug interrupt level.
86 # Now emit our output header with the assignments we chose
100 # Also, our highest level EPC/EPS registers
/Zephyr-latest/tests/modules/nanopb/
DCMakeLists.txt21 # Process our own library
/Zephyr-latest/.github/
DSECURITY.md21 Please see our [Security Vulnerability
/Zephyr-latest/dts/bindings/pinctrl/
Despressif,esp32-pinctrl.yaml54 Back to our fictional application, the previous I2C_0 state definition does not
55 meet our expectations as we would like to route I2C_0's SDA signal to GPIO_33
73 one definition on that file that corresponds to our needs
/Zephyr-latest/samples/net/sockets/echo_client/
Doverlay-vlan.conf7 # selected so that our address ends to .1 and the peer one to .2
/Zephyr-latest/doc/develop/test/twister/
Dsample_blackbox_test.py45 # Set flags for our Twister command as a list of strs
65 # First, provide the args variable as our Twister command line arguments.
/Zephyr-latest/drivers/flash/
Dsoc_flash_nrf_mram.c63 /* Barrier following our last write. */ in commit_changes()
67 /* Our last operation was MRAM word-aligned, so we're done. in commit_changes()
80 * Doing this lets us finalize our changes before we exit the driver API. in commit_changes()

12345678910>>...14