Lines Matching refs:blob
29 license as part of the blob submission process. Blob vendors may impose a
51 include a reference to a binary blob to the upstream Zephyr distribution, a
55 Each blob which may be fetched must be individually identified in the
56 corresponding :file:`module.yml` file. A specification for a blob must contain:
58 - An abstract description of the blob itself
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
101 The following binary blob types are acceptable in Zephyr:
117 Note that just because a blob has an acceptable type does not imply that it will
118 be unconditionally accepted by the project; any blob may be rejected for other
120 In case of disagreement, the TSC is the arbiter of whether a particular blob
130 meets these requirements. The project may remove a blob from the upstream
131 distribution if it is discovered that the blob fails to meet these requirements
145 blob requires the build system to provide.
147 * The blob must not depend on Zephyr APIs directly. In other words, it must have
172 around a library blob would not be bootable with open source software.
203 code path that is difficult or impossible to trigger without a blob. Project
207 able to determine if a given issue is due to a bug in Zephyr or the blob itself,
217 The submitter of the proposal to integrate a binary blob must commit to maintain
218 the integration of such blob for the foreseeable future.
254 If, after consideration by the TSC, the submission of the binary blob(s) is
255 approved, the submission process is complete and the binary blob(s) can be