User Tools

Site Tools


civilinfrastructureplatform:ciptestingboardatdesksingledevfeaturepage

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
civilinfrastructureplatform:ciptestingboardatdesksingledevfeaturepage [2018/06/08 12:08]
rajmarshall [KernelCI] improved formatting
civilinfrastructureplatform:ciptestingboardatdesksingledevfeaturepage [2018/11/28 14:35] (current)
rajmarshall [Snapshot Release] sublink the snapshot on downloads
Line 51: Line 51:
 If we take a deeper look, there are several technologies and configurations involved. This block diagram tries to give a little more detail.  ​ If we take a deeper look, there are several technologies and configurations involved. This block diagram tries to give a little more detail.  ​
  
-Board At Desk - Single Dev. block diagram- this lays out the structure of the testing environment. The host running GNU/Linux or Windows 10 runs B@D within a Vagrant environment,​ this environment is provisioned during initial boot with the kernelci and LAVA packages which pull in other necessary tools using ansible, apt-get and git so that the box is ready for kernel builds and testing. {{ :​civilinfrastructureplatform:​b_d_v1_0_block_diagram.jpg |}}+Board At Desk - Single Dev. block diagram- this lays out the structure of the testing environment. The host running GNU/Linux or Windows 10 runs B@D within a Vagrant environment,​ this environment is provisioned during initial boot with the kernelci and LAVA packages which pull in other necessary tools using ansible, apt-get and git so that the box is ready for kernel builds and testing. {{ :​civilinfrastructureplatform:​b_d_git_block_diagram.jpg?600 |}}
  
 These are the main software components and the versions shipped in the previous version compared to the current one. These are the main software components and the versions shipped in the previous version compared to the current one.
Line 98: Line 98:
  
 The overall CIP license policy can be read [[https://​www.cip-project.org/​wp-content/​uploads/​sites/​17/​2017/​04/​cip_agreement_charter_121916.pdf | here ]]. The overall CIP license policy can be read [[https://​www.cip-project.org/​wp-content/​uploads/​sites/​17/​2017/​04/​cip_agreement_charter_121916.pdf | here ]].
 +
 +===== Snapshot Release =====
 +
 +A snapshot release was created in October 2018 to support the Renesas iwg20m board and include the latest bug fixes. See the [[cipdownload#​snapshot-b-d-box|Download page]] page for links.
  
 ===== Prerequisites ===== ===== Prerequisites =====
Line 156: Line 160:
    * Renesas iWave-M (iwg20m)    * Renesas iWave-M (iwg20m)
       * [[http://​www.iwavesystems.com/​rz-g1m-qseven-development-kit.html|Board specs]] description.       * [[http://​www.iwavesystems.com/​rz-g1m-qseven-development-kit.html|Board specs]] description.
-      ​* Information about [[https://​www.elinux.org/​R-Car/​Upstream-Kernel-Release-Highlights|new features]] being incorporated to the Linux Kernel that could be incorporated to the CIP kernel, so they can be tested in B@D. +   * Information about [[https://​www.elinux.org/​R-Car/​Upstream-Kernel-Release-Highlights|new features]] being incorporated to the Linux Kernel that could be incorporated to the CIP kernel, so they can be tested in B@D. 
-      * [[https://​elinux.org/​RZ-G/​Boards/​SK-RZG1M|Set up instructions]] to bring a different board, but the same SoC, up. +   ​* [[https://​elinux.org/​RZ-G/​Boards/​SK-RZG1M|Set up instructions]] to bring a different board, but the same SoC, up. 
    * Cyclone V (not supported yet)    * Cyclone V (not supported yet)
    * Kernel CI https://​kernelci.org/​    * Kernel CI https://​kernelci.org/​
 [[ciptesting|Back to the parent page]] [[ciptesting|Back to the parent page]]
civilinfrastructureplatform/ciptestingboardatdesksingledevfeaturepage.1528459711.txt.gz · Last modified: 2018/06/08 12:08 by rajmarshall