summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/yocto-project-supported-features.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual/yocto-project-supported-features.rst')
-rw-r--r--documentation/ref-manual/yocto-project-supported-features.rst267
1 files changed, 267 insertions, 0 deletions
diff --git a/documentation/ref-manual/yocto-project-supported-features.rst b/documentation/ref-manual/yocto-project-supported-features.rst
new file mode 100644
index 0000000000..0e6c33cf6e
--- /dev/null
+++ b/documentation/ref-manual/yocto-project-supported-features.rst
@@ -0,0 +1,267 @@
1.. SPDX-License-Identifier: CC-BY-SA-2.0-UK
2
3**************************************************
4Yocto Project Supported Architectures And Features
5**************************************************
6
7The Yocto Project is putting continuous efforts into testing the changes made to
8the :term:`OpenEmbedded-Core (OE-Core)` metadata and core tools. The details on
9how this test environment functions is described in the
10:doc:`/test-manual/index`.
11
12These tests are also run for stable and :term:`LTS` versions of the Yocto
13Project. See the :doc:`/ref-manual/release-process` section of the Yocto Project
14Reference Manual for more information on these types of releases.
15
16The infrastructure behind the test environment is the
17:ref:`Yocto Project Autobuilder <test-manual/intro:Yocto Project Autobuilder
18Overview>`. The Autobuilder contains a set of Builders that are associated to an
19architecture or a feature to test. For example, the ``qemuarm64`` builder
20corresponds to testing the ARM 64-bit architecture.
21
22Below is a comprehensive list of target architectures and features that are
23supported, as well as their level of support. For each architecture or feature,
24their corresponding builders are also listed.
25
26Primary Supported
27=================
28
29The term "primary" means that dedicated builds for these architectures or
30features are being run on a daily basis on the Yocto Project Autobuilder and
31also tested with incoming changes before they merge. These changes are usually
32on the "-next" Git branches of the :term:`OpenEmbedded-Core (OE-Core)`
33repositories.
34
35Below is a list of primary tested features, their maintainer(s) and builder(s):
36
37.. list-table::
38 :widths: 20 20 20 40
39 :header-rows: 1
40
41 * - Feature
42 - Description
43 - Maintainer(s)
44 - Builder(s)
45 * - :wikipedia:`ARM <ARM_architecture_family>`
46 - ARM architecture testing
47 - Collective effort
48 - genericarm64,
49 genericarm64-alt,
50 musl-qemuarm64,
51 qemuarm,
52 qemuarm-alt,
53 qemuarm-oecore,
54 qemuarm-tc,
55 qemuarm64,
56 qemuarm64-alt,
57 qemuarm64-armhost,
58 qemuarm64-ltp,
59 qemuarm64-ptest,
60 qemuarm64-tc,
61 qemuarmv5
62 * - :yocto_git:`Beaglebone </poky/tree/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf>`
63 - Beaglebone image and SDK build testing
64 - Collective effort
65 - beaglebone,
66 beaglebone-alt
67 * - :doc:`Reproducible </test-manual/reproducible-builds>`
68 - reproducibility testing
69 - Collective effort
70 - reproducible
71 * - :term:`Buildtools`
72 - Buildtools generation
73 - Collective effort
74 - buildtools
75 * - `meta-agl-core <https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl>`__
76 - meta-agl-core layer testing
77 - TBD
78 - meta-agl-core
79 * - `meta-arm <https://git.yoctoproject.org/meta-arm>`__
80 - meta-arm layer testing
81 - meta-arm mailing list <meta-arm@lists.yoctoproject.org>
82 - meta-arm
83 * - `meta-aws <https://github.com/aws4embeddedlinux/meta-aws>`__
84 - meta-aws layer testing
85 - TBD
86 - meta-aws
87 * - `meta-intel <https://git.yoctoproject.org/meta-intel>`__
88 - meta-intel layer testing
89 - meta-intel mailing list <meta-intel@lists.yoctoproject.org>
90 - meta-intel
91 * - `meta-exein <https://github.com/exein-io/meta-exein>`__
92 - meta-exein layer testing
93 - TBD
94 - meta-exein
95 * - `meta-webosose <https://github.com/webosose/meta-webosose>`__
96 - meta-webosose layer testing
97 - TBD
98 - meta-webosose
99 * - :ref:`Multilib <dev-manual/libraries:Combining Multiple Versions of Library Files into One Image>`
100 - Multilib feature testing
101 - Collective effort
102 - multilib
103 * - :term:`OpenEmbedded-Core selftest<OpenEmbedded-Core (OE-Core)>`
104 - OpenEmbedded-Core layers selftests
105 - Collective effort
106 - oe-selftest-fedora,
107 oe-selftest-debian,
108 oe-selftest-armhost
109 * - Package managers
110 - Package managers (RPM, DEB and IPK formats) testing in the
111 :term:`OpenEmbedded Build System` (different from the
112 ``package-management`` :term:`image feature <IMAGE_FEATURES>`)
113 - Collective effort
114 - pkgman-non-rpm (other builders use RPM by default)
115 * - :ref:`Patchtest <contributor-guide/submit-changes:Validating Patches with Patchtest>`
116 - Patchtest tool selftests
117 - Collective effort
118 - patchtest-selftest
119 * - :wikipedia:`RISC-V (64-bit) <RISC-V>`
120 - RISC-V architecture testing (64-bit)
121 - Collective effort
122 - qemuriscv64,
123 qemuriscv64-ptest,
124 qemuriscv64-tc
125 * - :wikipedia:`systemd <Systemd>`
126 - Systemd init manager testing
127 - Collective effort
128 - no-x11, qa-extras2
129 * - :term:`Toaster`
130 - Toaster web interface testing
131 - Collective effort
132 - toaster
133 * - :ref:`Wic <dev-manual/wic:creating partitioned images using wic>`
134 - WIC image creation testing
135 - Collective effort
136 - wic
137 * - :wikipedia:`X86 <X86>`
138 - X86 architecture testing
139 - Collective effort
140 - genericx86,
141 genericx86-64,
142 genericx86-64-alt,
143 genericx86-alt,
144 musl-qemux86,
145 musl-qemux86-64,
146 qemux86,
147 qemux86-64,
148 qemux86-64-alt,
149 qemux86-64-ltp,
150 qemux86-64-ptest,
151 qemux86-64-tc,
152 qemux86-64-x32,
153 qemux86-alt,
154 qemux86-tc,
155 qemux86-world,
156 qemux86-world-alt
157
158Secondary Supported
159===================
160
161The term "secondary" means that in some cases there is code/feature/support
162which is desired by people using the project and is in the project's interests
163to support, however there isn't wide enough interest and support to justify
164testing all incoming changes on it. There are however project member
165organisations and maintainers willing to run tests and review fixes.
166
167This category may be applicable as support/usage in an area develops and grows,
168or as support/usage fades but we continue to have tests. It can also apply where
169resourcing isn't available for full primary support but there is
170member/maintainer support for running tests.
171
172We therefore have the following criteria and policies for such items:
173
174- It can be clearly isolated and defined by specific configuration.
175
176- There is a clear documented group of maintainers agreeing to maintain it.
177
178- Those maintainers are active and responsive.
179
180- It is being actively and publicly tested (potentially using
181 the :ref:`Autobuilder <test-manual/intro:Yocto Project Autobuilder Overview>`
182 by agreement, or otherwise).
183
184- Testing would not be part of standard incoming change testing and regressions
185 would not block incoming patches.
186
187- The :yocto_wiki:`SWAT </Yocto_Build_Failure_Swat_Team>` team would not handle
188 any test builds on the Autobuilder.
189
190- Test results can be submitted as part of the release process if desired.
191
192The Yocto Project :oe_wiki:`Technical Steering Committee (TSC) </TSC>` makes
193decisions on features in this status and Autobuilder testing. Such support would
194be dropped if the maintainers/testing were inactive.
195
196If you are interested in providing resources for improving testing please
197contact the :oe_wiki:`Technical Steering Committee (TSC) </TSC>`.
198
199Below is a list of secondary tested features, their maintainer(s) and
200builder(s):
201
202.. list-table::
203 :widths: 20 20 20 40
204 :header-rows: 1
205
206 * - Feature
207 - Description
208 - Maintainer(s)
209 - Builder(s)
210 * - :wikipedia:`PowerPC (32-bit) <PowerPC>`
211 - PowerPC architecture testing (32-bit)
212 - Peter Marko,
213 Adrian Freihofer
214 - qemuppc,
215 qemuppc-tc
216 * - :oe_git:`meta-openembedded </meta-openembedded>`
217 - meta-openembedded layer testing
218 - Collective effort / openembedded-devel mailing list <openebedded-devel@lists.openembedded.org>
219 - meta-oe
220 * - `meta-mingw <https://git.yoctoproject.org/meta-mingw>`__
221 - mingw based SDKs testing
222 - TBD
223 - meta-mingw
224 * - `meta-virtualization <https://git.yoctoproject.org/meta-virtualization/>`__
225 - meta-virtualization layer testing
226 - meta-virtualization mailing list <meta-virtualization@lists.yoctoproject.org>
227 - meta-virt
228 * - :wikipedia:`RISC-V (32-bit) <RISC-V>`
229 - RISC-V architecture testing (32-bit)
230 - TBD
231 - qemuriscv32,
232 qemuriscv32,
233 qemuriscv32-tc
234
235Untested
236========
237
238"Untested" means that whilst the configurations are present in the project, we
239don't currently run the tests on any regular basis and new changes are not
240tested against them. We may take patches in these areas if they make sense but
241it is on a best effort only basis.
242
243.. list-table::
244 :widths: 20 20 20 40
245 :header-rows: 1
246
247 * - Feature
248 - Description
249 - Maintainer(s)
250 - Builder(s)
251 * - :wikipedia:`MIPS <MIPS_architecture>`
252 - MIPS architecture testing
253 - No maintainers
254 - qemumips,
255 qemumips64,
256 qemumips-alt,
257 qemumips-tc,
258 qemumips64-tc
259 * - :wikipedia:`PowerPC (32-bit) <PowerPC>` Systemd
260 - PowerPC architecture testing (32-bit) with systemd
261 - No maintainers
262 - qemuppc-alt
263 * - :wikipedia:`PowerPC (64-bit) <PowerPC>`
264 - PowerPC architecture testing (64-bit)
265 - No maintainers
266 - qemuppc64,
267 qemuppc64-tc