Zephyr 1.14.0 Released (corrected)
All,toggle quoted messageShow quoted text
In my rush to get 1.14 released, I reported on the Major Enhancements from 1.13. Sorry for the confusion. Here is the corrected list of Major Enhancements in 1.14:
* The Zephyr project now supports over 160 different board configurations
spanning 8 architectures. All architectures are rigorously tested and
validated using one of the many simulation platforms supported by the
project: QEMU, Renode, ARC Simulator, and the native POSIX configuration.
* The timing subsystem has been reworked and reimplemented, greatly
simplifying the resulting drivers, removing thousands of lines
of code, and reducing a typical kernel build size by hundreds of bytes.
TICKLESS_KERNEL mode is now the default on all architectures.
* The Symmetric Multi-Processing (SMP) subsystem continues to evolve
with the addition of a new CPU affinity API that can "pin" threads to
specific cores or sets of cores. The core kernel no longer uses the
global irq_lock on SMP systems, and exclusively uses the spinlock API
(which on uniprocessor systems reduces to the same code).
* Zephyr now has support for the x86_64 architecture. It is currently
implemented only for QEMU targets, supports arbitrary numbers of CPUs,
and runs in SMP mode by default, our first platform to do so.
* We've overhauled the Network packet (net-pkt) API and moved the majority
of components and protocols to use the BSD socket API, including MQTT,
CoAP, LWM2M, and SNTP.
* We enhanced the native POSIX port by adding UART, USB, and display
drivers. Based on this port, we added a simulated NRF52832 SoC which enables
running full system, multi-node simulations, without the need of real
* We added an experimental BLE split software Controller with Upper Link Layer
and Lower Link Layer for supporting multiple BLE radio hardware
* The power management subsystem has been overhauled to support device idle
power management and move most of the power management logic from the
application back to the BSP.
* We introduced major updates and an overhaul to both the logging and
shell subsystems, supporting multiple back-ends, integration
of logging into the shell, and delayed log processing.
* Introduced the `west` tool for management of multiple repositories and
enhanced support for flashing and debugging.
* Added support for application user mode, application memory
partitions, and hardware stack protection in ARMv8m
* Applied MISRA-C code guideline on the kernel and core components of Zephyr.
MISRA-C is a well established code guideline focused on embedded systems and
aims to improve code safety, security and portability.
On Apr 16, 2019, at 3:44 PM, Kumar Gala <firstname.lastname@example.org> wrote:
Developers,toggle quoted messageShow quoted text
I wanted to thank everyone again that’s been part of the Zephyr community and contributed to the project and this major milestone in the project’s history.
As we now have an LTS release with 1.14 we will be putting in some processes on how code gets incorporated into the LTS branch. The first such activity is marking any PR that should be considered for LTS with the 'backport v1.14-branch’ tag. We are going to try and utilize a GitHub App that should hopefully help with the backport processes to the v1.14-branch. By tagging the PR with the label, the app will try and automatically create a PR for the backport once the original PR gets merged (if it can).
The TSC is meeting Face to Face next Week (April 24/25th) and one of the topics that we will be discussing is further processes around the LTS branch.
Additionally, now that 1.14 is out, we will slowly start merging PRs, the focus will first be on bug fix PRs as these might also be candidates for 'backport v1.14-branch'. I’d ask all developers, maintainers, and users to look at any outstanding PRs and mark them with the 'backport v1.14-branch’ label if you think they are candidates. Please bare with us as we slowly get back to the normal pace of development.
On Apr 16, 2019, at 4:02 PM, Kumar Gala <email@example.com> wrote: