Lines Matching full:be
7 many different IC families, some functionality may be unavailable without the
35 Blobs must be hosted on the Internet and managed by third-party infrastructure.
48 The blobs themselves must be specified in the :ref:`module.yml
52 module repository must exist first or be created as part of the submission
55 Each blob which may be fetched must be individually identified in the
61 - The blob’s :ref:`type <bin-blobs-types>`, which must be one of the allowed types
71 The :ref:`west blobs <west-blobs>` command can be used to list metadata of
75 Any accompanying code, including interface header files for the blobs, must be
84 in the context of Zephyr, a tainted image will be one that includes binary blobs
87 Tainting will be communicated to the user in the following manners:
89 - One or more Kconfig options ``TAINT_BLOBS_*`` will be set to ``y``
91 It will be possible to disable the warning using Kconfig
105 precompiled binary form, typically for SoC peripherals. An example could be an
108 processor or CPU. This can be full or partial (typically delta or patch data)
110 could be the firmware for the core running a Bluetooth LE Controller
111 * Miscellaneous binary data files. An example could be pre-trained neural
116 distributed as a static archive would be rejected.
119 be unconditionally accepted by the project; any blob may be rejected for other
138 The precompiled library must be accompanied by one or more header files,
151 APIs may change and such blobs cannot be modified by all project maintainers
154 abstraction layer (aka porting layer) can be provided alongside the library.
155 The implementation of this OS abstraction layer must be in source code form,
161 Precompiled library blobs must be in a data format which is compatible with and
162 can be linked by a toolchain supported by the Zephyr Project. This is required
173 around a library blob would not be bootable with open source software.
177 target must be able to pass using only open source software included in the
185 tests for a minimal feature set which must be supported via open source software
194 The Zephyr Project is not expected to be responsible for the maintenance and
199 blobs to reproduce may not be treated as bugs
200 - Such issues may be closed as out of scope of the Zephyr project
202 This does not imply that issues which require blobs to reproduce will be closed
203 without investigation. For example, the issue may be exposing a bug in a Zephyr
207 However, some flexibility is required because project maintainers may not be
209 may be unable to reproduce the bug due to lack of hardware, etc.
211 Blobs must have designated maintainers that must be responsive to issue reports
213 of the Zephyr Project release team, module revisions referencing blobs may be
221 Regarding Continuous Integration, binary blobs will **not** be fetched in the
232 For references to binary blobs to be included in the project, they must be
237 A request for integration with binary blobs must be made by creating a new
256 approved, the submission process is complete and the binary blob(s) can be