Date   

[PATCH 0/6] Add SDHI support to r8a7743

Fabrizio Castro <fabrizio.castro@...>
 

Dear All,

this patch series adds SDHI support to the r8a7743 SoC.

The only patch that hasn't been backported in this series is:
"ARM: shmobile: r8a7743: Rename SDHI clocks"

This work has been based on top of this series:
https://lists.cip-project.org/pipermail/cip-dev/2018-February/000863.html

Thanks,
Fabrizio

Biju Das (5):
mmc: renesas_sdhi: Add r8a7743/5 support
mmc: renesas_sdhi: Add r8a7743/5 support
ARM: dts: r8a7743: Add SDHI controllers
ARM: dts: iwg20m: Enable SDHI0 controller
ARM: dts: iwg20d-q7: Add SDHI1 support

Fabrizio Castro (1):
ARM: shmobile: r8a7743: Rename SDHI clocks

Documentation/devicetree/bindings/mmc/tmio_mmc.txt | 2 +
arch/arm/boot/dts/r8a7743-iwg20d-q7.dts | 40 ++++++++++++++++++++
arch/arm/boot/dts/r8a7743-iwg20m.dtsi | 17 +++++++++
arch/arm/boot/dts/r8a7743.dtsi | 43 +++++++++++++++++++++-
drivers/mmc/host/sh_mobile_sdhi.c | 2 +
include/dt-bindings/clock/r8a7743-clock.h | 4 +-
6 files changed, 104 insertions(+), 4 deletions(-)

--
2.7.4


Re: Increase of visibility of the work done in Gitlab: proposal

Jan Kiszka
 

On 2018-02-28 01:57, Jeff ErnstFriedman wrote:
Agustin,

Following up on this thread, I would like to raise the option of the
project moving from a Mailman mailing list (currently use) to Group.io.
We would see about a 50% savings over the course of the year and lower
the effort to create and maintain lists.
Maybe we should discuss the numbers at board level.


I leverage Groups.io with other LF projects and find it a better
experience. It is my understanding we can migrate all the existing
content to Groups.io for a one-time fee.
Seems like a an interesting project, but it's a one-man show, and I
would be careful with relying on it at that point.

Jan


Please let me know if there is any interest in me exploring further.



/Jeff ErnstFriedman/
/jernstfriedman@...
<mailto:jernstfriedman@...> /
/2201 Broadway #604, Oakland, CA 94612//
/
/mobile: 510.593.1367 <tel:(510)%20593-1367>/
/skype: jeffrey.ernstfriedman/
/twitter: @namdeirf/

On Thu, Feb 8, 2018 at 8:25 AM, Agustín Benito Bethencourt
<agustin.benito@... <mailto:agustin.benito@...>>
wrote:

__

Hi,

 

in order to increase the visibility of the work done in Gitlab I
suggest one of these two actions:

* Create a mailing list for development notifications where we can
send the notifications of the commits made in gitlab, including the
diffs.

* Send the notifications to this mailing list and let users filter them.

 

I do not expect heavy traffic as long as we do not include Ben's repo.

 

In the same line, I suggest to do the same with IRC, expecting
limited traffic.

 

Best Regards

 

--

Agustín Benito Bethencourt

Principal Consultant

Codethink Ltd


_______________________________________________
cip-dev mailing list
cip-dev@... <mailto:cip-dev@...>
https://lists.cip-project.org/mailman/listinfo/cip-dev
<https://lists.cip-project.org/mailman/listinfo/cip-dev>




_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev


Re: Increase of visibility of the work done in Gitlab: proposal

Daniel Wagner <wagi@...>
 

On 01.03.2018 18:05, Jeff ErnstFriedman wrote:
I would need to see if there are any caveats, but in the FAQ here are
the instructions to get an archive
extract: https://groups.io/static/help#how-can-i-download-my-member-list-and-message-archive,
so it seems a straight forward process to me.
Ah, though this seems only available for the admin of the list.


Re: Increase of visibility of the work done in Gitlab: proposal

Jeff ErnstFriedman <jernstfriedman@...>
 

Daniel,

I would need to see if there are any caveats, but in the FAQ here are the instructions to get an archive extract: https://groups.io/static/help#how-can-i-download-my-member-list-and-message-archive, so it seems a straight forward process to me.

Jeff ErnstFriedman
2201 Broadway #604, Oakland, CA 94612
mobile: 510.593.1367
skype: jeffrey.ernstfriedman
twitter: @namdeirf

On Thu, Mar 1, 2018 at 8:08 AM, Daniel Wagner <wagi@...> wrote:
Hi Jeff,

> Following up on this thread, I would like to raise the option of the
> project moving from a Mailman mailing list (currently use) to Group.io.
> We would see about a 50% savings over the course of the year and lower
> the effort to create and maintain lists.

Is there a way to get an archive extracted from the groups.io platform?

Daniel


Re: Increase of visibility of the work done in Gitlab: proposal

Daniel Wagner <wagi@...>
 

Hi Jeff,

Following up on this thread, I would like to raise the option of the
project moving from a Mailman mailing list (currently use) to Group.io.
We would see about a 50% savings over the course of the year and lower
the effort to create and maintain lists.
Is there a way to get an archive extracted from the groups.io platform?

Daniel


Re: Increase of visibility of the work done in Gitlab: proposal

Jeff ErnstFriedman <jernstfriedman@...>
 

Agustin,

Following up on this thread, I would like to raise the option of the project moving from a Mailman mailing list (currently use) to Group.io. We would see about a 50% savings over the course of the year and lower the effort to create and maintain lists. 

I leverage Groups.io with other LF projects and find it a better experience. It is my understanding we can migrate all the existing content to Groups.io for a one-time fee. 

