User Tools

Site Tools


civilinfrastructureplatform:cipkernelmaintenance

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
civilinfrastructureplatform:cipkernelmaintenance [2017/03/30 11:04]
Agustin Benito Bethencourt link to parent page
civilinfrastructureplatform:cipkernelmaintenance [2017/11/09 17:52]
anniefisher
Line 1: Line 1:
 ====== Kernel Maintenance ====== ====== Kernel Maintenance ======
  
-CIP announced ​two relevant decisions during ​the second half of 2016: +October 23, 2017 – The Civil Infrastructure Platform (CIP), which aims to provide a base layer of industrial grade open source software components, tools and methods to enable long-term management of critical systems, today announced the release ​of the CIP Core. The CIP Core, a ​reference ​minimal file system ​that offers a customizable environment that developers can use to test the CIP kernel ​and core packages, was on display at Embedded Linux Conference Europe with planned workshops, demos and Q&A sessions. 
-   * At LinuxCon North America 2016 we announced Ben Hutchings as the CIP kernel ​maintainerBen is currently ​the Debian Long Term Support ​kernel ​maintainer ​and a reputed ​kernel ​hackerspecialised in kernel maintainership+ 
-   * At Embedded Linux Conference Europe 2016 we announced that our first Super Long Term Support ​kernel ​branch will be based on Linux 4.4.+CIP aims to speed implementation of Linux-based civil infrastructure systems, build upon existing open source foundations and expertise, establish de facto standards by providing a base layer reference implementation,​ and contribute to and influence upstream projects regarding industrial needs. 
 + 
 +Hosted by The Linux Foundation, CIP addresses the needs of long-term software for the power generation and distribution,​ water, oil and gas, transportation and building automation industries. CIP members such as Codethink, Hitachi, Plat’Home,​ Renesas, Siemens and Toshiba are working to create a reliable and secure Linux-based embedded software platform that can be sustained more than 10 years and up to 60 years. 
 + 
 +“CIP ​is committed to creating, testing and maintaining an open source software foundation needed to deliver essential services for civil infrastructure and economic development on a global scale,” said Yoshitake Kobayashi, Chair of CIP’s Technical Steering Committee and the Senior Manager of Open Source Technology Department at Toshiba. “The CIP Core is a major milestone that will provide a platform for developers to easily build a reference file system and quickly test the CIP kernel ​with specific application ​and use cases. This customizable testing will eventually became ​part of the product solution.” 
 + 
 +CIP Core features include:  
 +- Creating reference file system images to test and demonstrate use of the CIP kernel ​and core packagesa selected set of open source software components that require super long-term support
 +- Achieving its first milestone after releasing reference file system images for the Beaglebone Black, the iWave RZ/G1M Qseven Development Kit, QEMU x86_64 and the DE0-Nano-SoC development kit. 
 +- Consolidating the CIP kernel ​and core packages into a minimal reference file system that can be tested and used for further development. 
 +- Leveraging released file system images that were generated with Deby, a reproducible and maintainable embedded Linux distribution currently ​based on poky and Debian LTS source code. 
 + 
 +Board at Desk v1.0: 
 +CIP also recently launched Board AT Desk (B@D) v1.0, a customized and easy to deploy instance of the kernelci and LAVA projects that should allow developers to test Linux kernels on boards connected to their own development machines using the tooling provided by one of the most successful Open Source testing projects, kernelci.org. B@D v1.0 is provided as a vagrant virtual machine (VM) image/​recipe and as a VM image, known as a Vagrant box. 
 + 
 +With this release, CIP is moving towards a “shared and trusted testing” target for not just those directly involved in maintaining the CIP kernel but any kernel developer that has physical access to a board. It reduces the deployment, configuration and maintenance costs. B@D introduces a “local” approach to kernelci.org which is a distributed service centrally managed. In addition, CIP intends to increase the number of developers and organizations willing to participate in kernelci.org by providing a simple mechanism to evaluate the technologies developed by that community (LAVA and kernelci) which CIP considers upstream. For more information about the B@D v1.0, read this blog post [[https://​www.cip-project.org/​blog/​2017/​10/​18/​cip-launches-bd-v1-0]].
  
 ===== Maintenance policies ===== ===== Maintenance policies =====
civilinfrastructureplatform/cipkernelmaintenance.txt · Last modified: 2023/09/28 06:49 by jki-siemens