Lines Matching full:binary

3 Binary Blobs
8 help of executable code distributed in binary form.  Binary blobs (or blobs for
9 short) are files containing proprietary machine code or data in a binary format,
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
21 therefore free to create Zephyr-based downstream software which uses binary
27 Most binary blobs are distributed under proprietary licenses which vary
39 The Zephyr Project does not host binary blobs in its Git repositories or
51 include a reference to a binary blob to the upstream Zephyr distribution, a
74 The ``west blobs`` command only fetches and stores the binary blobs themselves.
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
101 The following binary blob types are acceptable in Zephyr:
104   precompiled binary form, typically for SoC peripherals. An example could be an
110 * Miscellaneous binary data files. An example could be pre-trained neural
148   been possible to build the binary without any Zephyr source code present at
194 support of contributed binary blobs. As a consequence, at the discretion of the
217 The submitter of the proposal to integrate a binary blob must commit to maintain
220 Regarding Continuous Integration, binary blobs will **not** be fetched in the
231 For references to binary blobs to be included in the project, they must be
233 only required for new binary blobs, updates to binary blobs follow the
236 A request for integration with binary blobs must be made by creating a new
245 #. Use the :github:`New Binary Blobs Issue
249    Request that demonstrates the integration of the binary blobs and then
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