Home
last modified time | relevance | path

Searched +full:zephyr +full:- +full:main +full:- +full:ci +full:- +full:push +full:- +full:1 (Results 1 – 14 of 14) sorted by relevance

/Zephyr-latest/.github/workflows/
Dtwister-publish.yaml7 - main
9 - completed
12 upload-to-elasticsearch:
14 github.repository == 'zephyrproject-rtos/zephyr' &&
19 runs-on: ubuntu-22.04
22 - name: Checkout
25 fetch-depth: 0
26 persist-credentials: false
28 - name: Download Artifacts
29 id: download-artifacts
[all …]
Dtwister.yaml4 push:
6 - main
7 - v*-branch
8 - collab-*
11 - main
12 - v*-branch
13 - collab-*
16 - cron: '0 3 * * 0'
19 group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.head_ref || github.ref }}
20 cancel-in-progress: true
[all …]
Dfootprint-tracking.yml6 - cron: '50 1/12 * * *'
7 push:
9 - 'VERSION'
10 - '.github/workflows/footprint-tracking.yml'
12 - main
13 - v*-branch
15 # only publish v* tags, do not care about zephyr-v* which point to the
17 - 'v*'
20 group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.head_ref || github.ref }}
21 cancel-in-progress: true
[all …]
/Zephyr-latest/doc/contribute/
Dguidelines.rst6 As an open-source project, we welcome and encourage the community to submit
24 https://github.com/zephyrproject-rtos/zephyr/blob/main/LICENSE
26 .. _GitHub repo: https://github.com/zephyrproject-rtos/zephyr
28 Zephyr uses the `Apache 2.0 license`_ (as found in the LICENSE file in
38 https://www.zephyrproject.org/faqs/#1571346989065-9216c551-f523
41 https://www.whitesourcesoftware.com/whitesource-blog/top-10-apache-license-questions-answered/
52 There are some imported or reused components of the Zephyr project that
55 Importing code into the Zephyr OS from other projects that use a license
57 context and approved by the Zephyr governing board.
61 the Zephyr community can develop products with the Zephyr Project
[all …]
Dcontributor_expectations.rst1 .. _contributor-expectations:
6 The Zephyr project encourages :ref:`contributors <contributor>` to submit
10 - Reviewed more quickly and reviewed more thoroughly. It's easier for reviewers
14 - Less wasted work if reviewers or maintainers reject the direction of the
17 - Easier to rebase and merge. Smaller PRs are less likely to conflict with other
20 - Easier to revert if the PR breaks functionality.
32 - Smaller PRs should encompass one self-contained logical change.
34 - When adding a new large feature or API, the PR should address only one part of
38 - PRs should include tests or samples under the following conditions:
40 - Adding new features or functionality.
[all …]
/Zephyr-latest/doc/project/
Drelease_process.rst6 The Zephyr project releases on a time-based cycle, rather than a feature-driven
7 one. Zephyr releases represent an aggregation of the work of many contributors,
10 A time-based release process enables the Zephyr project to provide users with a
12 roughly 4-month release cycle allows the project to coordinate development of
17 The Zephyr release model was loosely based on the Linux kernel model:
19 - Release tagging procedure:
21 - linear mode on main branch,
22 - release branches for maintenance after release tagging.
23 - Each release period will consist of a development phase followed by a
29 - Development phase: all changes are considered and merged, subject to
[all …]
/Zephyr-latest/doc/releases/
Drelease-notes-2.7.rst5 Zephyr 2.7.0
8 We are pleased to announce the release of Zephyr RTOS version 2.7.0 (LTS2).
17 * Support for M-Profile Vector Extensions (MVE) on ARMv8.1-M
18 * Improved thread safety for Newlib and C++ on SMP-capable systems
20 * New Action-based Power Management API
23 * Linker Support for Tightly-Coupled Memory in RISC-V
25 * Support for extended PCI / PCIe capabilities, improved MIS-X support
27 * Added Zephyr Thread Awareness for OpenOCD to West
33 * The kernel now supports both 32- and 64-bit architectures
36 * We added support for Point-to-Point Protocol (PPP)
[all …]
Drelease-notes-2.6.rst5 Zephyr 2.6.0
8 We are pleased to announce the release of Zephyr RTOS version 2.6.0.
13 * Added support for 64-bit ARCv3
14 * Split ARM32 and ARM64, ARM64 is now a top-level architecture
15 * Added initial support for Arm v8.1-m and Cortex-M55
21 * Added an example standalone Zephyr application in its own Git repository:
22 https://github.com/zephyrproject-rtos/example-application
34 * CVE-2021-3581: Under embargo until 2021-09-04
41 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
46 * Driver APIs now return ``-ENOSYS`` if optional functions are not implemented.
[all …]
Drelease-notes-2.5.rst5 Zephyr 2.5.0
8 We are pleased to announce the release of Zephyr RTOS version 2.5.0.
27 * CVE-2021-3323: Under embargo until 2021-04-14
28 * CVE-2021-3321: Under embargo until 2021-04-14
29 * CVE-2021-3320: Under embargo until 2021-04-14
39 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
56 * Changed vcnl4040 dts binding default for property 'proximity-trigger'.
63 * The :c:func:`mqtt_keepalive_time_left` function now returns -1 if keep alive
67 timeout usage must use the new-style k_timeout_t type and not the
87 GPIO-only regulators a devicetree property ``supply-gpios`` is defined as a
[all …]
Drelease-notes-2.0.rst5 Zephyr 2.0.0
8 We are pleased to announce the release of Zephyr RTOS version 2.0.0.
12 * The kernel now supports both 32- and 64-bit architectures.
17 * We added support for :ref:`Point-to-Point Protocol (PPP) <ppp>`. PPP is a
20 * We added support for UpdateHub, an end-to-end solution for large scale
21 over-the-air device updates.
22 * We added support for ARM Cortex-R Architecture (Experimental).
32 * Fixes CVE-2019-9506: The Bluetooth BR/EDR specification up to and
35 negotiation. This allows practical brute-force attacks (aka "KNOB")
42 * New kernel API for per-thread disabling of Floating Point Services for
[all …]
Drelease-notes-3.3.rst5 Zephyr 3.3.0
8 We are pleased to announce the release of Zephyr version 3.3.0.
14 * Introduced :ref:`USB-C <usbc_api>` device stack with PD (power delivery)
17 CMSIS-DSP as the default backend.
18 * Added Picolibc support for all architectures when using Zephyr SDK.
30 * CVE-2023-0359: Under embargo until 2023-04-20
32 * CVE-2023-0779: Under embargo until 2023-04-22
66 removed in favor of new :dtcompatible:`zephyr,flash-disk` devicetree binding.
68 * Regulator APIs previously located in ``<zephyr/drivers/regulator/consumer.h>``
69 are now part of ``<zephyr/drivers/regulator.h>``.
[all …]
Drelease-notes-1.13.rst5 Zephyr Kernel 1.13.0
8 We are pleased to announce the release of Zephyr kernel version 1.13.0.
16 * Support for IEEE 802.1AS-2011 generalized Precision Time Protocol (gPTP)
23 * Basic support for Arm TrustZone in Armv8-M
42 * arch: arm: implement ARMv8-M MPU driver
44 * arch: arm: macro API for defining non-secure entry functions
48 * arch: ARM: Change the march used by cortex-m0 and cortex-m0plus
50 * arch: arm: basic Arm TrustZone-M functionality for Cortex-M23 and Cortex-M33
51 * arch: arm: built-in stack protection using Armv8-M SPLIM registers
52 * arch: arm: API for using TT intrinsics in Secure/Non-Secure Armv8-M firmware
[all …]
/Zephyr-latest/scripts/ci/
Dcheck_compliance.py5 # SPDX-License-Identifier: Apache-2.0
34 sys.path.insert(0, str(Path(__file__).resolve().parents[1]))
57 f"{cp.stdout.decode('utf-8')}\n"
59 f"{cp.stderr.decode('utf-8')}\n")
61 return cp.stdout.decode("utf-8").rstrip()
70 return git('rev-list',
71 f'--max-count={-1 if "." in refspec else 1}', refspec).split()
74 filter_arg = (f'--diff-filter={filter}',) if filter else ()
75 paths_arg = ('--', *paths) if paths else ()
76 out = git('diff', '--name-only', *filter_arg, COMMIT_RANGE, *paths_arg)
[all …]
/Zephyr-latest/doc/develop/application/
Dindex.rst10 …- your **application directory**, :file:`<app>`, is something like :file:`<home>/zephyrproject/app`
11 - its **build directory** is :file:`<app>/build`
19 <important-build-vars>` is set appropriately, though.)
24 Zephyr's build system is based on `CMake`_.
26 The build system is application-centric, and requires Zephyr-based applications
27 to initiate building the Zephyr source code. The application build controls
28 the configuration and build process of both the application and Zephyr itself,
31 The main zephyr repository contains Zephyr's source code, configuration files,
33 alongside the zephyr repository, which provide third party source code
36 The files in the **application directory** link Zephyr and any modules with the
[all …]