Skip to content
Snippets Groups Projects
Verified Commit 362c15d4 authored by Andrei Gherzan's avatar Andrei Gherzan :penguin:
Browse files

SQUASH: Minor typos, grammar and other tweaks


Signed-off-by: Andrei Gherzan's avatarAndrei Gherzan <andrei.gherzan@huawei.com>
parent 18f7ce84
No related branches found
No related tags found
No related merge requests found
Pipeline #13064 passed
...@@ -19,31 +19,31 @@ and documentation for custom components of the toolchain (`tinfoilhat`_, ...@@ -19,31 +19,31 @@ and documentation for custom components of the toolchain (`tinfoilhat`_,
`aliens4friends`_, `dashboard`_, `pipelines`_) can be found in their respective `aliens4friends`_, `dashboard`_, `pipelines`_) can be found in their respective
repositories. repositories.
*TL;DR*: we put ourselves in your shoes (a device maker willing to use Oniro to *TL;DR*: we put ourselves in your shoes, a device maker willing to use Oniro to
develop its products), and we simulated the IP compliance work that you would develop its products. We simulated the IP compliance work you would have to do
have to do on third-party components fetched by Yocto recipes to build your (on third-party components fetched by Yocto recipes) to build your firmware
firmware image(s), to spot possible legal risks and issues. In the true image(-s) and spot possible legal risks and issues. In the true open-source
open-source spirit, every time we found an issue with a particular upstream spirit, every time we found an issue with a particular upstream component, we
component, we raised that issue upstream, and most of the time we got it solved raised that issue upstream, and most of the time we got it solved for you by
for you by upstream developers. upstream developers.
As of Oniro’s 2.0.0 GA Release, there are just a few issues left that cannot be As of Oniro’s 2.0.0 GA Release, there are just a few issues left that we cannot
addressed by us (involving proprietary firmware/drivers for hardware support address. These relate to proprietary firmware/drivers for hardware support and
and some patent-covered technologies) and which require your attention (and some patent-covered technologies. The issues require your attention and
possibly action on your side - eg. getting a patent license). We will possible action, e.g. getting a patent license. We will briefly explain these
briefly explain these here. here.
The overall status of audit activities can be monitored through a `dedicated The overall status of audit activities can be monitored through a `dedicated
dashboard`_, which gets updated after every commit to Oniro's main repository. dashboard`_, which gets updated after every commit to Oniro's main repository.
In the such dashboard, also CVE information (collected at the time of the In the dashboard, also CVE information (collected at the time of the commit) is
commit) is shown and can be filtered based on target machines, images and shown and can be filtered based on target machines, images, and single
single components. components.
Last but not least, we provide reference SPDX SBoM of source packages used to Last but not least, we provide reference SPDX SBoM of source packages used to
build oniro-base-image and zephyr-philosophers images for a selection of build oniro-base-image and zephyr-philosophers images for a selection of
supported target machines (qemu, raspberrypi4, arduino-nano-33ble), generated supported target machines (qemu, raspberrypi4, arduino-nano-33ble), generated
by continuous compliance pipelines. They are provided as a convenience only, by continuous compliance pipelines. They are provided as a convenience only,
with no express warranty or implied about the accuracy and completeness of the with no express or implied warranty about the accuracy and completeness of the
information contained therein (see the disclaimers below): information contained therein (see the disclaimers below):
============================= ====== ============ =================== =================== ============================= ====== ============ =================== ===================
...@@ -70,8 +70,7 @@ you need to perform before marketing your products. ...@@ -70,8 +70,7 @@ you need to perform before marketing your products.
supported Oniro images (oniro-image-base and zephyr-philosophers) for supported supported Oniro images (oniro-image-base and zephyr-philosophers) for supported
target machines (qemux86-64, qemux86, qemuarm-efi, qemuarm64-efi, target machines (qemux86-64, qemux86, qemuarm-efi, qemuarm64-efi,
raspberrypi4-64, seco-intel-b68, seco-px30-d23, seco-imx8mm-c61-2gb, raspberrypi4-64, seco-intel-b68, seco-px30-d23, seco-imx8mm-c61-2gb,
seco-imx8mm-c61-4gb, qemu-cortex-m3, 96b-avenger96, nrf52840dk-nrf52840, seco-imx8mm-c61-4gb, qemu-cortex-m3, nrf52840dk-nrf52840, arduino-nano-33-ble).
arduino-nano-33-ble).
*Disclaimer#3*: “supported” *referred to a board* means that a board is *Disclaimer#3*: “supported” *referred to a board* means that a board is
officially targeted as a potential platform where an Oniro image can be officially targeted as a potential platform where an Oniro image can be
...@@ -131,13 +130,14 @@ IMX Firmware ...@@ -131,13 +130,14 @@ IMX Firmware
^^^^^^^^^^^^ ^^^^^^^^^^^^
A couple of supported target boards (seco-imx8mm-c61-2gb and A couple of supported target boards (seco-imx8mm-c61-2gb and
seco-imx8mm-c61-4gb) require a Freescale proprietary VPU library to work, which seco-imx8mm-c61-4gb) require Freescale i.MX firmware for VPU and SDMA as well
in turn requires the acceptance of a `EULA`_ by the user (you). Such acceptance as firmware for 8M Mini family to train memory interface on SoC and DRAM during
may be provided by flagging a specific environment variable (``ACCEPT_FSL_EULA initialization. These firmware require acceptance of a `EULA`_ by the user
= "1"``) in your configuration file (please refer to Oniro’s technical (you). Such acceptance may be provided by flagging a specific environment
documentation). You should carefully read that `EULA`_ to check whether you are variable (``ACCEPT_FSL_EULA = "1"``) in your configuration file (please refer
actually in a position to accept it and whether you can fulfill all of its to Oniro’s technical documentation). You should carefully read that `EULA`_ to
conditions. If needed, seek legal advice for that. check whether you are actually in a position to accept it and whether you can
fulfill all of its conditions. If needed, seek legal advice for that.
Linux-firmware Linux-firmware
^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^
...@@ -153,13 +153,14 @@ Some of them (apparently) contain further restrictions, stating that the binary ...@@ -153,13 +153,14 @@ Some of them (apparently) contain further restrictions, stating that the binary
file is licensed *“for use with [vendor] devices, but not as a part of the file is licensed *“for use with [vendor] devices, but not as a part of the
Linux kernel or in any other form which would require these files themselves to Linux kernel or in any other form which would require these files themselves to
be covered by the terms of the GNU General Public License”*. Our understanding be covered by the terms of the GNU General Public License”*. Our understanding
is that such restriction is either redundant (apart from some debatable and is that such restriction is either redundant or useless. Apart from some
contested corner cases, there is no way in which a firmware blob may become debatable and contested corner cases, there is no way in which a firmware blob
*part* of the Linux kernel and therefore be covered by the GNU General Public may become part of the Linux kernel and therefore be covered by the GNU General
License) or useless (if someone claims that a proprietary firmware requires Public License - so the above provision seems redundant. But even if someone
such a low-level interaction with the kernel that such firmware must be deemed claimed that a proprietary firmware requires such a low-level interaction with
as a derivative work of the kernel itself, such (alleged) non-compliance with the kernel that such firmware must be deemed as a derivative work of the kernel
GPL could not be avoided or excluded by a vendor license clause). In either itself, such (alleged) non-compliance with GPL could not be avoided or excluded
by a vendor license clause - so the above provision would be useless. In either
case, you should seek legal advice on that if you need to use the affected case, you should seek legal advice on that if you need to use the affected
firmware files. firmware files.
......
...@@ -155,7 +155,7 @@ As part of the Oniro continuous compliance process, all relevant metadata about ...@@ -155,7 +155,7 @@ As part of the Oniro continuous compliance process, all relevant metadata about
compliance and security are collected at build time for every commit to the compliance and security are collected at build time for every commit to the
Oniro project repo, and can be inspected through a `dedicated dashboard`_. Open Oniro project repo, and can be inspected through a `dedicated dashboard`_. Open
CVEs on single components data may be inspected by filtering components by CVEs on single components data may be inspected by filtering components by
status ("has unpatched CVEs") and by opening the component details: open CVEs status ("has unpatched CVEs") and by opening the component details: open CVEs
are displayed first, marked in red and ordered by score, while closed CVEs are are displayed first, marked in red and ordered by score, while closed CVEs are
marked in green. The dashboard gets updated after every commit and contains a marked in green. The dashboard gets updated after every commit and contains a
CVE status snapshot at the time of the commit. However, if some previously open CVE status snapshot at the time of the commit. However, if some previously open
...@@ -198,16 +198,16 @@ operating system built by users from the project manifest is an aggregate ...@@ -198,16 +198,16 @@ operating system built by users from the project manifest is an aggregate
comprised of many third-party components or component groups, each subject to comprised of many third-party components or component groups, each subject to
its license conditions. its license conditions.
Official project release includes only the project manifest as well as Official project release includes only the project manifest, project-specific
project-specific meta-layers, and recipes. Any reference binary image, build meta-layers, and recipes. Any reference binary image, build cache, and other
cache, and other build artefacts are distributed only as a convenience and are build artefacts are distributed only as a convenience and are not part of the
not part of the release itself. release itself.
.. note:: .. note::
"supported" `referred to a board` means that a board is officially targeted "supported" `referred to a board` means that a board is officially targeted
as a potential platform where an Oniro image can be installed for any as a potential platform where an Oniro image can be installed for any
purposes; when `referred to an image`, means that the imagine targeting a purposes; when `referred to an image`, means that the image targeting a
supported board receives thorough testing and specific attention during the supported board receives thorough testing and specific attention during the
development. It does NOT mean that both will receive support services nor development. It does NOT mean that both will receive support services nor
that any member of the Oniro Working Group or of the Eclipse Foundation will that any member of the Oniro Working Group or of the Eclipse Foundation will
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment