Lines Matching full:blobs

1 .. _bin-blobs:
3 Binary Blobs
8 help of executable code distributed in binary form. Binary blobs (or blobs for
12 Zephyr supports downloading and using third-party binary blobs via its built-in
18 the support for binary blobs in forks or third-party distributions of Zephyr. In
19 fact, Zephyr’s build system supports arbitrary use cases related to blobs. This
22 blobs if they cannot meet the requirements described in this page.
27 Most binary blobs are distributed under proprietary licenses which vary
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.
39 The Zephyr Project does not host binary blobs in its Git repositories or
42 Fetching blobs
45 Blobs are fetched from official third-party sources by the :ref:`west blobs
46 <west-blobs>` command.
48 The blobs themselves must be specified in the :ref:`module.yml
49 <modules-bin-blobs>` files included in separate Zephyr :ref:`module repositories
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.
63   This is required for reproducibility and to allow bisecting issues as blobs
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.
74 The ``west blobs`` command only fetches and stores the binary blobs themselves.
75 Any accompanying code, including interface header files for the blobs, must be
81 Inclusion of binary blobs will taint the Zephyr build. The definition of
84 in the context of Zephyr, a tainted image will be one that includes binary blobs
97 .. _bin-blobs-types:
128 blobs.
151   APIs may change and such blobs cannot be modified by all project maintainers
161 Precompiled library blobs must be in a data format which is compatible with and
170 Allowing arbitrary library blobs carries a risk of degrading the degree to
175 To mitigate this risk, the scope of upstream library blobs is limited. The
195 support of contributed binary blobs. As a consequence, at the discretion of the
199   blobs to reproduce may not be treated as bugs
202 This does not imply that issues which require blobs to reproduce will be closed
211 Blobs must have designated maintainers that must be responsive to issue reports
212 from users and provide updates to the blobs to address issues. At the discretion
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
234 only required for new binary blobs, updates to binary blobs follow the
237 A request for integration with binary blobs must be made by creating a new
239 about the blobs and the functionality they provide to the project.
243 #. Make sure to read through the :ref:`bin-blobs` section in
246 #. Use the :github:`New Binary Blobs Issue
247    <new?assignees=&labels=RFC&template=008_bin-blobs.md&title=>` to open an issue
250    Request that demonstrates the integration of the binary blobs and then