f8850a1726
Integrating the following commit(s) to linux-yocto/.:
58666126 genericarm64.scc: enable OP-TEE support
90e118e5 features optee.cfg: enable RPMB support
1d4363c2 genericarm64.cfg: add MTD support for Hyperbus
a6091c0a genericarm64.cfg: improve pmdomain support
fb4ff102 genericarm64.cfg: add MTD SPI NAND support
ce35b9dd genericarm64.cfg: enable Altera and Broadcom PCIe drivers
7701e479 genericarm64-arch.cfg: add new archs
20574dcf genericarm64.cfg: improve SPI support
6575e9c2 genericarm64.cfg: extend sound support via genericarm64-sound.cfg
7af0fff7 genericarm64.cfg: add more thermal drivers
5baf746c genericarm64.cfg: add more ADC support
82b8b2f2 genericarm64.cfg: add more mailbox support
6bcc928b genericarm64-arch.cfg: add Rockchip IO domain and DTPM support
4bd654f3 genericarm64.cfg: enable more Arm extensions
2e7a98fb genericarm64.cfg: add more PHY support
93405670 genericarm64.cfg: add Freescale and Rockchip NAND support
206f0249 genericarm64.cfg: enable more graphics DRM support
e475a5ba genericarm64.cfg: enable more CRYPTO_DEV drivers
65ca974e genericarm64.cfg: add Renesas STM memory controller drivers
20592693 genericarm64.cfg: enable DEVFREQ governors and drivers
c23b00f6 genericarm64.cfg: add CONFIG_ROCKCHIP_PM_DOMAINS=y
900c4d7c genericarm64.scc: enable SRAM support
952ea4f7 zynq: use sram.scc for SRAM support
93fdb4a1 sram: add feature with .scc and .cfg
d75a77bc genericarm64.cfg: enable Qualcomm RTC and DSP drivers
34a37d36 genericarm64.scc: enable nvme support
a50d70a8 intel-x86: use nvme.scc
0e4311da intel amd-x86-64: use nvme.scc
8df9e176 marvell-cn96xx.scc: use nvme.scc
c975d9dc bcm-2xxx-rpi.cfg: use nvme.scc
64047a98 nvme.scc: add feature for NVMe support
8e0c5d1e genericarm64.cfg: enable Tegra firmware drivers
1badd0c5 genericarm64.cfg: enable Qualcomm security firmware interfaces
a4393b2a genericarm64.cfg: add Google and MediaTek firmware drivers
93cf7834 genericarm64.cfg: enable CONFIG_MHI_BUS_PCI_GENERIC=m
413c8ca8 genericarm64.scc: enable firmware driver support
8d812d85 firmware.cfg: enable CONFIG_FW_LOADER_PAGED_BUF=y and CONFIG_FW_LOADER_SYSFS=y
624046ca genericarm64.cfg: enable more PCI/PCIe support
8fb9f378 genericarm64.scc: enable more Bluetooth HW drivers
bedb9b8a bluetooth-hw.scc: add config for Bluetooth HW drivers
35baf131 bluetooth-usb.cfg: enable more drivers
47061600 genericarm64.scc: add bluetooth-usb support
5b21b9d9 bluetooth.cfg: enable LED events
9cc05195 genericarm64.cfg: enable Qualcomm IPC drivers
52932f92 genericarm64.cfg: enable CONFIG_NET_SWITCHDEV=y
2bc84172 genericarm64.scc: enable kubernetes support
6b383a08 qemu-kvm-arm64.cfg: enable KSM with KVM
b58e205f genericarm64.scc: enable KVM support
715986a3 genericarm64.cfg: enable ACPI memory hotplug and error reporting
f362ed14 features: add memory/failure.scc
ec58a666 genericarm64.cfg: enable CONFIG_BLK_DEV_INTEGRITY=y
85984f29 features: add block/integrity.scc
3a49bdb6 genericarm64.cfg: enable CONFIG_JUMP_LABEL=y
19800309 genericarm64-arch.cfg: extend Tegra support
ffcf3235 genericarm64.cfg: enable CONFIG_CPU_FREQ_STAT=y
c594a800 features: add power/cpu_freq_stat.scc
000bfa8a genericarm64-arch.cfg: enable CONFIG_ARCH_AIROHA=y
e64dea75 genericarm64.cfg: enable CONFIG_SCHED_AUTOGROUP=y
270015f9 features: add sched/sched-desktop.scc
e711e072 genericarm64.cfg: add CONFIG_SCHED_HW_PRESSURE=y
(From OE-Core rev: fa3df8b8e28a03c9110731ff578e0fea4f76371f)
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.