Lines Matching +full:open +full:- +full:source

1 .. _bin-blobs:
10 e.g. without corresponding source code released under an OSI approved license.
12 Zephyr supports downloading and using third-party binary blobs via its built-in
15 `upstream (vanilla) Zephyr <https://github.com/zephyrproject-rtos/zephyr>`_.
18 the support for binary blobs in forks or third-party distributions of Zephyr. In
21 therefore free to create Zephyr-based downstream software which uses binary
30 click-through or other EULA-like workflow when users fetch and install blobs.
35 Blobs must be hosted on the Internet and managed by third-party infrastructure.
45 Blobs are fetched from official third-party sources by the :ref:`west blobs
46 <west-blobs>` command.
49 <modules-bin-blobs>` files included in separate Zephyr :ref:`module repositories
58 - An abstract description of the blob itself
59 - Version information
60 - A reference to vendor-provided documentation
61 - The blob’s :ref:`type <bin-blobs-types>`, which must be one of the allowed types
62 - A checksum for the blob, which ``west blobs`` checks after downloading.
65 - License text applicable to the blob or a reference to such text, in SPDX
68 See the :ref:`corresponding section <modules-bin-blobs>` for a more formal
71 The :ref:`west blobs <west-blobs>` command can be used to list metadata of
72 available blobs and to fetch blobs from user-selected modules.
83 <https://www.kernel.org/doc/html/latest/admin-guide/tainted-kernels.html>`_ and,
89 - One or more Kconfig options ``TAINT_BLOBS_*`` will be set to ``y``
90 - The Zephyr build system, during its configuration phase, will issue a warning.
92 - The ``west spdx`` command will include the tainted status in its output
93 - The kernel's default fatal error handler will also explicitly print out the
95 - The boot banner prints the kernel's tainted status
97 .. _bin-blobs-types:
111 * Miscellaneous binary data files. An example could be pre-trained neural
120 reasons on a case by case basis (see library-specific requirements below).
124 Precompiled library-specific requirements
139 distributed under a non-copyleft OSI approved license, that define the interface
149   been possible to build the binary without any Zephyr source code present at
155   The implementation of this OS abstraction layer must be in source code form,
171 which the upstream Zephyr software distribution is open source. As an extreme
173 around a library blob would not be bootable with open source software.
176 project maintainers define an open source test suite that an upstream
177 target must be able to pass using only open source software included in the
178 mainline distribution and its modules. The open source test suite currently
181 - :file:`samples/philosophers`
182 - :file:`tests/kernel`
185 tests for a minimal feature set which must be supported via open source software
196 Zephyr Project release team, and on a case-by-case basis:
198 - GitHub issues reported on the zephyr repository tracker that require use of
200 - Such issues may be closed as out of scope of the Zephyr project
216 over bit-rot, security issues, etc.
227 .. _blobs-process:
243 #. Make sure to read through the :ref:`bin-blobs` section in
247    <new?assignees=&labels=RFC&template=008_bin-blobs.md&title=>` to open an issue