321cb592ef
Adding the following commits to the 3.14 tree for ARM kprobe support: c1750e55eb75 ARM: add uprobes support 33e8a1334afe ARM: Make arch_specific_insn a define for new arch_probes_insn structure b1d3feead083 ARM: Add an emulate flag to the kprobes/uprobes instruction decode functions 84b5b70a01a2 ARM: Change the remaining shared kprobes/uprobes symbols to something generic 624e5e9aab5a ARM: Rename the shared kprobes/uprobe return value enum 7741eac39c2e ARM: Change more ARM kprobes symbol names to something more generic 47f51bac6a2d ARM: Make the kprobes condition_check symbol names more generic 3af2f454bb8e ARM: Remove use of struct kprobe from generic probes code a31964d3143a ARM: use a function table for determining instruction interpreter action 6de77767abfc ARM: move generic thumb instruction parsing code to new files for use by other feature eb2db188b856 ARM: Move generic arm instruction parsing code to new files for sharing between features bbc0a43ff46e ARM: move shared uprobe/kprobe definitions into new include file f5f2896020e6 uprobes: allow ignoring of probe hits cb133db6bd60 ARM: Fix missing includes in kprobes sources (From OE-Core rev: 835bb10d07d1a64119379e9837dd853dacfe79bc) 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, patches against the various components should be sent to their respective upstreams.
bitbake: bitbake-devel@lists.openembedded.org
meta-yocto: poky@yoctoproject.org
Most 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. 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.