Backporting the following commits for BXT and other device support: b4acdc6d1ea9 serial: 8250_dw: Do not use readl/writel before checking port iotype c439afb78cda serial: 8250_dw: Add support for big-endian MMIO accesses 9227cc288f7e serial: 8250_dw: Avoid serial_outx code duplicate with new dw8250_check_lcr() 9d608cf2b4c5 serial: 8250_dw: don't set UPF_BOOT_AUTOCONF flag db4e65b3a854 serial: 8250_dw: cleanup dw8250_setup_port f4885484ee87 serial: 8250_dw: cleanup dw8250_idma_filter 0912b12e5df0 serial: 8250_dw: rename and comment the fallback dma filter 3436bb74c86b serial: 8250_dw: proper support for UARTs without busy functionality fac8ac4a8074 serial: 8250_dw: add dw8250_quirks function 0bba963bdd94 serial: 8250_dw: only setup the port from one place d01850ea5471 serial: 8250_dw: hook the DMA in one place 585f11e24199 serial: 8250_dw: adapt to unified device property interface df44bc6d8b61 serial: 8250_dw: add separate pointer for the uart_port to dw8250_probe 84e9183637e7 serial: 8250_dw: allow lower reference frequencies 70ce481f5678 serial:8250_dw: do not alter CTS and DCTS since AFE is enabled 739968950dc4 serial: 8250: Auto CTS control by HW if AFE enabled 074cdf88d099 serial: 8250_dw: support ACPI platforms with integrated DMA engine 0bb15fc79c22 serial: 8250_dma: no need to sync RX buffer 45082f48e5c6 dmaengine: idma: rename to INTEL_IDMA64 1f4c5fb48460 mmc: sdhci-acpi: Set MMC_CAP_AGGRESSIVE_PM for Broxton controllers 6963cc8f6e2e mmc: sdhci-pci: Set MMC_CAP_AGGRESSIVE_PM for Broxton controllers aab588165ee4 mmc: sdhci-pci: Add support and PCI IDs for more Broxton host controllers c51e080a85ac mmc: sdhci-acpi: Fix card detect race for Intel BXT/APL fbbad4798f9c mmc: sdhci-pci: Fix card detect race for Intel BXT/APL ce6717f7195e mmc: sdhci: Allow override of get_cd() called from sdhci_request() abceeaf8efc8 mmc: sdhci: Allow override of mmc host operations 279c8ddf6b6d mmc: sdhci: make max-frequency property in device tree work 6e9d3ad3a003 mtd: spi-nor: add support for w25q128fw (From OE-Core rev: 8d11341b23d4f8867b1d829adb8a30556c3a5d54) 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.