9c353b0849
Integrating the following mainline (or mainline destined) patches to support Intel Broxton: 076cc85486fd mmc: sdhci-acpi: Set MMC_CAP_AGGRESSIVE_PM for Broxton controllers 5d9c3aba78a1 mmc: sdhci-pci: Remove redundant runtime PM calls aa0cd9a58d54 mmc: sdhci: Fix sdhci_runtime_pm_bus_on/off() f47597d00af0 mmc: sdhci: 64-bit DMA actually has 4-byte alignment a052a0703aed mmc: sdhci: Fix DMA descriptor with zero data length f9200dd4bfec mmc: sdio: Fix invalid vdd in voltage switch power cycle 7bbf49488269 mmc: sdhci: Do not BUG on invalid vdd 39fde8b630a6 tools/power turbostat: decode BXT TSC frequency via CPUID 2b4b633da512 tools/power turbostat: initial BXT support ee708ab5b74e intel_telemetry_debugfs: Fix unused warnings in telemetry debugfs 3053465d066b intel_telemetry_pltdrv: Change verbosity control bits 4c7732ec34bf platform:x86: Add Intel Telemetry Debugfs interfaces 401915397ddc platform:x86: Add Intel telemetry platform driver eaaee25ac936 platform/x86: Add Intel Telemetry Core Driver 44c969c62726 platform:x86 decouple telemetry driver from the optional IPC resources a6a2ecaf9980 platform:x86: Add Intel telemetry platform device e1f16b86eab0 intel_pmc_ipc: Avoid pending IPC1 command during legacy suspend ae91be46eb0d intel_pmc_ipc: Fix GCR register base address and length 3e15c1b19c81 intel_pmc_ipc: update acpi resource structure for Punit 5ec614cfd985 intel_punit_ipc: add NULL check for input parameters 4c3f01b178db platform:x86: add Intel P-Unit mailbox IPC driver 4826dbaac15f usb: dwc3: pci: add ID for one more Intel Broxton platform (From OE-Core rev: 802758b2ade24040d16ce4b692a07f97bef39331) (From OE-Core rev: 86bab7e5eaf19d259e60db6207ef687d43475dec) 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> Signed-off-by: Armin Kuster <akuster@mvista.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.