mirror of
https://git.yoctoproject.org/poky
synced 2026-05-07 16:59:22 +00:00
b6563a152564fc32a9cca94d8e92432e574a2548
Integrating the following mainline commits for Apollo Lake/Broxton support: 568c4910b938 device property: always check for fwnode type bd2ac1821e91 device property: fallback to pset when gettng one string 44a76bd61eed ACPI / property: Extend fwnode_property_* to data-only subnodes 76f301877fab ACPI / property: Add support for data-only subnodes 95010db1e8f9 ACPI / property: Add routine for extraction of _DSD properties 3d257abeae4d device property: Return -ENXIO if there is no suitable FW interface 15f7db3cd1d0 device property: attach 'else if' to the proper 'if' effb3f07966e ACPI / OF: Rename of_node() and acpi_node() to to_of_node() and to_acpi_node() 30aa0ae9ebf0 ACPI / scan: Parse _CCA and setup device coherency c8b4218d1523 ACPI / property: Define a symbol for PRP0001 3d20c5d27e99 ACPI / property: Refine consistency check for PRP0001 f753cbe35057 device property: avoid allocations of 0 length 6985a3d56431 device property: the secondary fwnode needs to depend on the primary 6c23f8de37ff device property: add spaces to PROPERTY_ENTRY_STRING macro 216b251c170c include/linux/property.h: fix build issues with gcc-4.4.4 c579da0b4812 device property: Take a copy of the property set e0c7ce6ec1eb device property: Fallback to secondary fwnode if primary misses the property a657577af2af device property: improve readability of macros 599f18f62daf device property: Add fwnode_property_match_string() 03599b274370 device property: helper macros for property entry creation 5247e6af02d6 device property: keep single value inplace c12af01cf0d4 device property: refactor built-in properties support 1390c21efa11 device property: rename helper functions (From OE-Core rev: cd4288126b01903fe69714eda772cd4f725ad43a) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
====
Poky is an integration of various components to form a complete prepackaged
build system and development environment. It features support for building
customised embedded device style images. There are reference demo images
featuring a X11/Matchbox/GTK themed UI called Sato. The system supports
cross-architecture application development using QEMU emulation and a
standalone toolchain and SDK with 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 layers which extend the systems capabilities in a modular way.
As an integration layer Poky consists of several upstream projects such as
BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information
e.g. for the hardware support. Poky is in turn a component of the Yocto Project.
The Yocto Project has extensive documentation about the system including a
reference manual which can be found at:
http://yoctoproject.org/documentation
OpenEmbedded-Core is a layer containing the core metadata for current versions
of OpenEmbedded. It is distro-less (can build a functional image with
DISTRO = "nodistro") and contains only emulated machine support.
For information about OpenEmbedded, see the OpenEmbedded website:
http://www.openembedded.org/
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:
bitbake:
Git repository: http://git.openembedded.org/bitbake/
Mailing list: bitbake-devel@lists.openembedded.org
documentation:
Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
Mailing list: yocto@yoctoproject.org
meta-poky, meta-yocto-bsp:
Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto(-bsp)
Mailing list: poky@yoctoproject.org
Everything else should be sent to the OpenEmbedded Core mailing list. If in
doubt, check the oe-core git repository for the content you intend to modify.
Before sending, be sure the patches apply cleanly to the current oe-core git
repository.
Git repository: http://git.openembedded.org/openembedded-core/
Mailing list: openembedded-core@lists.openembedded.org
Note: The scripts directory should be treated with extra care as it is a mix of
oe-core and poky-specific files.
Description