Lines Matching full:may
7 many different IC families, some functionality may be unavailable without the
29 license as part of the blob submission process. Blob vendors may impose a
55 Each blob which may be fetched must be individually identified in the
119 be unconditionally accepted by the project; any blob may be rejected for other
131 meets these requirements. The project may remove a blob from the upstream
151 APIs may change and such blobs cannot be modified by all project maintainers
163 for maintainability and usability. Use of such libraries may require special
164 compiler and/or linker flags, however. For example, a porting layer may require
165 special flags, or a static archive may require use of specific linker flags.
184 The scope of this test suite may grow over time. The goal is to specify
188 At the discretion of the release team, the project may remove support for a
199 blobs to reproduce may not be treated as bugs
200 - Such issues may be closed as out of scope of the Zephyr project
203 without investigation. For example, the issue may be exposing a bug in a Zephyr
205 maintainers may accept and attempt to resolve such issues.
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.
213 of the Zephyr Project release team, module revisions referencing blobs may be