Searched full:how (Results 1 – 25 of 1023) sorted by relevance
12345678910>>...41
| /Zephyr-latest/doc/templates/ |
| D | sample.tmpl | 6 the sentence "This code sample shows how to ...").
19 [For simple projects, a description of how to wire the board for the demo. For
25 [ How to build the sample and how to run it. Pointers to where to find the
26 sample in the source tree and how to configure it and run it for a specific
|
| D | board.tmpl | 25 [Tables describing the board PINs and how they are configured and can be used
33 [How to use this board with Zephyr and how to flash a Zephyr binary on this
39 [ How to debug this board]
|
| /Zephyr-latest/subsys/net/lib/capture/ |
| D | Kconfig | 25 int "How many network packets to allocate for capture"
28 This tells how many net_pkt to allocate for capturing
35 int "How many network buffers to allocate for capture"
38 This tells how many net_buf to allocate for capturing
89 int "How many link types (ETH_P_*) to capture at the same time"
94 This defines how many ETH_P_* link type values can be captured
|
| /Zephyr-latest/samples/application_development/external_lib/ |
| D | README.rst | 9 A simple example that demonstrates how to include an external static library
11 The demonstrates both how to build the external library using a different build
12 system and how to include the built static library.
|
| /Zephyr-latest/subsys/net/l2/ppp/ |
| D | Kconfig | 18 How long to wait Configure-Req.
25 How many times to resend Configure-Req messages before deciding the
33 How many times to resend Terminate-Req messages before terminating
41 How many times to accept NACK loops.
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.ipv4 | 20 This tells how many network interfaces there will be in the system
133 int "How many packets to reassemble at a time"
138 How many fragmented IPv4 packets can be waiting reassembly
143 int "How many fragments can be handled to reassemble a packet"
155 int "How long to wait for fragments to be received"
160 How long to wait for IPv4 fragment to arrive before the reassembly
173 How many PMTU entries we can track for each destination address.
|
| D | Kconfig.ipv6 | 21 This tells how many network interfaces there will be in the system
59 How many PMTU entries we can track for each destination address.
85 int "How many IPv6 neighbors are supported"
101 int "How many packets to reassemble at a time"
106 How many fragmented IPv6 packets can be waiting reassembly
112 int "How many fragments can be handled to reassemble a packet"
129 int "How long to wait the fragments to receive"
134 How long to wait for IPv6 fragment to arrive before the reassembly
193 Determines how the IPv6 Interface Identifier (IID) is generated.
|
| D | Kconfig | 113 Can be used to select how the network connectivity is established
157 Network initialization priority level. This number tells how
200 command itself will print out that it is disabled and how to
351 int "How many Tx traffic classes to have for each network device"
361 Define how many Tx traffic classes (queues) the system should have
376 int "How many Rx traffic classes to have for each network device"
383 Define how many Rx traffic classes (queues) the system should have
411 prompt "How the network RX/TX threads should work"
525 int "How many routers are supported"
556 This determines how many entries can be stored in routing table.
[all …]
|
| /Zephyr-latest/doc/develop/manifest/external/ |
| D | external.rst.tmpl | 9 Short intro into the module and how it relates to Zephyr.
14 How to use this module with Zephyr. Provide all the details.
|
| /Zephyr-latest/samples/boards/nxp/mimxrt1170_evk_cm7/magic_addr/ |
| D | README.rst | 9 A sample that shows how to use RT11XX FLEXRAM Magic Addr functionality
12 on an arbitrary RAM/TCM address access. This sample shows how to use the custom
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro.rst | 8 This is a conceptual overview of devicetree and how Zephyr uses it. For
11 The following pages introduce general devicetree concepts and how they apply to
|
| D | phandles.rst | 31 Notice how the ``&nodelabel`` devicetree syntax is similar to the "address of"
135 document more rules about how to use phandle-array properties in practice.
191 You may be wondering how the "pin and flags" convention is established and
201 *Specifier spaces* are a way to allow nodes to describe how you should
204 We'll start with an abstract, high level description of how specifier spaces
206 references to further reading for how this all works in practice using DTS
278 needed to describe each kind of resource (how many cells are needed in each
284 From the above example, you're already familiar with how one specifier space
310 In this section, we explain how phandle-array properties get their specifier
346 writing bindings. For details on how to do this, see :ref:`dt-bindings-cells`.
[all …]
|
| /Zephyr-latest/samples/net/lldp/ |
| D | prj.conf | 36 # how to do this kind of setup.
74 # How often to send LLDPDUs to network (in seconds)
77 # How many traffic classes to enable
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net_config_guide.rst | 10 This document describes how various network configuration options can be
16 The network buffer configuration options control how much data we
26 How many network buffers are allocated for receiving data.
62 How many network buffers are allocated for sending data. This is similar setting
70 This option tells how many network connection endpoints are supported.
88 on how many BSD sockets are polled in the system.
92 One needs to select proper value here depending on how many BSD sockets are created in
97 internal intermediate buffer, in bytes. This sets the limit how large
139 This tells how many network interfaces there will be in the system
155 How long to wait in TCP *TIME_WAIT* state (in milliseconds).
[all …]
|
| D | net_pkt_processing_stats.rst | 10 This page describes how to get information about network packet processing
13 Network stack contains infrastructure to figure out how long the network packet
33 The TX time tells how long it took for network packet from its creation to
53 The numbers inside the brackets contain information how many microseconds it
80 * The last value tells how long it took from there to the application. Here
|
| D | network_tracing.rst | 16 It will also collect packet sending or receiving timings i.e., how long
25 See the :ref:`tracing documentation <tracing>` for how to use the tracing
|
| /Zephyr-latest/doc/contribute/ |
| D | index.rst | 26 how to ensure your contribution can be considered for inclusion in the project and potentially
41 Learn when and how to submit RFCs (Request for Comments) for new features and changes to the
62 As you write documentation, it can be helpful to see how it will look when rendered.
64 This page describes how to build the Zephyr documentation locally.
80 This page describes in more details when and how to import external source code into Zephyr.
|
| /Zephyr-latest/doc/security/standards/ |
| D | index.rst | 7 with cyber security on their own. This included how to assess the scale and impact
10 Now, governments started looking how to regulate it and several regulations
|
| /Zephyr-latest/modules/lz4/ |
| D | Kconfig | 29 prompt "How stateless compression functions allocate memory for their hash table"
53 prompt "How stateless HC compression functions allocate memory for their workspace"
86 prompt "Control how LZ4F_compressFrame() allocates the Compression State"
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.cadence_qspi_nor | 36 int "Set QSPI to read / write how many bytes per device"
42 int "Set QSPI to read / write how many bytes per block"
|
| /Zephyr-latest/drivers/misc/coresight/ |
| D | Kconfig | 36 Period (in milliseconds) how often it is checked if any dropped messages
56 Determines how often attempt to dump the data is performed.
63 there is still a pending ETR data. This option specifies how often
|
| /Zephyr-latest/samples/tfm_integration/psa_crypto/src/ |
| D | util_sformat.h | 18 * @brief Indicates how hex data should be rendered in tabular format.
33 * @param fmt Pointer to thee sf_hex_tbl_fmt struct indicating how the
|
| /Zephyr-latest/dts/bindings/input/ |
| D | gpio-qdec.yaml | 55 How many steps to count before reporting an input event.
68 How often to sample the A and B signal lines when tracking the encoder
74 How often to sample the A and B signal while idling. If unset then the
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_WINDOWS.rst | 1 # How Xtensa register windows work
47 Note that we still don't know how to detect when the register file has
57 followed by 0, 1 or 2 zero bits that tell you how "big" (how many
74 the frame bit to detect how many quads are represented by the one
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | index.rst | 20 The following sections explain how to set Kconfig configuration options, go
21 into detail on how Kconfig is used within the Zephyr project, and have some
|
12345678910>>...41
