Home
last modified time | relevance | path

Searched full:standards (Results 1 – 25 of 46) sorted by relevance

12

/Zephyr-Core-3.5.0/lib/posix/
DKconfig18 Enable mostly-standards-compliant implementations of
35 This enables a mostly-standards-compliant implementation of
/Zephyr-Core-3.5.0/doc/develop/languages/c/
Dindex.rst22 Language Standards
25 Zephyr does not target a specific version of the C standards; however, the
50 the standards, in which case it will be necessary to use a more up-to-date
51 compiler toolchain that supports such standards.
Dpicolibc.rst8 (IEEE Std 1003.1-2017)`_ standards. Picolibc is an external open
95 all format specifiers defined by the C17 and POSIX 2018 standards with
/Zephyr-Core-3.5.0/
DCODE_OF_CONDUCT.md12 ## Our Standards
36 Project maintainers are responsible for clarifying the standards of acceptable
DCONTRIBUTING.rst6 standards and methods for submitting changes help reduce the chaos that can result
/Zephyr-Core-3.5.0/drivers/ieee802154/
DKconfig.cc120090 longer exist in recent standards (IEEE 802.15.4-2015+).
96 longer exist in recent standards (IEEE 802.15.4-2015+).
/Zephyr-Core-3.5.0/doc/hardware/peripherals/
Dw1.rst21 The implementation details are specified in the `BOOK OF IBUTTON STANDARDS`_.
93 .. _BOOK OF IBUTTON STANDARDS:
/Zephyr-Core-3.5.0/doc/connectivity/networking/api/
Dgsm_modem.rst14 3GPP standards and provide PPP connection to them.
Dgptp.rst73 https://standards.ieee.org/findstds/standard/802.1AS-2011.html
D8021Qav.rst109 https://standards.ieee.org/standard/802_1Qav-2009.html
Dieee802154.rst20 <https://ieeexplore.ieee.org/browse/standards/get-program/page/series?id=68>`_.
/Zephyr-Core-3.5.0/doc/safety/
Dsafety_overview.rst20 is, what standard we aim to achieve and what quality standards and processes need to be implemented
94 additional requirement caused by functional safety standards. Functional safety considers quality
99 1. Basic software quality standards
111 Basic software quality standards - Safety view
130 standards / guidelines to reduce likelihood of errors.
168 software architecture designs and implement them in accordance with safety standards because some
/Zephyr-Core-3.5.0/dts/bindings/gpio/
Dmikro-bus.yaml12 … https://download.mikroe.com/documents/standards/mikrobus/mikrobus-standard-specification-v200.pdf
/Zephyr-Core-3.5.0/dts/bindings/mtd/
Djedec,jesd216.yaml18 # JESD216 standards should be listed in this binding include file.
/Zephyr-Core-3.5.0/doc/security/
Dsecurity-citations.rst26 .. [NIST02] National Institute of Standards and Technology, FIPS PUB 140-2:
/Zephyr-Core-3.5.0/lib/cpp/
DKconfig19 C++ Standards.
/Zephyr-Core-3.5.0/doc/develop/languages/cpp/
Dindex.rst23 compiler flags passed) for Zephyr apps is C++11. Other standards are
/Zephyr-Core-3.5.0/cmake/compiler/
Dcompiler_flags_template.cmake41 # This section covers flags related to C or C++ standards / standard libs #
/Zephyr-Core-3.5.0/modules/mbedtls/
DKconfig69 The TLS standards mandate max payload size of 16384 bytes. So, for
/Zephyr-Core-3.5.0/include/zephyr/net/
Dieee802154_mgmt.h341 uint8_t key_len; /* a key length of 16 bytes is mandatory for standards conformance */
/Zephyr-Core-3.5.0/cmake/compiler/arcmwdt/
Dcompiler_flags.cmake112 # This section covers flags related to C or C++ standards / standard libs #
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/
Dbluetooth-ctlr-arch.rst250 - * 2.4 GHz radio transceiver with multiple radio standards such as 1 Mbps,
/Zephyr-Core-3.5.0/cmake/compiler/gcc/
Dcompiler_flags.cmake99 # This section covers flags related to C or C++ standards / standard libs #
/Zephyr-Core-3.5.0/samples/subsys/mgmt/hawkbit/
DREADME.rst11 device to retrieve software update tasks. This API is based on HTTP standards
/Zephyr-Core-3.5.0/tests/lib/mem_alloc/src/
Dmain.c15 * NOT guarantee that ALL standards-defined functionality is present, nor does

12