Paul Gortmaker refreshed the 3.14-rt support to the latest rt stable content. With these SRCREV bumps, the 3.14 LTSI kernel is now at -rt37. 91dc6afcecd4 rt: bump localversion from 32 to 37 e69f7430b620 rt: bump localversion to 32 c060800318e4 netpoll: guard the access to dev->npinfo with rcu_read_lock/unlock_bh() for CONFIG_PREEMPT_RT_FULL=y 833c21beba79 Revert "timers: do not raise softirq unconditionally" 6c9337ff352c fs,btrfs: fix rt deadlock on extent_buffer->lock 2d542663bfb9 staging: Mark rtl8821ae as broken 988e4701df83 timers: Reduce future __run_timers() latency for first add to empty list 2549262883c5 timers: Reduce future __run_timers() latency for newly emptied list 073fac19d3e4 timers: Reduce __run_timers() latency for empty list 25ca11173e64 timers: Track total number of timers in list 277a4ae36580 fs/aio: simple simple work 7b2ebc4e590b lockdep: selftest: fix warnings due to missing PREEMPT_RT conditionals 9afc01954298 thermal: Defer thermal wakups to threads 84d35d05b236 locking: ww_mutex: fix ww_mutex vs self-deadlock f0c8e4837a51 Revert "rwsem-rt: Do not allow readers to nest" df0d51ecf13f sunrpc: make svc_xprt_do_enqueue() use get_cpu_light() f069e339ca02 work-simple: Simple work queue implemenation 0d9e6cbead39 scheduling while atomic in cgroup code 8405cdab8c2c sas-ata/isci: dont't disable interrupts in qc_issue handler dfb7e1ab2427 mips: rt: Replace pagefault_* to raw version ddbe4584a13b ARM: cmpxchg: define __HAVE_ARCH_CMPXCHG for armv6 and later 607f2a27c2ee arm/futex: disable preemption during futex_atomic_cmpxchg_inatomic() 58de8f60159f ARM: enable irq in translation/section permission fault handlers 62d90b45607c x86: UV: raw_spinlock conversion e8d164191f65 rtmutex: enable deadlock detection in ww_mutex_lock functions 9612daf936db rt,locking: fix __ww_mutex_lock_interruptible() lockdep annotation 47915a120d41 rtmutex.c: Fix incorrect waiter check a6a68d53df5f locking/rt-mutex: avoid a NULL pointer dereference on deadlock fb2c256f8a91 futex: Simplify futex_lock_pi_atomic() and make it more robust 7e59d4d5900e futex: Split out the first waiter attachment from lookup_pi_state() 45ccc2e3f25f futex: Split out the waiter check from lookup_pi_state() c5133997a345 futex: Use futex_top_waiter() in lookup_pi_state() 4726c8b47964 futex: Make unlock_pi more robust b55c2c7782ee rtmutex: Avoid pointless requeueing in the deadlock detection chain walk ff7cfbb757d4 rtmutex: Cleanup deadlock detector debug logic e80ba665fa71 rtmutex: Confine deadlock logic to futex 7a9e7c37ccf4 rtmutex: Simplify remove_waiter() d664c14c1db3 rtmutex: Document pi chain walk 64bcb809c720 rtmutex: Clarify the boost/deboost part 02323ee362c4 rtmutex: No need to keep task ref for lock owner check 063983fb0497 rtmutex: Simplify and document try_to_take_rtmutex() f87319b715f1 rtmutex: Simplify rtmutex_slowtrylock() de9723ae23f9 gpio: omap: use raw locks for locking 705ad635f56a rt: bump localversion from 22 to 31 22b5a5cda73a mm/page_alloc: fixup warning from stable merges to -rt (From OE-Core rev: aa1900021aa05ce1d5b8e607de094ae7cf3fcd10) 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.