Home
last modified time | relevance | path

Searched full:versions (Results 1 – 25 of 162) sorted by relevance

1234567

/Zephyr-Core-3.4.0/doc/_templates/
Dzversions.html1 {# Add rst-badge after rst-versions for small badge style. #}
2 <div class="rst-versions" data-toggle="rst-versions" role="note" aria-label="versions">
8 <div class="rst-other-versions">
10 <dt>{{ _('Document Release Versions') }}</dt>
11 {% for slug, url in versions %}
/Zephyr-Core-3.4.0/scripts/ci/
Dversion_mgr.py23 VERSIONS_FILE = "versions.json"
28 description="Manage versions to be tested.", allow_abbrev=False)
30 help="List all published versions")
32 help="Update versions file from tree.")
44 if not os.path.exists('versions.json'):
45 url = 'https://testing.zephyrproject.org/daily_tests/versions.json'
46 urllib.request.urlretrieve(url, 'versions.json')
47 with open("versions.json", "r") as fp:
123 with open(VERSIONS_FILE, "w") as versions:
129 json.dump(data, versions)
/Zephyr-Core-3.4.0/.github/
DSECURITY.md3 ## Supported versions
5 The Zephyr project supports the following versions with security
12 versions are:
/Zephyr-Core-3.4.0/.github/workflows/
Ddaily_test_version.yml38 aws s3 cp versions.json s3://testing.zephyrproject.org/daily_tests/versions.json
/Zephyr-Core-3.4.0/arch/arc/core/mpu/
DKconfig11 ARC MPU has several versions. For MPU v2, the minimum region is 2048 bytes;
12 For other versions, the minimum region is 32 bytes; v4 has secure features,
/Zephyr-Core-3.4.0/drivers/dma/
DKconfig.stm3242 Enable DMA V2 or DMA V2bis support. With the versions V2 of DMA, the
44 With the versions V2 bis of DMA, the peripheral request (slot) is not
/Zephyr-Core-3.4.0/arch/posix/include/
Dasm_inline_gcc.h1 /* EMPTY ON PURPOSE. Why do the intel and ARM arch have 2 versions of it? */
/Zephyr-Core-3.4.0/cmake/modules/
DFindZephyr-sdk.cmake63 # Paths that are used to find installed Zephyr SDK versions
74 # return a list of compatible versions and find the best suited version that
106 # This means no compatible Zephyr SDK versions were found, set the version
/Zephyr-Core-3.4.0/include/zephyr/net/
Dsocket_net_mgmt.h90 * following versions.
92 * Network management message versions:
/Zephyr-Core-3.4.0/doc/_static/css/
Dcustom.css25 .rst-versions {
753 .rst-versions {
757 .rst-versions a,
758 .rst-versions .rst-current-version,
759 .rst-versions .rst-current-version .fa,
760 .rst-versions .rst-other-versions dd a {
764 .rst-versions .rst-other-versions small {
768 .rst-versions .rst-other-versions dd a:hover {
772 .rst-versions .rst-other-versions {
776 .rst-versions .rst-current-version {
[all …]
/Zephyr-Core-3.4.0/dts/bindings/test/
Dvnd,great-grandchild-bindings.yaml7 Previous versions of Zephyr only allowed up to two levels of
/Zephyr-Core-3.4.0/tests/lib/cbprintf_fp/
DREADME.txt5 minimal libc and newlib versions with printk, printf, and cbprintf.
/Zephyr-Core-3.4.0/doc/develop/languages/c/
Dpicolibc.rst53 versions of Picolibc for every target architecture, along with
54 precompiled versions of libstdc++.
105 versions of the Bessel functions.
/Zephyr-Core-3.4.0/lib/libc/newlib/include/
Dstdint.h18 /* Has this header. Older versions do it in <stdint.h>. */
/Zephyr-Core-3.4.0/doc/services/device_mgmt/
Dmcumgr_backporting.rst17 Versions of Zephyr past 2.7 use the MCUmgr library that is `part of the Zephyr code base <https://g…
39 Applying fixes to previous versions of MCUmgr
42 This section indicates how to apply fixes to previous versions of MCUmgr.
140 …``zephyr`` - if the fix has been applied to the Zephyr internal MCUmgr library (past 2.7 versions).
/Zephyr-Core-3.4.0/lib/libc/picolibc/
DKconfig32 types are always supported in the floating-point versions.
99 versions.
/Zephyr-Core-3.4.0/subsys/net/lib/lwm2m/
Dlwm2m_senml_cbor.cddl17 ; now define the generic versions
/Zephyr-Core-3.4.0/boards/posix/native_posix/
DCMakeLists.txt42 # This was in general ok, but with some host compilers and C library versions
/Zephyr-Core-3.4.0/include/zephyr/arch/xtensa/
Datomic_xtensa.h10 /* Recent GCC versions actually do have working atomics support on
12 * but existing versions of Xtensa's XCC do not. So we define an
/Zephyr-Core-3.4.0/samples/sensor/fdc2x1x/
DREADME.rst11 to read the 12-Bit and 28-Bit, as well as the 2-Channel and 4-Channel versions
12 (FDC2112, FDC2114, FDC2212, FDC2214). The 4-channel versions are chosen through
/Zephyr-Core-3.4.0/modules/nanopb/
DKconfig51 process packed arrays, such as protobuf.js versions before 2020.
/Zephyr-Core-3.4.0/boards/xtensa/intel_adsp_ace15_mtpm/doc/
Dindex.rst29 For older versions of the toolchain, set the toolchain variant to ``xcc``.
/Zephyr-Core-3.4.0/include/zephyr/mgmt/ec_host_cmd/
Dec_host_cmd.h67 * The bitfield of all versions that the @a handler supports, where
92 * @param _version_mask The bitfield of all versions that the @a _function
115 * @param _version_mask The bitfield of all versions that the @a _function
149 * versions start at 0.
/Zephyr-Core-3.4.0/boards/posix/nrf52_bsim/
DCMakeLists.txt48 # This was in general ok, but with some host compilers and C library versions
/Zephyr-Core-3.4.0/arch/xtensa/core/
Dcpu_idle.c23 /* Cribbed from SOF: workaround for a bug in some versions of in arch_cpu_idle()

1234567