Home
last modified time | relevance | path

Searched refs:destination (Results 1 – 25 of 28) sorted by relevance

12

/Zephyr-Core-2.7.6/tests/boards/intel_s1000_crb/main/src/
Ddma_test.c64 char *destination; member
80 .destination = rx_data,
85 .destination = rx_data2,
90 .destination = rx_data3,
95 .destination = rx_data4,
115 dst = (uint32_t)transfer_blocks[current_block_count].destination; in test_done()
/Zephyr-Core-2.7.6/cmake/util/
Dfmerge.cmake3 # Merges a list of files into a destination file.
4 # Usage: list of files as arguments, first argument is the destination file
/Zephyr-Core-2.7.6/scripts/dts/python-devicetree/tests/
Dtest.dts292 // destination to make it a bit trickier
293 gpio-map = <1 2 &{/gpio-map/destination} 5
294 3 4 &{/gpio-map/destination} 6>;
296 destination {
/Zephyr-Core-2.7.6/doc/reference/bluetooth/mesh/
Dshell.rst42 * To set the destination address, call ``mesh dst <addr>``.
51 By setting the destination address to the local unicast address (``0x0001`` in the ``mesh provision…
75destination address, using the current network and application key indexes. As the destination add…
79 With the destination address set to ``0xffff``, any other mesh nodes in the network with the config…
82 …To change the configuration of the device, the destination address must be set back to the local u…
111 …ndex>``), and optional parameters are marked with square brackets (e.g. ``[destination address]``).
158 ``mesh dst [destination address]``
161 …Get or set the message destination address. The destination address determines where mesh packets …
163 …* ``destination address``: If present, sets the new 16-bit mesh destination address. If omitted, t…
185 …Send a raw mesh message with the current destination address, network and application index. The m…
[all …]
Dheartbeat.rst49 the time. To receive a Heartbeat message, both the source and destination must
/Zephyr-Core-2.7.6/subsys/net/l2/ethernet/
DKconfig63 the source and destination IP are both set to the IP of the machine
64 issuing the packet and the destination MAC is the broadcast address
/Zephyr-Core-2.7.6/samples/bluetooth/mesh_demo/
DREADME.rst25 map nicely to displayed addresses and the list of destination addresses
/Zephyr-Core-2.7.6/samples/subsys/settings/
DREADME.rst79 loading subtree to destination provided by the caller
/Zephyr-Core-2.7.6/samples/net/capture/
DREADME.rst80 inet 198.51.100.2 netmask 255.255.255.0 destination 198.51.100.2
89 inet 203.0.113.2 netmask 255.255.255.0 destination 203.0.113.2
/Zephyr-Core-2.7.6/subsys/net/l2/
DKconfig33 Neighbor Discovery cache causing the destination link address to be
/Zephyr-Core-2.7.6/subsys/net/ip/
DKconfig.ipv444 bool "Accept 0.0.0.0 broadcast destination address"
DKconfig277 Check that either the source or destination address is
846 bool "Disable destination unreachable ICMP errors"
848 Suppress the generation of ICMP destination unreachable errors
/Zephyr-Core-2.7.6/tests/bluetooth/tester/src/
Dbttester.h1148 uint16_t destination; member
1161 uint16_t destination; member
Dmesh.c1878 pub.dst = cmd->destination; in config_hb_pub_set()
1935 sub.dst = cmd->destination; in config_hb_sub_set()
/Zephyr-Core-2.7.6/subsys/net/lib/sockets/
DKconfig176 on the information in the sockaddr_ll destination address before
/Zephyr-Core-2.7.6/doc/reference/settings/
Dindex.rst63 implementation allows for multiple source backends but only a single destination
/Zephyr-Core-2.7.6/doc/reference/data_structures/
Dring_buffers.rst151 user requests the destination location where data can be written.
/Zephyr-Core-2.7.6/doc/reference/usermode/
Dmemory_domain.rst220 which need to be placed inside a partition are tagged with their destination
Dsyscalls.rst518 as a block of memory to write to some hardware destination, this data
/Zephyr-Core-2.7.6/doc/releases/
Drelease-notes-1.14.rst1775 * :github:`12162` - net: icmpv4: Zephyr replies to ICMPv4 echo request with broadcast destination I…
1948 …0961` - net: ipv6: Zephyr replies to a packet with organization local multicast destination address
1949 * :github:`10960` - net: ipv6: Zephyr replies to a packet with site-local multicast destination add…
1950 * :github:`10959` - net: ipv6: Zephyr replies to a packet with interface-local multicast destination
1951 * :github:`10958` - net: ipv6: Zephyr replies to a packet with destination multicast with scope zero
Drelease-notes-2.7.rst1081 * Added an optional destination address filtering in the 802.15.4 L2.
1147 response destination.
1148 * Added an option to suppress ICMP destination unreachable errors.
/Zephyr-Core-2.7.6/doc/reference/kernel/threads/
Dworkqueue.rst357 incomplete delay and changing the destination queue if necessary. Use this
/Zephyr-Core-2.7.6/doc/contribute/
Dindex.rst417 https://github.com/zephyrproject-rtos/zephyr#fork-destination-box
/Zephyr-Core-2.7.6/cmake/
Dextensions.cmake1170 # Set up the paths to the destination files. These files are #included inside
1181 # Clear destination files if this is the first time the function is called.
1194 # Choose destination file, based on the <location> argument.
/Zephyr-Core-2.7.6/doc/security/
Dvulnerabilities.rst792 Improper processing of omitted source and destination addresses in

12