Updating the SRCREVs to integrate the following fixes: 0befa35f4099 drm/i915/chv: Remove DPIO force latency causing interpair skew issue 184e0374e4eb drm/i915: Fix chv cdclk support e2a99b9cd086 drm/i915: Increase the range of sideband address. 9d5d55ede53b drm/i915: Disable DDR DVFS on CHV 96cce945ac97 drm/i915: Enable the maxfifo PM5 mode when appropriate on CHV b5005319da56 drm/i915: Program PFI credits for VLV c7aa33eb3697 drm/i915: Rewrite VLV/CHV watermark code a421d8bcaa6d drm/i915: Make sure PND deadline mode is enabled on VLV/CHV 631afc98c4b5 drm/i915: Read out display FIFO size on VLV/CHV e0dcdc019b8a drm/i915: Pass plane to vlv_compute_drain_latency() a6a5562b7754 drm/i915: Reorganize VLV DDL setup bb662a47ec0c drm/i915: Hide VLV DDL precision handling 3d2d93239cd7 drm/i915: Simplify VLV drain latency computation f68614743b92 drm/i915: Kill DRAIN_LATENCY_PRECISION_* defines 86c658c06ede drm/i915: Reduce CHV DDL multiplier to 16/8 8c4cdd96a3f2 drm/i915: Allow pixel clock up to 95% of cdclk on CHV d9d4fb889c2a drm/i915: Reduce CHV DPLL min vco frequency to 4.8 GHz (From OE-Core rev: 5eaa3c2c57dad400305e5ca64c62b2507fd96a54) 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-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.