Please let me know if there is any interest in me exploring further.



Jeff ErnstFriedman
2201 Broadway #604, Oakland, CA 94612
mobile: 510.593.1367
skype: jeffrey.ernstfriedman
twitter: @namdeirf

On Thu, Feb 8, 2018 at 8:25 AM, Agustín Benito Bethencourt <agustin.benito@....uk> wrote:

Hi,

 

in order to increase the visibility of the work done in Gitlab I suggest one of these two actions:

* Create a mailing list for development notifications where we can send the notifications of the commits made in gitlab, including the diffs.

* Send the notifications to this mailing list and let users filter them.

 

I do not expect heavy traffic as long as we do not include Ben's repo.

 

In the same line, I suggest to do the same with IRC, expecting limited traffic.

 

Best Regards

 

--

Agustín Benito Bethencourt

Principal Consultant

Codethink Ltd


_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev



Re: How to develop on the RT version

Chris Brandt <Chris.Brandt@...>
 

Hi Daniel,

On Thursday, February 22, 2018, Daniel Wagner wrote:
In short: linux-4.4.y-cip-rt wont be rebased. linux-4.4.y-cip-rt-rebase
tree contains the extracted patches from linux-4.4.y.cip-rt. Some people
like to get a patchset which they can apply on top of some tree. But it
looks no one here around is particular interested in this.

The linux-4.4.y-cip-patches is just a variation from the rebase branch.
Probably not really useful to anyone. I just archived all the a patches
in that branch. It was useful for me when I started with the scripting
to have a backup but I don't think I need it anymore. So if no one needs
I can drop it completely to avoid further confusion.

Thank you for this information.

I admit, I had 2 purposes for the question:

1. To be able to guild RZ/G customers on how to develop on the RT branch.

2. To get an idea of how to maintain the public repos for the RZ/A BSP with an RT branch. The 'rebase' branch thing didn't seem to make sense to me that anyone would want to follow that.

The current official RZ/A1 BSPs are 3.14, 4.9 and 4.14, although most of the drivers are mainlined at this point. So, maybe on the next CIP cycle, we'll support CIP for RZ/A as well.

Thanks,
Chris


Re: How to develop on the RT version

Daniel Wagner <daniel.wagner@...>
 

Hi Chris,

On 22.02.2018 03:36, Chris Brandt wrote:
On Wednesday, February 21, 2018, Daniel Sangorrin wrote:
The rebase branch is something complimentary, the maintainer may decide
not to prepare it (the same with the patches).
# The rebase branch might useful to see clearly which patches come from
the cip kernel and which ones are from PREEMPT RT.
OK, that was the info that I needed.
Sorry for the late response.

In short: linux-4.4.y-cip-rt wont be rebased. linux-4.4.y-cip-rt-rebase
tree contains the extracted patches from linux-4.4.y.cip-rt. Some people
like to get a patchset which they can apply on top of some tree. But it
looks no one here around is particular interested in this.

The linux-4.4.y-cip-patches is just a variation from the rebase branch.
Probably not really useful to anyone. I just archived all the a patches
in that branch. It was useful for me when I started with the scripting
to have a backup but I don't think I need it anymore. So if no one needs
I can drop it completely to avoid further confusion.

Thanks,
Daniel


Re: How to develop on the RT version

Chris Brandt <Chris.Brandt@...>
 

Hi Daniel,

Thank you for the reply!

On Wednesday, February 21, 2018, Daniel Sangorrin wrote:
The rebase branch is something complimentary, the maintainer may decide
not to prepare it (the same with the patches).
# The rebase branch might useful to see clearly which patches come from
the cip kernel and which ones are from PREEMPT RT.
OK, that was the info that I needed.

Thanks again,
Chris


Re: How to develop on the RT version

Daniel Sangorrin <daniel.sangorrin@...>
 

-----Original Message-----
From: Daniel Sangorrin [mailto:daniel.sangorrin@...]
Sent: Thursday, February 22, 2018 11:19 AM
To: 'Chris Brandt' <Chris.Brandt@...>; 'cip-dev@...' <cip-dev@...>
Subject: RE: [cip-dev] How to develop on the RT version

Hi Chris,

-----Original Message-----
From: cip-dev-bounces@... [mailto:cip-dev-bounces@...] On Behalf Of Chris Brandt
Sent: Friday, February 09, 2018 11:37 PM
To: cip-dev@...
Subject: [cip-dev] How to develop on the RT version

Hello CIP members,

As I look at the git repository, there are multiple PREEMPT_RT branches:

* linux-4.4.y-cip-rt-rebase
* linux-4.4.y-cip-rt
* linux-4.4.y-cip-rt-patches

I'm trying to understand if I want to develop a product using RT, what branch should I be tracking and pulling into my local git repo?
This one: linux-4.4.y-cip-rt

I would think that locally, I would have some git repository that I will pull from CIP and merge into my own tree. I would also be
pushing that to some local server to share with the other team members in my group.

Therefore, the 'rebase' thing doesn't make sense to me because if you are pushing a rebased tree, that means you are changing the
existing parent history and doing a simple 'git pull' doesn't work so well (like what you have with the linux-next tree).
The rebase branch is something complimentary, the maintainer may decide not to prepare it (the same with the patches).
# The rebase branch might useful to see clearly which patches come from the cip kernel and which ones are from PREEMPT RT.

Do I just fetch and merge from 'linux-4.4.y-cip-rt' periodically as I develop my product, and that will play nicely with the local commits
that I am also making and pushing locally to my repository?
That should work unless your local commits create some conflict. You can also rebase your local commits at the same time so that you
have them on the top of the git log for convenience.
Of course, if you rebase the local changes, your team will have to do a hard reset after fetching the new changes.


