Agustin Benito Bethencourt pushed to branch masterat cip-project / cip-testing / testingCommits: ddbe6ede by Don Brownat 2017-01-20T12:34:08-05:00remove 0001.patch 40d4405b by Don Brownat

Agustin Benito Bethencourt pushed to branch masterat cip-project / cip-testing / board-at-desk-single-devCommits: 645520c6 by Robert Marshallat 2017-11-06T15:19:06+00:00Install python-selinux to fix

Agustin Benito Bethencourt pushed to branch masterat cip-project / cip-kernel-secCommits: 7f1b8a46 by Ben Hutchingsat 2018-01-31T16:38:01+00:00Add fixed-by commit hash for CVE-2017-17857 in

Agustin Benito Bethencourt pushed to branch masterat cip-project / cip-testing / CIP-kernel-test-logsCommits: 1681c453 by Robert Marshallat 2017-07-07T14:56:31+01:00add README 36cafa6d by Robert

Agustin Benito Bethencourt pushed to branch masterat cip-project / cip-testing / imported-kernel-testsCommits: bd25c959 by Robert Marshallat 2017-07-25T14:02:02+01:00Get install correct 95e5dd3d by

Agustin Benito Bethencourt pushed to branch masterat cip-project / cip-testing / board-at-desk-single-devCommits: 645520c6 by Robert Marshallat 2017-11-06T15:19:06+00:00Install python-selinux to fix

From: Biju Das <biju.das@...> The iWave RZ/G1M Q7 SOM supports RTC (TI BQ32000). To increase hardware support enable the driver in the multi_v7_defconfig multiplatform

From: Biju Das <biju.das@...> The iWave RZ/G1M Q7 SOM supports RTC (TI BQ32000). To increase hardware support enable the driver in the shmobile_defconfig multiplatform

From: Biju Das <biju.das@...> Define the iWave RainboW-G20D-Qseven board dependent part of the RTC device node. Signed-off-by: Biju Das <biju.das@...> Signed-off-by: Chris

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:

Hi, this is a summary of the CIP related work we've done the last couple of weeks: ## Kernel maintenance * Reviewed patches from Renesas to add support for SMP and I²C masters on R8A7743 SoC, and

More about proxies: Here is update on the Lava proxy business. Please, read this very carefully, since this is the solution to the problems with Lava proxies, as well as Lava DUT ones. YES, after

On Tue, 2018-01-16 at 08:01 +0000, Chris Paterson wrote: [...] > > Meltdown: > > - arm 32-bit: Not affected?  (ARM reports that only the Cortex-A75 is > >   affected, but I haven't seen information

https://gitlab.com/cip-project/cip-testing/testing/issues/99 Also from: https://lists.cip-project.org/pipermail/cip-dev/2017-July/000338.html At the end of test issue #99, I added the solution to

Hi Zoran Zoran S <zoran.stojsavljevic.de@...> writes: https://gitlab.com/cip-project/cip-testing/board-at-desk-single-dev/tree/master/tests And if you're building the VMs using the B@D git

Could you, please, point to me where these test directories are? I did build two vagrant VM machines, one with debian/stratch64, second pre-built debian9, which refuses to behave correctly. In other

Zoran, Zoran S <zoran.stojsavljevic.de@...> writes: According to the B@D feature page, 0.9.1 was using 2016.12-1 and that was V2 - the tests were yaml files then. the current version of B@D

Hello Robert, You are correct. I am (as I email to the list about V2) finding more info about the Lava framework. The fact is that, since Lava 2017.2 Version 2 is first usable version along with

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

Zoran "zoran.stojsavljevic.de" <zoran.stojsavljevic.de@...> writes: We've been using LAVA v 2 from the start (well at least from the 0.9 release and maybe earlier). We're still using LAVA