Searched full:repository (Results 1 – 25 of 167) sorted by relevance
1234567
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | Kconfig.tfm.partitions | 17 in the trusted-firmware-m repository for details regarding this
20 repository.
28 in the trusted-firmware-m repository for details regarding this
31 repository.
39 in the trusted-firmware-m repository for details regarding this
42 repository.
51 in the trusted-firmware-m repository for details regarding this
54 repository.
62 in the trusted-firmware-m repository for details regarding this
65 repository.
[all …]
|
| /Zephyr-latest/scripts/dts/ |
| D | README.txt | 19 README.txt matches the standalone python-devicetree repository linked
23 repository. We will mirror changes into the standalone repository as
26 Code in the zephyr repository which needs these libraries will import
31 repository will disappear, and a standalone repository will be the
|
| /Zephyr-latest/doc/develop/west/ |
| D | basics.rst | 14 repository>`, while the ``west update`` command initially clones, and later updates, the
30 │ # The manifest repository, never modified by west after creation:
70 manifest repository
71 Every west workspace contains exactly one *manifest repository*, which is a
72 Git repository containing a *manifest file*. The location of the manifest
73 repository is given by the :ref:`manifest.path configuration option
76 For upstream Zephyr, :file:`zephyr` is the manifest repository, but you can
77 configure west to use any Git repository in the workspace as the manifest
78 repository. The only requirement is that it contains a valid manifest file.
102 Any repository known to west (either the manifest repository or any project
[all …]
|
| D | moving-to-west.rst | 22 #. Move your zephyr repository to a new :file:`zephyrproject` parent directory,
41 repository as a local manifest repository::
47 the zephyr repository in any way.
|
| D | workspaces.rst | 32 West does not create a ``manifest-rev`` branch in the manifest repository,
33 since west does not manage the manifest repository's branches or revisions.
143 the manifest repository or as immediate subdirectories of the topdir. However,
146 You may replace a project's repository directory within the workspace with a
156 - T1: star topology, zephyr is the manifest repository
157 - T2: star topology, a Zephyr application is the manifest repository
158 - T3: forest topology, freestanding manifest repository
160 T1: Star topology, zephyr is the manifest repository
163 - The zephyr repository acts as the central repository and specifies
173 T2: Star topology, application is the manifest repository
[all …]
|
| D | built-in.rst | 17 to using all projects in the manifest file plus the manifest repository
29 1. Cloning a new manifest repository from a remote URL
30 2. Creating a workspace around an existing local manifest repository
32 **Option 1**: to clone a new manifest repository from a remote URL, use:
41 the location of the manifest file within the repository using ``--mf``.
49 would clone the upstream official zephyr repository into :file:`zp/zephyr`,
53 repository in the workspace. The default manifest file location is used.
57 the default branch in the manifest repository unless the ``--mr`` option
63 repository, use:
107 #. Initializes a local Git repository for the project in the workspace, if
[all …]
|
| D | without-west.rst | 12 addition to the main zephyr repository, and keeping them up to date
33 In addition to downloading the zephyr source code repository itself,
35 :term:`west manifest` file inside that repository.
45 As you pull changes in the zephyr repository, you will also need to
|
| D | manifest.rst | 6 This page contains detailed information about west's multiple repository model,
18 Multiple Repository Model
32 The history of the manifest repository is the line of Git commits which is
35 repositories in the workspace, with each project repository boxed in by a
36 rectangle. Parent/child commit relationships in each repository are also shown
39 The commits in the manifest repository (again, for upstream Zephyr this is the
40 zephyr repository itself) each have a manifest file. The manifest file in each
43 diagram. Each dotted line arrow points from a commit in the manifest repository
44 to a corresponding commit in a project repository.
48 - Projects can be added (like ``P1`` between manifest repository
[all …]
|
| D | index.rst | 7 ``west``\ [#west-name]_. West is developed in its own `repository`_.
9 West's built-in commands provide a multiple repository management system with
|
| /Zephyr-latest/.github/workflows/ |
| D | backport_issue_check.yml | 20 if: github.repository == 'zephyrproject-rtos/zephyr'
35 -o ${{ github.event.repository.owner.login }} \
36 -r ${{ github.event.repository.name }} \
|
| D | stale-workflow-queue-cleanup.yml | 23 repository: ${{ github.repository }}
|
| D | stats_merged_prs.yml | 11 if: github.event.pull_request.merged == true && github.repository == 'zephyrproject-rtos/zephyr'
24 …erged_prs.py --pull-request ${{ github.event.pull_request.number }} --repo ${{ github.repository }}
|
| D | assigner.yml | 37 FLAGS+=" -o ${{ github.event.repository.owner.login }}"
38 FLAGS+=" -r ${{ github.event.repository.name }}"
|
| D | doc-publish-pr.yml | 20 github.repository == 'zephyrproject-rtos/zephyr'
78 s3://builds.zephyrproject.org/${{ github.event.repository.name }}/pr/${PR_NUM}/docs \
82 … s3://builds.zephyrproject.org/${{ github.event.repository.name }}/pr/${PR_NUM}/api-coverage \
|
| D | issue_count.yml | 18 if: github.repository == 'zephyrproject-rtos/zephyr'
32 title: 'Issues Report for ${{ github.repository }}'
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 15 the Zephyr Project, that is, reside in its own repository, and have its own
54 the Zephyr build system can pull in the source code from the repository.
73 * The module repository codebase shall include a *module.yml* file in a
74 :file:`zephyr/` folder at the root of the repository.
76 * Module repository names should follow the convention of using lowercase
89 * Modules should use "zephyr" as the default name for the repository main
93 * If the module has an external (upstream) project repository, the module
94 repository should preserve the upstream repository folder structure.
99 branch mirroring the master branch of the external repository. It
112 It is preferred to synchronize a module repository with the latest stable
[all …]
|
| D | env_vars.rst | 99 run** ``source zephyr-env.sh`` from the main ``zephyr`` repository. Among
113 to the main ``zephyr`` repository. Among other things, this script runs
121 - set :envvar:`ZEPHYR_BASE` to the location of the zephyr repository
134 You can use the zephyr repository scripts ``zephyr-env.sh`` (for macOS and
137 zephyr repository:
155 - set :envvar:`ZEPHYR_BASE` to the location of the zephyr repository
|
| /Zephyr-latest/doc/safety/ |
| D | safety_requirements.rst | 14 The requirements are gathered in the separate repository:
15 `Requirement repository
21 Below are the guidelines for the requirements repository and the expectations of the safety
22 committee when adding requirements to the repository.
35 Levels of requirements in the repository
80 Pull Request requirement repository
85 * As long as they are applicable to the requirements repository.
|
| /Zephyr-latest/doc/project/ |
| D | index.rst | 48 - subsystem/feature branch: is a branch within the same repository. In our case,
50 repository, which are a copy of a repository sharing the same history.
|
| /Zephyr-latest/scripts/ci/ |
| D | guideline_check.py | 42 parser.add_argument('-r', "--repository", required=False,
43 help="Path to repository")
56 if args.repository is None:
59 repository_path = args.repository
|
| /Zephyr-latest/doc/ |
| D | glossary.rst | 171 west manifest repository
172 The Git repository in a :term:`west workspace` which contains the
178 repository that will be cloned and managed by west when working with the
179 corresponding :term:`west manifest repository`. Note that a west project
185 :term:`west manifest repository` in it. You clone the Zephyr source code,
196 A Git repository containing a :file:`zephyr/module.yml` file, used by the
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 6 The processes described in this document apply to both the zephyr repository itself and the MCUmgr …
15 The upstream MCUmgr repository is located `in this page <https://github.com/apache/mynewt-mcumgr>`_.
23 to the upstream repository of MCUmgr and then bring it to Zephyr with snapshot updates.
28 …* The fix, ported to the Zephyr held code from the upstream repository, is backported to the ``v2.…
139 * ``upstream`` - if the fix has originally been merged to the upstream repository.
145 request 137, which has already been merged to the upstream repository of MCUmgr.
|
| /Zephyr-latest/share/zephyr-package/cmake/ |
| D | ZephyrConfig.cmake | 114 # Project is in Zephyr repository.
115 # We are in Zephyr repository.
117 include_boilerplate("Zephyr repository")
122 # A higher level did the checking and included us and as we are not in Zephyr repository
|
| /Zephyr-latest/modules/percepio/ |
| D | Kconfig | 2 # The real Kconfig for the module is located in the module repository,
|
| /Zephyr-latest/boards/quicklogic/qomu/doc/ |
| D | index.rst | 17 Detailed information about the board can be found in a `Qomu repository`_ and `Qomu User Guide`_.
57 .. _Qomu repository:
|
1234567