Thank you,
Daniel


Re: How to develop on the RT version

Daniel Sangorrin <daniel.sangorrin@...>
 

Hi Chris,

-----Original Message-----
From: cip-dev-bounces@... [mailto:cip-dev-bounces@...] On Behalf Of Chris Brandt
Sent: Friday, February 09, 2018 11:37 PM
To: cip-dev@...
Subject: [cip-dev] How to develop on the RT version

Hello CIP members,

As I look at the git repository, there are multiple PREEMPT_RT branches:

* linux-4.4.y-cip-rt-rebase
* linux-4.4.y-cip-rt
* linux-4.4.y-cip-rt-patches

I'm trying to understand if I want to develop a product using RT, what branch should I be tracking and pulling into my local git repo?
This one: linux-4.4.y-cip-rt

I would think that locally, I would have some git repository that I will pull from CIP and merge into my own tree. I would also be
pushing that to some local server to share with the other team members in my group.

Therefore, the 'rebase' thing doesn't make sense to me because if you are pushing a rebased tree, that means you are changing the
existing parent history and doing a simple 'git pull' doesn't work so well (like what you have with the linux-next tree).
The rebase branch is something complimentary, the maintainer may decide not to prepare it (the same with the patches).
# The rebase branch might useful to see clearly which patches come from the cip kernel and which ones are from PREEMPT RT.

Do I just fetch and merge from 'linux-4.4.y-cip-rt' periodically as I develop my product, and that will play nicely with the local commits
that I am also making and pushing locally to my repository?
That should work unless your local commits create some conflict. You can also rebase your local commits at the same time so that you
have them on the top of the git log for convenience.

Thank you,
Daniel


CIP kernel tests results

Agustín Benito Bethencourt <agustin.benito@...>
 

Hi,

for those of you who have joined CIP recently, let me remind you that there is
a mailing list where Robert sends a minimalist report of the kernel being
tested with B@D.:

https://lists.cip-project.org/mailman/listinfo/cip-testing-results

Best Regards
--
Agustín Benito Bethencourt
Principal Consultant
Codethink Ltd


Re: [PATCH 0/3] Add RTC support to iwg20d

Chris Paterson
 

From: Fabrizio Castro [mailto:fabrizio.castro@...]
Sent: 19 February 2018 18:46
To: Ben Hutchings <ben.hutchings@...>
Cc: cip-dev@...; Chris Paterson
<Chris.Paterson2@...>; Biju Das <biju.das@...>;
Fabrizio Castro <fabrizio.castro@...>
Subject: [cip-dev][PATCH 0/3] Add RTC support to iwg20d

This patch series aims at adding RTC support to the iwg20d board from iWave.
The commits from this series backport board specific DT support and
defconfig support.

Biju Das (3):
ARM: dts: iwg20d-q7: Add RTC support
ARM: shmobile: Enable BQ32000 rtc in shmobile_defconfig
ARM: multi_v7_defconfig: Enable BQ32000 RTC driver
Series looks okay to me.

Reviewed-by: Chris Paterson <chris.paterson2@...>



arch/arm/boot/dts/r8a7743-iwg20d-q7.dts | 18 ++++++++++++++++++
arch/arm/configs/multi_v7_defconfig | 1 +
arch/arm/configs/shmobile_defconfig | 1 +
3 files changed, 20 insertions(+)

--
2.7.4


[Git][cip-project/cip-testing/kernelci-debian][master] 2 commits: Modify sed to work only on FILE_SERVER_URL Lines. Also change create_builds to clone CIP Kernel

Agustin Benito Bethencourt
 

Agustin Benito Bethencourt pushed to branch master at cip-project / cip-testing / kernelci-debian

Commits:

  • a6c7dc68
    by Don Brown at 2017-02-05T20:07:01-05:00
    Modify sed to work only on FILE_SERVER_URL Lines. Also change create_builds to clone CIP Kernel
    
  • 38e351da
    by Don Brown at 2017-02-22T22:36:49+00:00
    Update README.md

3 changed files:

