| /Zephyr-latest/doc/_doxygen/ |
| D | mainpage.md | 20 ## Licensing section in Introduction
26 use other licensing, as described in [Licensing of Zephyr Project
27 components](https://docs.zephyrproject.org/latest/LICENSING.html#zephyr-licensing).
|
| /Zephyr-latest/doc/ |
| D | LICENSING.rst | 5 Licensing of Zephyr Project components
11 licensing in this document.
17 * *Licensing:* `GPLv2 License`_
29 * *Licensing:* `GPLv2 License`_
51 * *Licensing:* `GPLv2 License`_ with Runtime Library Exception
61 * *Licensing:* `GPLv2 License`_
72 * *Licensing:* `MIT License`_
93 * *Licensing:* `BSD-3-clause`_
105 * *Licensing:* `BSD-3-clause`_
|
| D | index.rst | 33 <p>Architecture, features & licensing details</p>
92 licensing, as described in :ref:`Zephyr_Licensing`.
|
| /Zephyr-latest/samples/tfm_integration/tfm_psa_test/ |
| D | sample.yaml | 37 # The test suite below has been disabled due to licensing issues with the QCBOR
38 # library used by t_cose. This test will be re-enabled once the licensing
|
| /Zephyr-latest/ |
| D | CONTRIBUTING.rst | 18 use other licensing and are clearly identified.
21 ensure developers are following licensing criteria for their
|
| /Zephyr-latest/cmake/toolchain/xt-clang/ |
| D | generic.cmake | 16 # obtain license information from remote licensing servers. So here
|
| /Zephyr-latest/cmake/toolchain/xcc/ |
| D | generic.cmake | 21 # obtain license information from remote licensing servers. So here
|
| /Zephyr-latest/lib/hash/ |
| D | hash_func32_djb2.c | 15 * sense to use the default Zephyr licensing.
|
| /Zephyr-latest/doc/project/ |
| D | tsc.rst | 79 Compliance and Licensing
80 Ensure compliance with project licensing requirements and open-source best
81 practices, addressing any licensing-related issues that may arise.
|
| D | dev_env_and_tools.rst | 336 * - :guilabel:`Licensing`
337 - The PR has licensing issues which require a licensing expert to review it.
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 45 Licensing section in Contribution Guidelines
48 Licensing is very important to open source projects. It helps ensure the
62 this, check out articles such as `Why choose Apache 2.0 licensing`_ and
65 .. _Why choose Apache 2.0 licensing:
73 licensing rights and agrees to them. Sometimes the copyright holder isn't the
81 use other licensing, as described in :ref:`Zephyr_Licensing`.
100 ../LICENSING.rst
124 To make a good faith effort to ensure licensing criteria are met, the Zephyr
460 For open source licensing reasons, your commit must include a
|
| D | external.rst | 91 an entry is added to the :ref:`licensing page <zephyr_licensing>`.
|
| D | contributor_expectations.rst | 103 - All files in the PR must comply with :ref:`Licensing
|
| /Zephyr-latest/doc/introduction/ |
| D | index.rst | 34 Licensing section in Introduction
40 imported or reused components of the Zephyr project that use other licensing,
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | cadence_xcc.rst | 27 a remote licensing server.
|
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | CMakeLists.txt | 218 # TODO: Remove this when QCBOR licensing issues w/t_cose have been resolved,
222 "with TF-M due to licensing issues with a dependent library. This "
223 "restriction will be removed once licensing issues have been resolved."
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 23 :ref:`module licensing requirements<modules_licensing>` and
296 Licensing requirements and policies
318 Zephyr recommends conveying module licensing via individual license
320 an external project have its own practice of conveying how licensing
323 be referred to in the Zephyr module, as long as licensing requirements,
351 * licensing information as described in :ref:`modules_licensing`.
396 * Licensing changes in the external project
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.6.rst | 316 * ``ZEP-1079`` - Licensing not clear for imported components
|
| D | release-notes-1.9.rst | 290 * ``ZEP-2335`` - Ensure the Licensing page is up-to-date for the release
|
| D | release-notes-1.7.rst | 381 * ``ZEP-1593`` - /scripts/sysgen should create output using SPDX licensing tag
|
| D | release-notes-1.10.rst | 553 * :github:`5266` - Ensure the Licensing page is up-to-date for the release
|
| D | release-notes-1.12.rst | 395 * :github:`6038` - Update Zephyr Licensing page
|
| D | release-notes-2.5.rst | 1907 * :github:`17545` - Licensing and reference to public domain material
|
