Because meta-intel linux-yocto-tiny specifies a KBRANCH of
standard/tiny/common-pc, we get the below warning since the board
metadata doesn't match that. Add a common-pc branch to sync them up.
WARNING: .. do_patch: After meta data application, the kernel tree branch is
standard/tiny/base.
WARNI
We now have a dedicated standard/intel branch for Intel platforms, so
have intel-common/*-developer BSPs make use of it.
Signed-off-by: Tom Zanussi
---
bsp/intel-common/intel-core2-32-developer.scc | 2 ++
bsp/intel-common/intel-corei7-64-developer.scc | 2 ++
2 files changed, 4 insertions(+)
We now have a dedicated standard/tiny/intel branch for Intel
platforms, so have the core meta-intel BSPs make use of it.
Signed-off-by: Tom Zanussi
---
bsp/intel-common/intel-quark-tiny.scc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bsp/intel-common/intel-quark-tiny.scc
We now have a dedicated standard/intel branch for Intel platforms, so
have common-pc*/*-standard BSPs make use of it.
Signed-off-by: Tom Zanussi
---
bsp/common-pc-64/common-pc-64-standard.scc | 1 +
bsp/common-pc/common-pc-standard.scc | 1 +
2 files changed, 2 insertions(+)
diff --git a/
We now have a dedicated standard/preempt-rt/intel branch for Intel
platforms, so have the core meta-intel BSPs make use of it.
Signed-off-by: Tom Zanussi
---
bsp/intel-common/intel-core2-32-preempt-rt.scc | 2 ++
bsp/intel-common/intel-corei7-64-preempt-rt.scc | 2 ++
2 files changed, 4 inserti
Because meta-intel linux-yocto-tiny specifies a KBRANCH of
standard/tiny/common-pc, we get the below warning since the board
metadata doesn't match that. Add a common-pc branch to sync them up.
WARNING: .. do_patch: After meta data application, the kernel tree branch is
standard/tiny/base.
WARNI
We now have a dedicated standard/tiny/intel branch for Intel
platforms, so have the core meta-intel BSPs make use of it.
Signed-off-by: Tom Zanussi
---
bsp/intel-common/intel-quark-tiny.scc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bsp/intel-common/intel-quark-tiny.scc
We now have a dedicated standard/intel branch for Intel platforms, so
have the core meta-intel BSPs make use of it.
Signed-off-by: Tom Zanussi
---
bsp/intel-common/intel-core2-32-standard.scc | 2 ++
bsp/intel-common/intel-corei7-64-standard.scc | 2 ++
bsp/intel-common/intel-quark-standard.scc
In order to provide more timely support for Intel platforms, this
patchset makes use of a set of dedicated */intel branches to be
created for the linux-yocto 4.4 kernel.
These branches and the corresponding kernel metadata branches provide
a place to add Intel-specific features and updates which a
We now have a dedicated standard/intel branch for Intel platforms, so
have common-pc*/*-standard BSPs make use of it.
Signed-off-by: Tom Zanussi
---
bsp/common-pc-64/common-pc-64-standard.scc | 1 +
bsp/common-pc/common-pc-standard.scc | 1 +
2 files changed, 2 insertions(+)
diff --git a/
In order to provide more timely support for Intel platforms, this
patchset makes use of a set of dedicated */intel branches to be
created for the linux-yocto 4.1 kernel.
These branches and the corresponding kernel metadata branches provide
a place to add Intel-specific features and updates which a
We now have a dedicated standard/preempt-rt/intel branch for Intel
platforms, so have the core meta-intel BSPs make use of it.
Signed-off-by: Tom Zanussi
---
bsp/intel-common/intel-core2-32-preempt-rt.scc | 2 ++
bsp/intel-common/intel-corei7-64-preempt-rt.scc | 2 ++
2 files changed, 4 inserti
We now have a dedicated standard/intel branch for Intel platforms, so
have the core meta-intel BSPs make use of it.
Signed-off-by: Tom Zanussi
---
bsp/intel-common/intel-core2-32-standard.scc | 2 ++
bsp/intel-common/intel-corei7-64-standard.scc | 2 ++
bsp/intel-common/intel-quark-standard.scc
Hi Bruce,
This is a set of backports from upstream. I have tested allyesconfig,
allnoconfig, and standard builds and can't find anything wrong there.
I have also tested running the kernel on MinnowBoard Max and there are
no new errors or warnings.
Let me know if I need to make any modifications a
On 2016-05-24 3:05 AM, Zhenbo Gao wrote:
Hi All,
Ericsson AB found the following lockdep splat information on axxiaarm board:
[ 4.491058] ==
[ 4.497232] [ INFO: possible circular locking dependency detected ]
[ 4.503495] 4.1.15-rt13+ #8 Not tai
Hi All,
Ericsson AB found the following lockdep splat information on axxiaarm board:
[ 4.491058] ==
[ 4.497232] [ INFO: possible circular locking dependency detected ]
[ 4.503495] 4.1.15-rt13+ #8 Not tainted
[ 4.507325] --
From: Fredrik Markstrom
The non-HCD_BH mode has a AB-BA lock problem, but we wan't HCD_BH mode anyway
since it
performs better and all other ehci drivers uses it. It will cause the lockdep
splat below:
[4.240663] ==
[4.246838] [ INFO:
17 matches
Mail list logo