Backporting the following mainline changes to the 4.1 and 4.4 kernels: device property: Avoid potential dereferences of invalid pointers device property: convert to use match_string() helper lib/string: introduce match_string() helper device property: fix for a case of use-after-free device property: fwnode->secondary may contain ERR_PTR(-ENODEV) xhci: harden xhci_find_next_ext_cap against device removal xhci: rework xhci extended capability list parsing functions xhci: parse xhci protocol speed ID list for usb 3.1 usage extcon: Redefine the unique id of supported external connectors without 'enum extcon' type extcon: Remove optional print_name() function pointer of extcon_dev extcon: Update the prototype of extcon_register_notifier() with enum extcon extcon: Use capital letter for the name of external connectors extcon: Use the unique id for external connector instead of string extcon: Remove the optional name of extcon device extcon: adc-jack: Remove the unneeded num_cables field extcon: Alter MHL-TA cable name to TA cable name extcon: Unify the dock device names on max8997/77693 extcon: Unify the jig cable names on rt8973 and max14577/77693/77843 extcon: Fix the checkpatch warning and minor coding style issue extcon: Add extcon_get_edev_name() API to get the extcon device name extcon: Modify the device name as extcon[X] for sysfs extcon: Add manufactor name of each extcon device And the following config change: mei.cfg: Add CONFIG_INTEL_MEI_TXE=m (From OE-Core rev: a04c634adc3d073701ecf2576fe9dd0cf8ace629) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.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.