| /Zephyr-Core-2.7.6/doc/security/ |
| D | reporting.rst | 10 vulnerabilities@zephyrproject.org mailing list. These reports will be
12 Each vulnerability will be entered into the Zephyr Project security
13 tracking JIRA_. The original submitter will be granted permission to
24 Issues within this bug tracking system will transition through a
35 response team will analyze the issue, determine a responsible
37 issue to the Assigned state. Part of triage will be to set the
44 link will be added to a comment in the issue, and the issue moved to
52 - Public: The embargo period has ended. The issue will be made
66 Subcommittee. In the general case, this will include:
78 The guideline for embargo will be based on: 1. Severity of the issue,
[all …]
|
| /Zephyr-Core-2.7.6/subsys/net/lib/tftp/ |
| D | Kconfig | 22 int "Maximum amount of time the TFTP Client will wait for a response from the server."
25 Maximum amount of time (in msec) that the TFTP Client will wait for
27 will assume that the Server failed and close the connection.
30 int "Number of times the TFTP Client will retransmit the request to the server."
33 Once the TFTP Client sends out a request, it will wait
35 However, if it doesn't arrive within the given time we will re-transmit
36 the request to the server in hopes that the server will respond within
37 time to this request. This number dictates the number of times we will
|
| /Zephyr-Core-2.7.6/boards/posix/nrf52_bsim/ |
| D | bstests.h | 23 * Will be called with the command line arguments for the testcase.
27 /* It will be called (in the HW models thread) before the CPU is booted */
30 * It will be called (in the HW models thread) when the CPU goes to sleep
34 /* It will be called (in the HW models thread) each time the bst_timer ticks */
37 * It will be called (in the HW models thread) when the execution is being
42 * It will be called (in SW context) when a HW interrupt is raised.
43 * If it returns true, the normal interrupt handler will NOT be called and
44 * Zephyr will only see a spurious wake
50 * This function will be called (in SW context) as a Zephyr PRE_KERNEL_1
54 * will crash)
[all …]
|
| /Zephyr-Core-2.7.6/doc/ |
| D | zephyr.doxyfile.in | 9 # All text after a single hash (#) is considered a comment and will be ignored.
51 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
57 # into which the generated documentation will be written. If a relative path is
58 # entered, it will be relative to the location where doxygen was started. If
59 # left blank the current directory will be used.
63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
65 # will distribute the generated files over these directories. Enabling this
74 # documentation generated by doxygen is written. Doxygen will use this
88 # If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
95 # If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief
[all …]
|
| /Zephyr-Core-2.7.6/dts/bindings/ethernet/ |
| D | xlnx,gem.yaml | 24 frequency will be derived using two dividers in the respective GEM's
27 which it will be adjusted at run-time. Therefore, the value of this
58 PHY will be claimed by the driver, watch out in case of shared MDIO
73 the respective controller will be configured to match the link speed
75 the link speed specified here will be requested. If the optional pro-
77 speed specified here plus any valid link speed below this value will
158 When set, the hardware TX data buffer will make use of the full 4 kB
159 that are available. If unset, the hardware TX data buffer will be
203 non-standard preamble will not be rejected.
227 When set, frames with FCS/CRC errors will not be rejected. FCS error
[all …]
|
| /Zephyr-Core-2.7.6/scripts/dts/ |
| D | README.txt | 22 For now, the 'main' copy will continue to be hosted here in the zephyr
23 repository. We will mirror changes into the standalone repository as
26 Code in the zephyr repository which needs these libraries will import
27 devicetree.edtlib from now on, but the code will continue to be found
31 repository will disappear, and a standalone repository will be the
|
| /Zephyr-Core-2.7.6/include/sys/ |
| D | mem_manage.h | 33 /** Region will have read/write access (and not read-only) */
36 /** Region will be executable (normally forbidden) */
39 /** Region will be accessible to user mode (normally supervisor-only) */
54 * Note that when demand paging is active, these will only work with page
57 * TODO: This will likely need to move to an arch API or need additional
177 * for the kernel. This function will choose the virtual address
180 * Portable code should never assume that phys_addr and linear_addr will
189 * If there is insufficient virtual address space for the mapping this will
199 * and pin it at build time, it will be mapped when the system boots.
222 * This will align the input parameters to page boundaries so that
[all …]
|
| D | kobject.h | 103 * state. The permissions will be granted when the threads are initialized
130 * Calling this on an object will make it usable from userspace.
187 * The thread will be granted access to the object if the caller is from
200 * The thread will lose access to the object if the caller is from
224 * have sufficient permissions on the object, then that object will have
242 * This will instantiate at runtime a kernel object of the specified type,
243 * returning a pointer to it. The object will be returned in an uninitialized
245 * for the object will be allocated out of the calling thread's resource pool.
261 * Initialization state and thread permissions will be cleared. The
262 * returned z_object's data value will be uninitialized.
[all …]
|
| /Zephyr-Core-2.7.6/doc/reference/api/ |
| D | api_lifecycle.rst | 7 given API will not change in future releases. At the same time, developers
58 Changes will not be announced.
76 minor changes. Backwards-compatibility will be maintained if reasonable.
94 `Zephyr API meeting`_ where, barring any objections, the Pull Request will be
141 The RFC will then receive feedback through issue comments and will also be
143 large will have a chance to discuss it in detail.
149 proceed with confidence that it will be accepted.
169 Once the steps above have been completed, the outcome of the proposal will
179 Incompatible changes will be announced in the "API Changes" section of the
188 Deprecation and removal of APIs will be announced in the "API Changes"
[all …]
|
| /Zephyr-Core-2.7.6/doc/reference/networking/ |
| D | net_pkt.rst | 44 Note, however, one will rarely have to use it, as the core provides
80 awareness to buffer allocation and, as we will see later, its
99 be allocated. Indeed, the allocator will use the network interface to
102 the allocated space will be of the requested size plus, eventually,
104 size will be shrunk so the possible headers space and new size will
114 will successfully allocate 800 + 20 + 8 bytes of buffer for the new
121 will successfully allocate 1500 bytes, and where 20 + 8 bytes (IPv4 +
122 UDP headers) will not be used for the payload.
130 will allocate 800 bytes and no extra header space.
137 will allocate 1514 bytes, the MTU + Ethernet header space.
[all …]
|
| D | net_l2.rst | 42 into a :c:type:`net_pkt`, will push this buffer to the network
48 function will return ``NET_DROP`` in case of an erroneous packet,
52 - ``send()``: Similar to receive function, the network stack will call this
54 will be generated and added by this function.
61 - ``get_flags()``: This function will return the capabilities of an L2 driver,
77 macros will call the :c:macro:`DEVICE_DEFINE()` macro, and also
84 In the next section, we will describe how a device driver should behave when
94 :c:func:`net_pkt_rx_alloc_with_buffer`. Then all data buffers will be
98 call :c:func:`net_recv_data`. If that call fails, it will be up to the
101 On sending, the device driver send function will be called, and it is up to
[all …]
|
| /Zephyr-Core-2.7.6/doc/reference/kernel/smp/ |
| D | smp.rst | 14 a supported dual processor device, they will both run simultaneously.
18 a uniprocessor kernel will be built. In general the platform default
19 will have enabled this anywhere it's supported. When enabled, the
21 :kconfig:`CONFIG_MP_NUM_CPUS`. Likewise, the default for this will be the
23 typical apps will change it. But it is legal and supported to set
40 does not: the fact that your CPU will not be interrupted while you are
42 will be running simultaneously and be inspecting or modifying the same
65 re-acquire it or it will deadlock (it is perfectly legal to nest
83 threads. The kernel will ensure that only one thread across all CPUs
86 when a thread is switched in. Other CPUs will spin waiting for the
[all …]
|
| /Zephyr-Core-2.7.6/boards/ |
| D | Kconfig | 7 the Zephyr release that the board configuration will be removed.
8 When set, any build for that board will generate a clearly visible
21 When building for a qemu target then NET_DRIVERS will be default
46 Enable QEMU virtual instruction counter. The virtual cpu will
47 execute one instruction every 2^N ns of virtual time. This will
54 The virtual CPU will execute one instruction every 2^N nanoseconds
71 This option indicates that QEMU will use UEFI bootable method
|
| /Zephyr-Core-2.7.6/subsys/demand_paging/eviction/ |
| D | Kconfig | 14 This option is chosen when the eviction algorithm will be implemented
21 A periodic timer will clear the accessed state of all virtual pages.
22 When a page frame needs to be evicted, the algorithm will prefer to
37 A periodic timer will fire that clears the accessed state of all virtual
39 still has the accessed property, it will be considered as recently used.
|
| /Zephyr-Core-2.7.6/samples/net/lldp/ |
| D | prj.conf | 33 # There will be three network interfaces. This is just an example
36 # First ethernet interface will use these settings
42 # Second ethernet interface will have these settings
59 # VLAN settings. We will have three VLANs in this sample.
60 # The CONFIG_NET_VLAN_COUNT will also determine how many ethernet network
61 # interfaces there will be in the system.
|
| /Zephyr-Core-2.7.6/cmake/ |
| D | target_toolchain_flags.cmake | 7 # the MD5 will also change (as example toolchain upgrade in same folder)
9 # multiple symlinks pointing to same executable will generate different
11 # ccache will generate unique signatures
13 # * CMAKE_C_COMPILER_VERSION will ensure that even when using the previous
15 # usage and symbolic links, then the upgraded compiler will have new version
18 # Toolchains with the same signature will always support the same set of flags.
27 # Load the compile features file which will provide compile features lists for
|
| /Zephyr-Core-2.7.6/subsys/testsuite/ |
| D | Kconfig | 14 Mark a project or an application as a test. This will enable a few
37 This option will build your application with the -coverage option
38 which will generate data that can be used to create coverage reports.
48 This option will select the custom gcov library. The reports will
63 and that the build system will [override and] enable USERSPACE
70 OK to enable this even if the test will run on platforms which do
120 This option will enable hardware-based stack protection by default
129 This option will help test the flash drivers. This should be enabled
143 when building a Secure ARMv8-M firmware. This will allow
|
| /Zephyr-Core-2.7.6/soc/posix/inf_clock/ |
| D | soc.h | 26 * There is 5 choices for when the function will be called (level):
27 * * PRE_BOOT_1: Will be called before the command line parameters are parsed,
30 * * PRE_BOOT_2: Will be called after the command line parameters are parsed,
33 * * PRE_BOOT_3: Will be called after the HW models initialization, right before
36 * * FIRST_SLEEP: Will be called the 1st time the CPU is sent to sleep
38 * * ON_EXIT: Will be called during termination of the native application
|
| /Zephyr-Core-2.7.6/tests/kernel/poll/src/ |
| D | test_poll_fail.c | 19 * as parameter to check if a error will be met.
36 * as parameter to check if a error will be met.
52 * as parameter to check if a error will be met.
74 * as parameter to check if a error will be met.
96 * as parameter to check if a error will be met.
118 * as parameter to check if a error will be met.
141 * parameter to check if a error will be met.
157 * as parameter to check if a error will be met.
178 * will be met.
202 * will be met.
[all …]
|
| /Zephyr-Core-2.7.6/subsys/shell/ |
| D | shell_wildcard.c | 49 * Function will search commands tree for commands matching wildcard pattern
50 * stored in argv[cmd_lvl]. When match is found wildcard pattern will be
52 * matching commands function will add as many as possible. Next it will
53 * continue to search for next wildcard pattern and it will try to add matching
60 * @param[in] cmd Pointer to command which will be processed
132 * 3. If algorithm will find a wildcard character it switches to in z_shell_wildcard_prepare()
150 * It will allow to find wildcard commands easily with strstr function. in z_shell_wildcard_prepare()
173 /* Function will search commands tree for commands matching wildcard in z_shell_wildcard_process()
175 * will be replaced by matching commands. If there is no space in the in z_shell_wildcard_process()
176 * buffer to add all matching commands function will add as many as in z_shell_wildcard_process()
[all …]
|
| /Zephyr-Core-2.7.6/subsys/bluetooth/common/ |
| D | Kconfig | 14 The Host will segment the data transmitted to the Controller so that
15 packets sent to the Controller will contain data up to this size.
16 In a combined build this value will be set in both the Host and the
18 In a Host-only build the Host will read the maximum ACL size supported
22 will fragment L2CAP PDUs into ACL data packets.
23 The Controller will return this value in the HCI LE Read Buffer
25 Layer transmission size then the Controller will perform
28 then this will restrict the maximum Link Layer transmission size.
45 The Controller will return this value in the HCI LE Read Buffer Size
64 Host and the Controller will use this value for buffer sizes, and
[all …]
|
| /Zephyr-Core-2.7.6/subsys/net/lib/conn_mgr/ |
| D | Kconfig | 11 When enabled, this will start the connection manager that will
13 whether an interface is connected or not. It will then raise
28 Sets the stack size which will be used by the connection manager
|
| /Zephyr-Core-2.7.6/doc/guides/networking/ |
| D | qemu_user_setup.rst | 22 this gateway, which will filter out packets based on the QEMU command line
40 Once this configuration option is enabled, all QEMU launches will use SLIRP.
42 not pass any arguments to it. This means that the Guest will only be able to
44 will be dropped by QEMU.
57 offloads this to the user, and expects that they will provide arguments
66 this command line will be reported by QEMU only. Here's what this particular
67 example will do,
87 Therefore, IPv6 will not work with User Networking.
|
| /Zephyr-Core-2.7.6/include/drivers/misc/ft8xx/ |
| D | ft8xx_dl.h | 68 * the primitive is selected, it will be valid till the new primitive is
71 * @note The primitive drawing operation will not be performed until
81 * Setting @p c to true will clear the color buffer of the FT8xx to the preset
82 * value. Setting this bit to false will maintain the color buffer of the FT8xx
87 * Setting @p s to true will clear the stencil buffer of the FT8xx to the preset
88 * value. Setting this bit to false will maintain the stencil buffer of the
92 * Setting @p t to true will clear the tag buffer of the FT8xx to the preset
93 * value. Setting this bit to false will maintain the tag buffer of the FT8xx
121 * Sets red, green and blue values of the FT8xx color buffer which will be
136 * FT8xx will ignore all the commands following this command.
[all …]
|
| /Zephyr-Core-2.7.6/subsys/net/l2/ieee802154/ |
| D | Kconfig | 19 Enable support for Sub-GHz devices. This will add a tiny bit more
44 This will print-out both received and transmitted packets.
49 This will print-out received packets only.
54 This will print-out transmitted packets only.
76 This is the level for PAN device, not PAN coordinator. This will make
112 Reassembly timer will start as soon as first packet received
128 IEEE 802.15.4 soft MAC will use to run authentication, encryption and
|