Changes:

  • README.md
    1
    -# Kernel CI for the Civil Infrastructure Platform #
    
    1
    +# Board at desk - single dev description  #
    
    2 2
     
    
    3
    -This repository provides the vagrant infrastructure that allows users/labs
    
    4
    -to easily set up a Kernel CI frontend and backend tailored to the needs
    
    5
    -of the Civil Infrastructure Platform (http://www.cip-platform.org).
    
    3
    +Board at desk - single dev is an effort to ease the deployment of KernelCI and LAVAv2 allowing
    
    4
    +a developer with a board connected to its machine test kernels. 
    
    5
    +In order to do so, a VM has been created with all the tools and configurations required. 
    
    6
    +The current technology used to create that VM is Vagrant. 
    
    6 7
     
    
    7
    -## KernelCI Virtual Machine Setup & Configuration ##
    
    8
    +# Interesting links #
    
    8 9
     
    
    9
    -The current setup requires (2) Virtual Machines; one for KernelCI and the other for LAVA v2
    
    10
    +* Board at desk - single dev [feature page](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdesksingledevfeaturepage)
    
    11
    +* [Download](https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipdownload) Board at desk - single dev.
    
    12
    +* Instructions to [download and set up Board at desk - single dev](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdesksingledevsetup).
    
    13
    +* [Connect and configure Beaglebone Black](https://wiki.linuxfoundation.org/civilinfrastructureplatform/beagleboneblackboard) to test the kernel on the board.
    
    14
    +* [CIP testing project home page](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting)
    
    10 15
     
    
    11
    -### Setting up the Debian Jessie KernelCI VM ###
    
    12
    -
    
    13
    -1.) Install Vagrant
    
    14
    -
    
    15
    -```[user@host ~] $ sudo apt-get install vagrant```
    
    16
    -
    
    17
    -2.) Install Oracle Virtualbox
    
    18
    -
    
    19
    -```[user@host ~] $ sudo apt-get install virtualbox```
    
    20
    -
    
    21
    -OR, if you downloaded Virtualbox from the Oracle website
    
    22
    -Note: This assumes you are running Ubuntu Xenial(16.04) 64-bit
    
    23
    -```[user@host ~] $ cd Downloads```
    
    24
    -```[user@host Downloads] $ sudo dpkg -i virtualbox-5.1_5.1.8-111374-Ubuntu-xenial_amd64.deb```
    
    25
    -
    
    26
    -3.) Get the CIP Debian Jessie KernelCI Project
    
    27
    -
    
    28
    -```[user@host ~/git] $ git clone https://gitlab.com/cip-project/kernelci-debian.git```
    
    29
    -
    
    30
    -4.) Change to the kernelci-debian directory
    
    31
    -
    
    32
    -```[user@host ~/git] $ cd kernelci-debian```
    
    33
    -
    
    34
    -5.) Launch the KernelCI Virtual Machine
    
    35
    -
    
    36
    -```[user@host ~/git/kernelci-debian] $ vagrant up```
    
    37
    -
    
    38
    -Note: Please ignore any warnings such as “GetPassWarning: Can not control echo on the terminal.” or “Warning: Password input may be echoed.” - These do not affect the operation of the KernelCI VM.
    
    39
    -
    
    40
    -6.) Connect to the KernelCI VM through ssh using vagrant
    
    41
    -
    
    42
    -```[user@host ~] $ vagrant ssh```
    
    43
    -
    
    44
    -### Get CIP Kernel using git ###
    
    45
    -
    
    46
    -7.) Change to the git-repos directory
    
    47
    -
    
    48
    -```vagrant@guest:~$ cd git-repos```
    
    49
    -
    
    50
    -8.) Clone the Linux Kernel
    
    51
    -
    
    52
    -```vagrant@guest:~/git-repos$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git```
    
    53
    -
    
    54
    -9.) Find the branch of the kernel version you want (i.e. 4.4.27)
    
    55
    -
    
    56
    -```vagrant@guest:~/git-repos$ cd linux-stable```
    
    57
    -
    
    58
    -```vagrant@guest:~/git-repos/linux-stable$ git tag -l | grep 4.4.y```
    
    59
    -
    
    60
    -10.) Create a new branch using that tag.
    
    61
    -
    
    62
    -```vagrant@guest:~/git-repos/linux-stable$ git checkout -b cip_v4.4.27 v4.4.27```
    
    63
    -
    
    64
    -### Compile CIP Kernel ###
    
    65
    -
    
    66
    -11.) Set the environment variables
    
    67
    -
    
    68
    -```vagrant@guest:~/git-repos/linux-stable$ export TREE_NAME=cip-test```
    
    69
    -
    
    70
    -```vagrant@guest:~/git-repos/linux-stable$ export ARCH=arm```
    
    71
    -
    
    72
    -```vagrant@guest:~/git-repos/linux$ export CROSS_COMPILE=arm-linux-gnueabi-```
    
    73
    -
    
    74
    -Note: Don't forget the dash (-) at the end of the CROSS_COMPILE line!
    
    75
    -
    
    76
    -12.) Execute the build.py command
    
    77
    -
    
    78
    -```vagrant@guest:~/git-repos/linux-stable$ ~/kernelci-build/build.py -c tinyconfig -p CIP-KernelCI```
    
    79
    -
    
    80
    -13.) The Web Server is already running in the background. when you navigate from page to page the logs are written to the screen. To get back to the command line, simply press Enter
    
    81
    -
    
    82
    -14.) On your host machine, open a web browser and enter the following in the address box:
    
    83
    -
    
    84
    -http://localhost:5000
    
    85
    -
    
    86
    -15.) You will see the KernelCI Website home page from which, you can navigate to the different builds and trees that you've created
    
    87
    - 
    
    16
    +# Contribute to the CIP testing project: #
    
    17
    +* Please read the Testing at [CIP FAQ](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingfaq) to learn more about this action.
    
    18
    +* Join the technical mailing list ( [cip-dev](https://lists.cip-project.org/mailman/listinfo/cip-dev) ) to follow this effort.
    
    19
    +* Report a [bug](https://gitlab.com/cip-project/testing/boards). 
    
    88 20
     

  • integration-scripts/configure_singledev.sh
    ... ... @@ -11,11 +11,11 @@ sudo sed -ie 's/app.run(thread/app.run(host='\''0.0.0.0'\'', thread/g' /srv/kern
    11 11
     # To Make KernelCI use the local machine for the "KernelCI Storage Server"
    
    12 12
     # 1. Add this line in Vagrantfile, where ports are forwarded:
    
    13 13
     # Make FILE_SERVER_URL point to 'http://localhost:8000/' instead of 'localhost'.
    
    14
    -sudo sed -ie "s/localhost/localhost:8000\//" /etc/linaro/kernelci-frontend.cfg
    
    14
    +sudo sed -ie "/FILE_SERVER_URL/s/localhost/localhost:8000\//g" /etc/linaro/kernelci-frontend.cfg
    
    15 15
     
    
    16 16
     # 2. The first is /etc/linaro/kernelci-frontend.cfg:
    
    17 17
     # Make FILE_SERVER_URL point to "http://127.0.0.1:8000/" instead of "127.0.0.1".
    
    18
    -sudo sed -ie "s/127.0.0.1\//127.0.0.1:8000\//" /srv/kernelci-frontend/app/dashboard/default_settings.py
    
    18
    +sudo sed -ie "/FILE_SERVER_URL/s/127.0.0.1/127.0.0.1:8000/g" /srv/kernelci-frontend/app/dashboard/default_settings.py
    
    19 19
     
    
    20 20
     # 3. Run the fileserver from the directory that has artifacts:
    
    21 21
     # cd /var/www/images/kernel-ci
    

  • scripts/create_builds.sh
    1 1
     cd ~
    
    2 2
     cd git-repos
    
    3
    -git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
    
    3
    +git clone https://gitlab.com/cip-project/linux-cip.git
    
    4 4
     cd linux-stable
    
    5 5
     git checkout -b cip_v4.4.27 v4.4.27
    
    6 6
     echo "Building ARMhf cip-tyrannosaurus Tree"
    


  • [Git][cip-project/cip-testing/kernelci-build][master] 2 commits: Add licence headers #110

    Agustin Benito Bethencourt
     

    Agustin Benito Bethencourt pushed to branch master at cip-project / cip-testing / kernelci-build

    Commits:

    • ab0ca46a
      by Robert Marshall at 2017-06-30T15:50:44+01:00
      Add licence headers #110
      
    • e2b922a7
      by Robert Marshall at 2017-10-12T11:28:12+00:00
      Add new file LICENSE.spdx

    3 changed files:

    Changes:

  • LICENSE.spdx
    1
    +DataLicense: CC0-1.0
    
    2
    +PackageName: B@D
    
    3
    +DataFormat: SPDXRef-1
    
    4
    +PackageSupplier: Organization: Linux Foundation
    
    5
    +PackageHomePage: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting
    
    6
    +PackageLicenseDeclared: AGPL-3.0
    
    7
    +PackageCopyrightText: 2017, Codethink Ltd
    
    8
    +PackageSummary: <text>kernelci build scripts
    
    9
    +                </text>
    
    10
    +Created: 2017-10-12
    
    11
    +PackageDownloadLocation: https://gitlab.com/cip-project/cip-testing/kernelci-build
    
    12
    +Creator: Person: Robert Marshall

  • build-complete.sh
    1 1
     #!/bin/bash
    
    2
    +# Copyright (C) 2017, Linaro Ltd.
    
    3
    +# Copyright (C) 2017 Linux Foundation
    
    4
    +# Copyright (C) 2017, Codethink, Ltd.
    
    5
    +# This program is free software: you can redistribute it and/or modify
    
    6
    +# it under the terms of the GNU Affero General Public License as
    
    7
    +# published by the Free Software Foundation, either version 3 of the
    
    8
    +# License, or (at your option) any later version.
    
    9
    +#
    
    10
    +# This program is distributed in the hope that it will be useful,
    
    11
    +# but WITHOUT ANY WARRANTY; without even the implied warranty of
    
    12
    +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    
    13
    +# GNU Affero General Public License for more details.
    
    14
    +#
    
    15
    +# You should have received a copy of the GNU Affero General Public License
    
    16
    +# along with this program.  If not, see <http://www.gnu.org/licenses/>.
    
    2 17
     
    
    3 18
     rm -rf *
    
    4 19
     
    

  • build.py
    1 1
     #!/usr/bin/env python
    
    2
    +# Copyright (C) 2017, Codethink, Ltd., Robert Marshall
    
    3
    +# SPDX-License-Identifier:	AGPL-3.0
    
    4
    +# This program is free software: you can redistribute it and/or modify
    
    5
    +# it under the terms of the GNU Affero General Public License as
    
    6
    +# published by the Free Software Foundation, either version 3 of the
    
    7
    +# License, or (at your option) any later version.
    
    8
    +#
    
    9
    +# This program is distributed in the hope that it will be useful,
    
    10
    +# but WITHOUT ANY WARRANTY; without even the implied warranty of
    
    11
    +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    
    12
    +# GNU Affero General Public License for more details.
    
    13
    +#
    
    14
    +# You should have received a copy of the GNU Affero General Public License
    
    15
    +# along with this program.  If not, see <http://www.gnu.org/licenses/>.
    
    2 16
     #
    
    3 17
     # NOTES:
    
    4 18
     # - override ARCH and CROSS_COMPILE using environment variables
    


  • [Git][cip-project/cip-testing/testing][master] 2 commits: remove 0001.patch

    Agustin Benito Bethencourt
     

    Agustin Benito Bethencourt pushed to branch master at cip-project / cip-testing / testing

    Commits:

    • ddbe6ede
      by Don Brown at 2017-01-20T12:34:08-05:00
      remove 0001.patch
      
    • 40d4405b
      by Don Brown at 2017-02-22T18:43:47+00:00
      Update README.md

    2 changed files:

    Changes:

  • 0001.patch deleted
    1
    - integration-scripts/install_backend.sh      |  8 +++++++-
    
    2
    - integration-scripts/install_build_script.sh |  9 ++++++++-
    
    3
    - integration-scripts/install_frontend.sh     |  8 +++++++-
    
    4
    - scripts/setup-dev-env.sh                    | 11 +++++++++++
    
    5
    - 4 files changed, 33 insertions(+), 3 deletions(-)
    
    6
    - create mode 100644 scripts/setup-dev-env.sh
    
    7
    -
    
    8
    -diff --git a/integration-scripts/install_backend.sh b/integration-scripts/install_backend.sh
    
    9
    -index 72a974033a3c..157e7184e349 100755
    
    10
    ---- a/integration-scripts/install_backend.sh
    
    11
    -+++ b/integration-scripts/install_backend.sh
    
    12
    -@@ -4,7 +4,13 @@
    
    13
    - # Install kernelci backend
    
    14
    -
    
    15
    - cd $HOME && mkdir git-repos && cd git-repos
    
    16
    --git clone https://github.com/kernelci/kernelci-backend-config.git kernelci-backend
    
    17
    -+
    
    18
    -+GIT_SRC="https://github.com/kernelci/kernelci-backend-config.git"
    
    19
    -+if [ -d /vagrant/kernelci-backend-config ]; then
    
    20
    -+    GIT_SRC=/vagrant/kernelci-backend-config
    
    21
    -+fi
    
    22
    -+git clone $GIT_SRC kernelci-backend
    
    23
    -+
    
    24
    - cp /vagrant/config/secrets-backend.yml kernelci-backend/secrets.yml
    
    25
    -
    
    26
    - # Fixme: Don't let ansible try to create the file in the first place.
    
    27
    -diff --git a/integration-scripts/install_build_script.sh b/integration-scripts/install_build_script.sh
    
    28
    -index 322619317af6..879aaed01792 100755
    
    29
    ---- a/integration-scripts/install_build_script.sh
    
    30
    -+++ b/integration-scripts/install_build_script.sh
    
    31
    -@@ -3,7 +3,14 @@
    
    32
    - # Copyright (C) 2016, Siemens AG, Wolfgang Mauerer <wolfgang.mauerer@...>
    
    33
    - # SPDX-License-Identifier:     Apache-2.0
    
    34
    -
    
    35
    --cd $HOME && git clone https://github.com/kernelci/kernelci-build.git
    
    36
    -+cd $HOME
    
    37
    -+
    
    38
    -+GIT_SRC="https://github.com/kernelci/kernelci-build.git"
    
    39
    -+if [ -d /vagrant/kernelci-build ]; then
    
    40
    -+    GIT_SRC=/vagrant/kernelci-build
    
    41
    -+fi
    
    42
    -+git clone $GIT_SRC
    
    43
    -+
    
    44
    - cd kernelci-build
    
    45
    -
    
    46
    - MASTER_KEY=`cat $HOME/backend-admin-token.txt`
    
    47
    -diff --git a/integration-scripts/install_frontend.sh b/integration-scripts/install_frontend.sh
    
    48
    -index 48ab91ab83ce..251ef89d28f3 100755
    
    49
    ---- a/integration-scripts/install_frontend.sh
    
    50
    -+++ b/integration-scripts/install_frontend.sh
    
    51
    -@@ -4,7 +4,13 @@
    
    52
    - # Install kernelci frontend
    
    53
    -
    
    54
    - cd $HOME/git-repos
    
    55
    --git clone https://github.com/kernelci/kernelci-frontend-config.git kernelci-frontend
    
    56
    -+
    
    57
    -+GIT_SRC="https://github.com/kernelci/kernelci-frontend-config.git"
    
    58
    -+if [ -d /vagrant/kernelci-frontend-config ]; then
    
    59
    -+    GIT_SRC=/vagrant/kernelci-frontend-config
    
    60
    -+fi
    
    61
    -+git clone $GIT_SRC kernelci-frontend
    
    62
    -+
    
    63
    - sed -i kernelci-frontend/roles/install-app/tasks/main.yml \
    
    64
    -     -e 's/kernelci\/kernelci-frontend.git/siemens\/kernelci-frontend.git/'
    
    65
    -
    
    66
    -diff --git a/scripts/setup-dev-env.sh b/scripts/setup-dev-env.sh
    
    67
    -new file mode 100644
    
    68
    -index 000000000000..59c13b233065
    
    69
    ---- /dev/null
    
    70
    -+++ b/scripts/setup-dev-env.sh
    
    71
    -@@ -0,0 +1,11 @@
    
    72
    -+#!/bin/sh
    
    73
    -+
    
    74
    -+if [ ! -f "Vagrantfile" ]; then
    
    75
    -+    echo "script is supposed to be run from the top folder where"
    
    76
    -+    echo "the Vagrantfile is."
    
    77
    -+    exit 1
    
    78
    -+fi
    
    79
    -+
    
    80
    -+git clone https://github.com/kernelci/kernelci-backend-config.git
    
    81
    -+git clone https://github.com/kernelci/kernelci-build.git
    
    82
    -+git clone https://github.com/kernelci/kernelci-frontend-config.git
    
    83
    -

  • README.md
    1
    -# Kernel CI for the Civil Infrastructure Platform #
    
    1
    +# Board at desk - single dev description  #
    
    2 2
     
    
    3
    -This repository provides vagrant infrastructure that allows users/labs
    
    4
    -to easily set up a kernel CI front- end backend tailored to the needs
    
    5
    -of the civil infrastructure platform (http://www.cip-platform.org).
    
    3
    +Board at desk - single dev is an effort to ease the deployment of KernelCI and LAVAv2 allowing
    
    4
    +a developer with a board connected to its machine test kernels. 
    
    5
    +In order to do so, a VM has been created with all the tools and configurations required. 
    
    6
    +The current technology used to create that VM is Vagrant. 
    
    6 7
     
    
    7
    -KernelCI Virtual Machine Setup & Configuration
    
    8
    +# Interesting links #
    
    8 9
     
    
    9
    -The current setup requires (2) Virtual Machines; one for KernelCI and the other for LAVA v2
    
    10
    +* Board at desk - single dev [feature page](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdesksingledevfeaturepage)
    
    11
    +* [Download](https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipdownload) Board at desk - single dev.
    
    12
    +* Instructions to [download and set up Board at desk - single dev](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdesksingledevsetup).
    
    13
    +* [Connect and configure Beaglebone Black](https://wiki.linuxfoundation.org/civilinfrastructureplatform/beagleboneblackboard) to test the kernel on the board.
    
    14
    +* [CIP testing project home page](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting)
    
    10 15
     
    
    11
    -Edit
    
    12
    -Setting up KernelCI VM
    
    16
    +# Contribute to the CIP testing project: #
    
    17
    +* Please read the Testing at [CIP FAQ](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingfaq) to learn more about this action.
    
    18
    +* Join the technical mailing list ( [cip-dev](https://lists.cip-project.org/mailman/listinfo/cip-dev) ) to follow this effort.
    
    19
    +* Report a [bug](https://gitlab.com/cip-project/testing/boards). 
    
    13 20
     
    14
    -1. Install Vagrant
    
    15
    -
    
    16
    -[user@host ~] $ sudo apt-get install vagrant
    
    17
    -
    
    18
    -2. Install Oracle Virtualbox
    
    19
    -
    
    20
    -[user@host ~] $ sudo apt-get install virtualbox
    
    21
    -
    
    22
    -OR, if you downloaded Virtualbox from the Oracle website
    
    23
    -Note: This assumes you are running Ubuntu Xenial(16.04) 64-bit
    
    24
    -[user@host ~] $ cd Downloads
    
    25
    -[user@host Downloads] $ sudo dpkg -i virtualbox-5.1_5.1.8-111374-Ubuntu-xenial_amd64.deb
    
    26
    -
    
    27
    -3. Get the CIP KernelCI Project
    
    28
    -
    
    29
    -[user@host ~/git] $ git clone https://gitlab.com/cip-project/testing.git
    
    30
    -
    
    31
    -4. Change to the testing directory
    
    32
    -
    
    33
    -[user@host ~/git] $ cd testing
    
    34
    -
    
    35
    -5. Launch the KernelCI Virtual Machine
    
    36
    -
    
    37
    -[user@host ~/git/testing] $ vagrant up
    
    38
    -
    
    39
    -Note: Please ignore any warnings such as “GetPassWarning: Can not control echo on the terminal.” or “Warning: Password input may be echoed.” - These do not affect the operation of the KernelCI VM.
    
    40
    -
    
    41
    -6. Connect to the KernelCI VM through ssh using vagrant
    
    42
    -
    
    43
    -[user@host ~] $ vagrant ssh
    
    44
    -
    
    45
    -Edit
    
    46
    -Get CIP Kernel using git
    
    47
    -
    
    48
    -7. Change to the git-repos directory
    
    49
    -
    
    50
    -vagrant@guest:~$ cd git-repos
    
    51
    -
    
    52
    -8. Clone the Linux Kernel
    
    53
    -
    
    54
    -vagrant@guest:~/git-repos$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
    
    55
    -
    
    56
    -9. Find the branch of the kernel version you want (i.e. 4.4.27)
    
    57
    -
    
    58
    -vagrant@guest:~/git-repos$ cd linux-stable
    
    59
    -
    
    60
    -vagrant@guest:~/git-repos/linux-stable$ git tag -l | grep 4.4.y
    
    61
    -
    
    62
    -10. Create a new branch using that tag.
    
    63
    -
    
    64
    -vagrant@guest:~/git-repos/linux-stable$ git checkout -b cip_v4.4.27 v4.4.27
    
    65
    -
    
    66
    -Edit
    
    67
    -Compile CIP Kernel
    
    68
    -
    
    69
    -11. Set the environment variables
    
    70
    -
    
    71
    -vagrant@guest:~/git-repos/linux-stable$ export TREE_NAME=cip-test
    
    72
    -
    
    73
    -vagrant@guest:~/git-repos/linux-stable$ export ARCH=arm
    
    74
    -
    
    75
    -vagrant@guest:~/git-repos/linux$ export CROSS_COMPILE=arm-linux-gnueabi-
    
    76
    -
    
    77
    -Note: Don't forget the dash (-) at the end of the CROSS_COMPILE line!
    
    78
    -
    
    79
    -12. Execute the build.py command
    
    80
    -
    
    81
    -vagrant@guest:~/git-repos/linux-stable$ ~/kernelci-build/build.py -c tinyconfig -p CIP-KernelCI
    
    82
    -
    
    83
    -13. The Web Server is already running in the background. when you navigate from page to page the logs are written to the screen. To get back to the command line, simply press Enter
    
    84
    -
    
    85
    -14. On your host machine, open a web browser and enter the following in the address box:
    
    86
    -
    
    87
    -http://localhost:5000
    
    88
    -
    
    89
    -15. You will see the KernelCI Website home page from which, you can navigate to the different builds and trees that you've created
    
    90
    - 


  • [Git][cip-project/cip-testing/board-at-desk-single-dev][master] 3 commits: Install python-selinux to fix kernelci-backend issue #168

    Agustin Benito Bethencourt
     

    Agustin Benito Bethencourt pushed to branch master at cip-project / cip-testing / board-at-desk-single-dev

    Commits:

    • 645520c6
      by Robert Marshall at 2017-11-06T15:19:06+00:00
      Install python-selinux to fix kernelci-backend issue #168
      
    • c3d64a3b
      by Robert Marshall at 2017-11-07T10:55:53+00:00
      Merge branch 'fix-selinux-error' into 'master'
      
      Install python-selinux to fix kernelci-backend issue #168
      
      See merge request cip-project/cip-testing/board-at-desk-single-dev!51
    • a2b0bba4
      by Robert Marshall at 2018-02-07T13:42:22+00:00
      Fix comment typo (port now 8080)
      

    2 changed files:

    Changes:

  • Vagrantfile
    ... ... @@ -41,7 +41,7 @@ Vagrant.configure(2) do |config|
    41 41
       config.vm.network :forwarded_port, guest: 8010, host: 8010
    
    42 42
       # Forward port 5000 for the KernelCI Frontend Web Server
    
    43 43
       config.vm.network :forwarded_port, guest: 5000, host: 5000
    
    44
    -  # Forward port 80 for the http Lava Frontend Web Server
    
    44
    +  # Forward port 8080 for the http Lava Frontend Web Server
    
    45 45
       config.vm.network :forwarded_port, guest: 8080, host: 8080
    
    46 46
       # Forward port 443 for the https Lava Frontend Web Server
    
    47 47
       config.vm.network :forwarded_port, guest: 443, host: 4443
    

  • integration-scripts/install_dependencies.sh
    ... ... @@ -32,7 +32,7 @@ sudo DEBIAN_FRONTEND=noninteractive apt-get -y update
    32 32
     sudo DEBIAN_FRONTEND=noninteractive apt-get -y upgrade
    
    33 33
     
    
    34 34
     # Install the dependencies
    
    35
    -sudo DEBIAN_FRONTEND=noninteractive apt-get -y install git python-pip python-dev python-concurrent.futures python-tornado libffi-dev libyaml-dev libssl-dev rng-tools python-requests ser2net telnet screen
    
    35
    +sudo DEBIAN_FRONTEND=noninteractive apt-get -y install git python-pip python-dev python-concurrent.futures python-tornado libffi-dev libyaml-dev libssl-dev rng-tools python-requests ser2net telnet screen python-selinux
    
    36 36
     
    
    37 37
     # Install the ARM, ARM-HF & ARM64 Toolchain
    
    38 38
     sudo DEBIAN_FRONTEND=noninteractive apt-get -y install gcc-arm-linux-gnueabi gcc-arm-linux-gnueabihf gcc-aarch64-linux-gnu
    


  • [Git][cip-project/cip-kernel-sec][master] 2 commits: Add fixed-by commit hash for CVE-2017-17857 in 4.14

    Agustin Benito Bethencourt
     


    [Git][cip-project/cip-testing/CIP-kernel-test-logs][master] 2 commits: add README

    Agustin Benito Bethencourt
     

    Agustin Benito Bethencourt pushed to branch master at cip-project / cip-testing / CIP-kernel-test-logs

    Commits:

    • 1681c453
      by Robert Marshall at 2017-07-07T14:56:31+01:00
      add README
      
    • 36cafa6d
      by Robert Marshall at 2017-10-16T11:48:15+01:00
      Update output for v1.0 #144
      

    2 changed files:

    Changes:

  • README.md

  • vagrant-up.output The diff for this file was not included because it is too large.

  • [Git][cip-project/cip-testing/imported-kernel-tests][master] 2 commits: Get install correct

    Agustin Benito Bethencourt
     

    Agustin Benito Bethencourt pushed to branch master at cip-project / cip-testing / imported-kernel-tests

    Commits:

    • bd25c959
      by Robert Marshall at 2017-07-25T14:02:02+01:00
      Get install correct
      
    • 95e5dd3d
      by Robert Marshall at 2017-07-25T14:38:13+01:00
      Initial commit
      

    2 changed files:

    Changes:

  • kselftest.yaml
    ... ... @@ -28,17 +28,17 @@ params:
    28 28
     
    
    29 29
     # Skip install deps and steps on minimal rootfs from LAVA test
    
    30 30
     # Example:
    
    31
    -# "skip_install": "all"
    
    32
    -install:
    
    33
    -    deps:
    
    34
    -        - libpopt-dev
    
    35
    -        - libcap-dev
    
    36
    -        - binutils-dev
    
    37
    -        - perl
    
    38
    -        - wget
    
    39
    -        - tar
    
    40
    -    steps:
    
    41
    -        - './'
    
    31
    +skip_install: all
    
    32
    +# install:
    
    33
    +#     deps:
    
    34
    +#         - libpopt-dev
    
    35
    +#         - libcap-dev
    
    36
    +#         - binutils-dev
    
    37
    +#         - perl
    
    38
    +#         - wget
    
    39
    +#         - tar
    
    40
    +#     steps:
    
    41
    +#         - './'
    
    42 42
     
    
    43 43
     run:
    
    44 44
         steps:
    

  • selftests/kselftest_install.sh
    1
    +#!/bin/bash
    
    2
    +#
    
    3
    +# Kselftest Install
    
    4
    +# Install kselftest tests
    
    5
    +# Author: Shuah Khan <shuahkh@...>
    
    6
    +# Copyright (C) 2015 Samsung Electronics Co., Ltd.
    
    7
    +
    
    8
    +# This software may be freely redistributed under the terms of the GNU
    
    9
    +# General Public License (GPLv2).
    
    10
    +
    
    11
    +install_loc=`pwd`
    
    12
    +
    
    13
    +main()
    
    14
    +{
    
    15
    +	if [ $(basename $install_loc) !=  "selftests" ]; then
    
    16
    +		echo "$0: Please run it in selftests directory ..."
    
    17
    +		exit 1;
    
    18
    +	fi
    
    19
    +	if [ "$#" -eq 0 ]; then
    
    20
    +		echo "$0: Installing in default location - $install_loc ..."
    
    21
    +	elif [ ! -d "$1" ]; then
    
    22
    +		echo "$0: $1 doesn't exist!!"
    
    23
    +		exit 1;
    
    24
    +	else
    
    25
    +		install_loc=$1
    
    26
    +		echo "$0: Installing in specified location - $install_loc ..."
    
    27
    +	fi
    
    28
    +
    
    29
    +	install_dir=$install_loc/kselftest
    
    30
    +
    
    31
    +# Create install directory
    
    32
    +	mkdir -p $install_dir
    
    33
    +# # Build tests
    
    34
    +# 	INSTALL_PATH=$install_dir make install
    
    35
    +}
    
    36
    +
    
    37
    +main "$@"

  • 8321 - 8340 of 9209